A county owned the San Bernardino iPhone and consented to a search; the phone’s security still stopped the FBI

The government’s February 16, 2016 filing said a county health department owned the phone, had a search policy and consented. Its passcode and Apple’s signing control still blocked access. For agencies, ownership and policy are not a path to their own data.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

The government’s February 16, 2016 filing said a county health department owned the phone, had a search policy and consented. Its passcode and Apple’s signing control still blocked access. For agencies, ownership and policy are not a path to their own data.

  1. The week The phone did not belong to the attacker who used it.
  2. Ownership and policy: complete on paper By the government’s account, the county had every legal element an agency could want.
  3. Configuration: what the county issued, and what changed The county told the FBI two things about how it issued the phone.
  4. The keys: where the decisive control sat The government’s filing described two components that together decrypted the phone’s data.
  5. The recovery path: data that lives elsewhere Its limit was that last date.
  6. How the case reaches different public bodies The case concerned a county department’s phone.
  7. Objections, in order The device was an agency asset, issued under an agency policy, configured by the agency. [1] The FBI was the one asking, but an agency’s records officer or counsel could face the same locked screen.
  8. Checks an agency CIO or CISO could run For each class of device, record whether the agency may access it under policy and whether it can access it in fact.
  9. With hindsight The court case ended without a ruling on the merits.

The week

On February 16, 2016, the US Attorney’s Office for the Central District of California filed an ex parte application asking a federal court to order Apple to help the FBI search an iPhone. [1] The phone had been seized under a search warrant issued and executed on December 3, 2015, in the investigation of the December 2, 2015 shootings in San Bernardino. [1] The application was filed under the All Writs Act, 28 U.S.C. 1651. [1]

The phone did not belong to the attacker who used it. The application said the device was owned by his employer, the San Bernardino County Department of Public Health, and was assigned to and used by him as part of his employment. [1] It said the department had given its consent to the search and to Apple’s assistance. [1] A footnote added that the department had a written policy that all digital devices are subject to search at any time, which the employee had accepted by signature when hired. [1]

The application then explained why consent and a warrant were not enough. It said the FBI had been unable to search the phone because it was locked with a user-determined numeric passcode. [1] It said the FBI could not try to determine the passcode because of an auto-erase function that, if enabled, would destroy the encryption key material after 10 wrong attempts. [1] It added that iOS invokes escalating delays after failed attempts, up to a one-hour delay after the ninth. [1]

The government’s filing described the encryption in some detail. It said iOS 9 encrypts data files with a combination of the user’s passcode and a unique 256-bit AES key fused into the phone during manufacture. [1] It said the phone would run only software signed by Apple, which prevented anyone else, including the government, from running other software to recover data or test passcodes. [1]

The request was specific. The government asked Apple for a signed software file that would run from the phone’s memory. [1] It would bypass or disable the auto-erase function, allow passcodes to be submitted electronically and add no delays between attempts beyond those the hardware imposed. [1] It said the file could be coded to run only on that phone, and could be loaded at a government facility or at Apple’s. [1]

The filing also described what the county’s settings had left behind. The FBI declarant said the department told him the phone was provided with the auto-erase function turned on, and that the most recent iCloud backup also showed it on. [1] The application said the most recent backup obtained by the government was dated October 19, 2015. [1] The declarant said the department told him automatic backup was turned on when the phone was given to the employee, which led him to believe the employee may have disabled it. [1]

The Justice Department’s Inspector General later reported that the office sought and obtained an ex parte court order that day requiring Apple to assist the FBI. [3] Apple answered publicly the same day. In a letter to customers dated February 16, 2016, the company said it opposed the order and that the government had asked it to build what it called a backdoor to the iPhone. [2] The letter said Apple had complied with valid subpoenas and search warrants in the case and had made engineers available to advise the FBI. [2] It argued that software of the kind requested could be used again on other devices once created. [2]

The San Bernardino dispute set a technology company against the FBI. For a public agency’s technology and security leaders, the more useful fact is in the government’s first paragraph of facts. The phone belonged to a county public health department, which had a written search policy and consented to the search. [1] None of that opened the phone. [1]

Our argument is that the case separated three kinds of control an agency may assume are one. Legal control, through ownership and policy, was complete. [1] Configuration control, through the settings the county issued, existed but had drifted. [1] Cryptographic control sat with the passcode the employee chose and the signing key Apple held. [1] The only route the agency itself could have built in advance was a recovery path, and the filing shows what was and was not in it. [1]

We take the case in four parts:

  1. Ownership and policy: what the county’s legal control over the device could and could not do.
  2. Configuration: the settings the county issued with the phone, and how they changed.
  3. The keys: where the encryption put the decisive control.
  4. The recovery path: what the county could retrieve without the phone, and what that implies for agency planning.

The parts do not overlap. The first is legal authority, the second device state, the third cryptography and the fourth data that lives elsewhere. After them we look at how the case reaches different kinds of public body, take the objections in order and end with checks an agency CIO or CISO could run.

Ownership and policy: complete on paper

What the county had

By the government’s account, the county had every legal element an agency could want. It owned the device. [1] It had assigned it to an employee for work. [1] It had a written policy that all digital devices are subject to search at any time, accepted by the employee in writing. [1] And it consented to the search and to Apple’s help. [1]

The FBI also had a warrant. The application said the search was authorized by a warrant obtained and executed on December 3, 2015. [1] So the question was never whether the search was lawful. The government’s own framing was that, despite both a warrant and the owner’s consent, it could not complete the search. [1]

What the policy could not do

A search policy answers a legal question: may the employer look? It does not answer a technical one: can the employer look? The two questions came apart on this phone. The county’s authority to search was clear; its ability to search depended on a passcode it did not have.

That distinction applies well beyond a criminal investigation. An agency may need a departing employee’s device for a records request, a litigation hold, an internal investigation or an audit. In each case, a policy that says the agency may access the device is necessary. It is not sufficient.

The application said the department gave its consent to the search and to Apple’s assistance. [1] It did not say which official gave it. For an agency, the question is worth settling before anyone asks: who may consent to a search of an agency device, on what advice, and how the consent is recorded.

Counsel, the records officer and the department head may each have a role. A request from law enforcement, a records request and an internal investigation may call for different approvers. A short written rule avoids improvising under pressure.

The signed acknowledgment

The county’s policy had been accepted by the employee’s signature at hiring, according to the application. [1] That acknowledgment settled the employee’s side of the legal question. It told the employee that the device was subject to search at any time. [1]

An acknowledgment of that kind could also carry operational duties: to keep backup enabled, to leave management controls in place and to return the device unlocked at separation. Those duties would not open a locked phone, but they would make drift a policy violation as well as a technical event.

The application treated the county’s consent as one input among several. It recited the warrant, the consent and the county’s policy, and then turned to what Apple could do. [1] In our reading, the filing shows that an owner’s consent removes legal obstacles but adds no technical capability. Only the party holding a key or a signing authority could add that.

Why this matters for public records

Public agencies hold records subject to retention schedules and public records laws. A record on a locked device the agency cannot open is a record the agency may be unable to produce. The legal duty and the technical capability have to be planned together, at the time the device is issued, not when the record is requested.

Holds and requests on locked devices

A litigation hold or a records request can name an employee’s phone. The agency’s legal duty to preserve and produce then meets the same technical limit the FBI met. If the agency cannot open the device, it may be unable to say what is on it, let alone produce it.

The defensible position is to know in advance which records live only on devices, and to keep that set as small as policy allows. A hold notice that reaches a device the agency cannot read is a problem counsel should hear about early, not when production is due.

Configuration: what the county issued, and what changed

Two settings on at issue

The county told the FBI two things about how it issued the phone. The phone was provided with the auto-erase function turned on, according to an employee of the department. [1] Automatic iCloud backup was also turned on when the phone was given to the employee, the department said. [1]

Both settings are sensible on their own. Auto-erase protects data if a phone is lost or stolen. Backup protects data if a phone fails. In this case, the first one helped stop the FBI from guessing the passcode. [1] The second one would have preserved a copy of the data elsewhere, if it had kept running. [1]

The setting that drifted

The most recent backup the government obtained was dated October 19, 2015. [1] The FBI declarant said that, given the department’s statement that backup was on when the phone was issued, he believed the employee may have disabled it. [1] The application also said toll records showed the phone was used to communicate with another person named in the filing between July and November 2015, and that this information was not in the backup. [1]

For an agency, the issue is drift. A setting chosen at issue is a statement about the device on one day. Unless something enforces it, a user can change it. In this case, the setting that would have kept a copy of the data was the one the FBI believed the employee may have disabled; the one that would destroy data after failed guesses was, the FBI suspected, still on.

Issuance records became evidence

The filing said it is not apparent from the outside whether the auto-erase function is enabled on a locked iPhone. [1] The government relied in part on what the county told it about how the phone was issued, and on the last backup, to suspect that it was on. [1]

That made the county’s issuance practice part of the evidence. An agency that records each device’s configuration at issue, and keeps that record, can answer such a question with documents. An agency that relies on memory can answer it only with a staff member’s recollection.

An inventory of configurations

An inventory that lists device, user and serial number is not enough for this purpose. The useful inventory also lists the configuration profile applied, the date it was applied and the last date it was confirmed. That is the record that would tell an investigator, or a records officer, what to expect when a device is locked.

The settings an owner can enforce

NIST’s current guidance on mobile devices in the enterprise addresses this problem in general terms. Its abstract says the publication describes technologies and strategies for managing and securing mobile devices, and covers centralized device management and endpoint protection. [4] It covers both organization-provided and personally owned devices across the device lifecycle. [4]

We do not know from the sources what management tools the county used. The point for an agency is the design question the case raises: which settings on an agency-owned device are enforced by the agency, and which are only defaults a user can change. A backup that matters for records should be in the first group.

Configuration as a records decision

Device settings can look like an IT choice made for security and convenience. The case shows that some of them are also records decisions. Whether work data is backed up, where the backup lives and who can reach it determine what the agency can retain and produce.

That argues for the records officer and counsel having a say in the device standard, alongside security. A standard written only by the security team may protect the data well and still leave the agency unable to retrieve its own records when it must.

Security settings that cut both ways

Auto-erase is a good control against a thief and an obstacle to the owner who has lost the passcode. [1] The case shows that an agency choosing it should also choose how it will recover data if the passcode holder is unavailable. Turning the control off is one answer. Building a separate recovery path is another, and is the subject of the fourth part.

The keys: where the decisive control sat

The passcode and the hardware key

The government’s filing described two components that together decrypted the phone’s data. One was the user-determined passcode. The other was a unique 256-bit AES key fused into the phone during manufacture. [1] Both were required, combined in a calculation that the filing described as determined by Apple’s software and unknown to the government. [1]

That design meant the data could not be decrypted off the phone by copying it elsewhere and guessing there, in our reading of the filing. Guesses had to go through the phone, where auto-erase and delays applied. [1]

The signing key

The second control was the software signature. The filing said Apple designed its hardware and operating system to run only software signed cryptographically by Apple. [1] That prevented the government from running its own software on the phone to test passcodes. [1] It said only Apple could modify the software to change the auto-erase setting or prevent it from running. [1]

Apple’s letter described the same fact from its side. It said the FBI wanted a new version of the iPhone operating system, circumventing several important security features, installed on the recovered phone. [2] It argued that such software could unlock any iPhone in someone’s physical possession if it fell into the wrong hands. [2]

Delays and erasure as controls

The filing described two non-encryption features. One was auto-erase, which it said would destroy the encryption key material after 10 consecutive incorrect passcodes if enabled. [1] The other was escalating delays after failed attempts, up to a one-hour delay after the ninth. [1]

Together they turned guessing into a gamble. The filing said trying successive passcodes risked permanently losing the ability to access the data. [1] For an agency, the same features protect a lost phone from a finder. They also mean that the agency, as owner, cannot guess its way in either.

What the government asked Apple to change

The request was for software that would run from memory and leave the operating system and user data partition on the phone unchanged. [1] It would disable auto-erase, allow passcodes to be submitted electronically and add no delay beyond the hardware’s. [1] The filing said the software could be made to run only on the one phone, by checking its unique identifiers. [1]

Apple’s letter disputed the limit. It said the government suggested the tool could be used only once, on one phone, but that once created the technique could be used again on any number of devices. [2] The disagreement was about whether a tool built for one device stays limited to one device. An agency designing its own recovery path faces a smaller version of the same question.

Older systems, different answers

The filing said Apple had the ability, with older operating systems, to obtain unencrypted file content from phones without the passcode. [1] It said Apple had routinely done so for law enforcement with a search warrant and an accompanying All Writs Act order. [1] The phone in this case ran iOS 9. [1]

For an agency, that statement means the answer to whether data can be recovered depended on the operating system version. A fleet with mixed versions has mixed answers. The inventory that records configuration should also record the version, because it changes what is possible.

Why the owner held neither key

The county owned the hardware. It did not hold the passcode, which the employee had set, and it did not hold the signing authority, which Apple held. In our reading, that is the core of the case for an agency: owning a device does not mean holding either key that controls access to its data.

That is a design property, not a defect. The same property protects an agency’s data when its phones are stolen. The question for the agency is whether it has its own legitimate path to its own data that does not depend on either key.

The agency’s own signing keys

The filing’s description of Apple’s signing control has a parallel inside agencies. [1] An agency that runs a device management platform, signs its own software or issues certificates holds keys that decide what runs on its devices. Those keys are the agency’s equivalent of the control Apple held over the phone.

They deserve the same care: a named owner, protected storage, limited use and a record of each use. An agency that cannot say who holds its signing keys has the same blind spot, at smaller scale, that the case exposed for the device.

The vendor as the remaining party

When the owner and the user cannot unlock a device, the remaining party is the manufacturer. The government’s request shows what that means: an order directing the manufacturer to write and sign software for one device. [1] Apple’s letter shows the manufacturer’s view of that request. [2]

For an agency, depending on a vendor and a court to reach its own records is a poor plan. It takes time, it is uncertain and it sets the agency’s needs against the vendor’s interest in the security of all its customers.

The recovery path: data that lives elsewhere

What the backups showed

The government obtained iCloud backup data. [1] The application described evidence from it, including communications with people later killed in the shootings. [1] The backup was therefore a recovery path that worked, up to its last date. [1]

Its limit was that last date. The application said the government believed the phone might hold data from the period after the last backup that could not be obtained any other way. [1] In our reading, the backup did what backups do: it preserved what it captured, and nothing after it stopped.

What the vendor could already provide

Apple’s letter said that when the FBI requested data in Apple’s possession, Apple provided it, and that it complies with valid subpoenas and search warrants. [2] The cloud backup was that kind of data. [1] [2] In our reading, the cloud copy was reachable by legal process because it lived on the provider’s systems, while the phone’s contents were not.

For an agency, that raises a question the filing does not answer: whose account held the backup. A backup tied to an account the agency controls is a recovery path the agency can use directly. A backup tied to an account the employee controls may be reachable only through the provider, with legal process. Agencies should know which kind their devices use.

Records the agency held anyway

Toll records showed communications that the backup did not contain. [1] Those came from the carrier, not the phone. An agency’s own systems, such as email servers, document repositories and collaboration platforms, are similar sources. Data that also lives in an agency-controlled system does not depend on the device.

The planning principle follows. The more agency records are created and kept in agency-controlled systems, the less any single device matters. A phone used as a window into those systems holds less that only the phone can produce.

Designing the path in advance

NIST’s guidance frames device management as a lifecycle that runs from deployment through use to disposal. [4] In our reading, the recovery path belongs at the start of that lifecycle. An agency deciding how to issue a phone can decide at the same time where its records will be kept, which settings will be enforced and who can recover access when the user cannot.

These are choices with trade-offs. A recovery mechanism that the agency controls is also a path an attacker may target. It needs strong authentication, logging and limited administrators. The case does not argue for weaker devices. It argues for a deliberate path that the owner controls.

Separation and offboarding

Agencies also need devices back for ordinary reasons: an employee’s departure, illness or death. A separation checklist that includes returning devices unlocked, and confirming that records are in agency systems, prevents the problem in the ordinary case.

For unplanned absences, the recovery procedure has to work without the employee. That is the case the San Bernardino filing describes in its most extreme form, and the reason the procedure should be designed and tested before it is needed.

What a recovery path costs

A recovery path has costs an agency should state openly. It needs a management platform, staff who run it, enrollment of every device and periodic tests. It also creates a privileged function that must itself be protected, with strong authentication, separation of duties and logging of every use.

Against those costs, the agency weighs the cost of records it cannot produce, investigations it cannot complete and the time it would spend seeking outside help. The case shows the outside help is uncertain. The weighing is the agency’s to do, and it is better done in a budget cycle than during an incident.

Testing the path

A recovery procedure that has never been run is a hypothesis. Agencies can test it on returned devices before they are wiped, or on a sample of active devices with the user’s cooperation. The test should confirm that the records expected in agency systems are there, and that recovery access works for the device models in use.

Each test is also a check on the configuration inventory. A device that cannot be recovered as expected is either misconfigured or recorded wrongly. Either finding is useful before an investigation, request or departure depends on it.

The path the FBI found

In the end, the FBI reached the data by another route. The Justice Department’s Inspector General later reported that on March 21, 2016, the government told the court that an outside party had demonstrated a possible method for unlocking the iPhone. [3] On March 28, 2016, it reported that the FBI had accessed the phone and no longer needed Apple’s help. [3]

That route is not available to a county records officer. It relied on a vendor’s exploit technique and a law enforcement agency’s resources. For an agency’s own planning, it is a reminder that the fallback was outside the owner’s control entirely.

How the case reaches different public bodies

The case concerned a county department’s phone. The same separation of controls applies across public bodies, with differences in what each must be able to retrieve.

A county public health department

The department in the case had the policy and the consent. [1] A similar department today would want enforced backup or server-side storage for work records. It would also want a way to recover access when an employee leaves or cannot be reached, and a record of how each device was configured at issue.

A state agency

A state agency with a central IT department can set device standards once and apply them statewide. Its risk is the gap between the standard and the device actually in an employee’s hand. Periodic compliance checks against the standard are the evidence that the configuration has not drifted.

A federal agency

A federal agency can turn to NIST’s guidance on managing mobile devices. [4] Its records duties and its security duties meet on the same device. The device plan should name who decides on recovery access and how that decision is logged.

A police department

A police department is on both sides of this case. It issues devices to its own staff and seeks access to devices in investigations. Its own devices hold evidence and case data that it must be able to produce. The configuration lessons apply to its fleet as much as to any other agency’s.

A public hospital or health system

A public hospital issues phones that may hold patient communications. The same three questions apply: may it access them, can it access them, and is the data also kept in a system it controls. Clinical messaging that lives on a managed platform reduces dependence on any one handset.

A school district or small municipality

A smaller public body may have no device management at all. For it, the minimum is a written policy, a configuration checklist applied at issue and a clear rule that work records live in agency systems as well as on phones.

A utility, transit or port authority

An authority that runs physical infrastructure issues phones to field staff and supervisors. Those devices may hold operational messages that matter after an incident. The same separation applies: policy authority over the device, configuration that keeps records elsewhere and a tested recovery path.

A prosecutor’s or attorney general’s office

A prosecutor’s office may be the party seeking access to someone else’s device, as the US Attorney’s Office was here. [1] It also issues devices to its own attorneys and investigators, which hold case material subject to discovery and retention rules. The office’s own fleet needs the recovery path it would want any other agency to have.

A personally owned device used for work

NIST’s guidance covers personally owned devices too. [4] An agency has weaker legal control over an employee’s own phone than the county had over its own device. The recovery path for work records on such devices has to run through agency systems, because the agency will not own the hardware.

Objections, in order

1. This was a law enforcement case with no lesson for agency IT

The device was an agency asset, issued under an agency policy, configured by the agency. [1] The FBI was the one asking, but an agency’s records officer or counsel could face the same locked screen. The difference is that they would have no court order and no outside vendor to call.

2. Ownership should have been enough

Legally it was: the search was authorized and consented to. [1] Technically it could not be, given the design the government described. [1] An agency that expects ownership to deliver access is relying on a property the hardware was built not to provide.

3. Turning off security features would have solved it

Turning off auto-erase would have let guessing proceed, but the filing said escalating delays applied after failed attempts. [1] It would also have weakened the phone against theft. A recovery path that does not depend on guessing is the better design.

4. The backup was enough

The backup worked up to its last date. [1] The government said data after that date might exist only on the phone. [1] A backup the user can switch off is a convenience; a backup the agency enforces is a control.

5. The vendor will help when it matters

Apple said it had provided data in its possession and offered engineers and ideas. [2] It also said publicly that it opposed the order to build new software. [2] An agency’s plan should not assume a vendor will write custom tools to reach the agency’s own data.

6. Encryption was the problem

The encryption protected the data as designed. [1] The agency’s difficulty came from having no other path to its own records for the period after the last backup. [1] Weakening encryption on agency devices would expose them to every thief and attacker. Building an owner-controlled path addresses the agency’s need without that exposure.

7. An agency recovery path is a backdoor by another name

Apple’s objection was to software that, once created, could be used on any number of devices in someone’s physical possession. [2] An agency recovery mechanism for its own enrolled devices is narrower in scope: it covers devices the agency owns, under the agency’s management. It is still an attractive target, which is why it needs the protections described in the fourth part.

8. Devices have changed since 2016

Devices and operating systems have changed, and the specific features the filing described belong to one version. [1] The separation of controls has not. NIST’s 2023 guidance still treats organization-provided devices as a management problem across their lifecycle, with centralized device management within its scope. [4] The questions in this article apply to whatever devices an agency issues now.

Checks an agency CIO or CISO could run

Policy and capability match

For each class of device, record whether the agency may access it under policy and whether it can access it in fact. Any device where the answers differ is a gap to close.

Enforced settings

List the settings on agency phones that are enforced by management tools and those that are only defaults. Backup of work records and the recovery method belong in the enforced list. [4]

Drift reporting

Produce a regular report of devices whose configuration differs from the standard. A device that stopped backing up is a finding, with an owner and a date.

Exception register

Keep a register of devices exempted from the standard configuration, with the reason, the approver and an end date. An exception without an end date becomes the configuration, and the case shows how much depends on the configuration actually in place.

Tabletop exercise

Run a short exercise in which a key employee’s locked phone is needed for a records request and the employee cannot help. Record each step the agency would take, who would take it and where the process would stop.

Records location

Confirm that work records, including messages where policy requires it, are kept in agency systems as well as on devices. Test retrieval for a sample of departed employees.

Recovery procedure

Write down how the agency regains access to a managed device when the user cannot or will not unlock it, who may authorize that and how the action is logged. Test it.

Issuance records

Keep a record of each device’s configuration profile, operating system version and issue date, and confirm it on a schedule. The San Bernardino filing relied on the county’s account of how the phone was issued. [1]

Separation checklist

Add device return, unlock and records confirmation to every separation checklist, and audit a sample of completed separations each quarter.

Write down who may consent to a search of an agency device, for law enforcement, records and internal purposes, and how the consent is documented.

Signing key register

List the keys and certificates that control what runs on agency devices, such as device management and code signing keys, with an owner, storage location and record of use for each.

Backup account ownership

For each managed device type, record which account receives its backups and whether the agency controls that account. Move work backups to agency-controlled accounts where the platform allows it.

Vendor dependence

Identify which device records could be reached only with the manufacturer’s help. Treat each as a residual risk with a named owner, since the case showed that help is not assured. [2]

With hindsight

The court case ended without a ruling on the merits. The Justice Department’s Inspector General reported in March 2018 on how it ended. [3] On March 21, 2016, before the district judge ruled on the pending motions, the US Attorney’s Office told the court an outside party had demonstrated a possible method for unlocking the iPhone. [3] On March 28, 2016, it reported that the FBI had successfully accessed the phone and no longer required assistance from Apple. [3]

The Inspector General’s inquiry examined whether the FBI’s statements had been accurate. It found no evidence that the FBI’s Operational Technology Division had the capability to exploit the phone when the Director testified to Congress and when the initial court filings were made. [3] It therefore determined that neither the testimony nor the court submissions were inaccurate when made. [3]

The report found something else. It said inadequate communication and coordination within the division delayed engaging all relevant personnel, and the outside party that later developed the method. [3] It found that the chief of one unit had only just begun contacting vendors on the eve of the February 16 filing, including one he knew was almost 90 percent finished with a solution. [3] The report said that, as a result, the government had to withdraw its stated position that it could not access the phone without the manufacturer’s cooperation. [3] The report also recorded that, after reviewing a draft, the FBI represented that there had been no delay in the vendor’s development of the technique and that the vendor had developed it on its own. The Inspector General said the suggestion that the vendor had done so without any request was not consistent with the unit chief’s testimony. [3]

The Inspector General recommended that the FBI finalize a reorganization and other actions to ensure full coordination. [3] The FBI’s response, dated March 9, 2018 and included in the report, concurred with the recommendation. [3]

For agencies, the report confirms a point from the body of this article in an unexpected way. Even the FBI’s answer to the question of what it could access depended on whether the right internal teams had been asked. [3] An agency’s own inventory of what it can recover from its devices is only as good as the canvass behind it.

NIST published Special Publication 800-124 Revision 2, Guidelines for Managing the Security of Mobile Devices in the Enterprise, in May 2023. [4] As checked on November 16, 2026, the NIST page lists it as final. [4] Its abstract says mobile devices are now permanent fixtures in enterprises used to process sensitive data, and that it gives recommendations for deployment, use and disposal across the device lifecycle. [4]

What held up from February 2016 is the separation of controls the government’s filing laid out. Ownership and consent did not unlock the device; the passcode and the manufacturer’s signing control decided access. [1] What changed is how the specific phone was reached, by a third party’s method rather than the manufacturer’s. [3] That route is not one a public body can plan around for its own records.

The FBI’s response also said the problems the report noted were addressed through a change in leadership for the units involved. [3] It said the division had realigned mission areas for several units ahead of a larger reorganization. [3]

In our view, the durable point for a county, state or federal agency is to decide at issue how it will reach its own data without the user and without the vendor. The case shows what it costs to find out afterward that the answer is no. [1] [3]

Spotted an error? Tell us and we will check it and correct the article where needed.

  • mobile devices
  • encryption
  • All Writs Act
  • device management
  • public records
  • backup