Government claims San Bernardino shooter had disabled iCloud backup system
Russell Brandom / The Verge :
Context & Ripple Effects
This claim sits at the center of the court order demanding Apple disable the iPhone's 10-tries-and-wipe feature: the government argued iCloud auto-backup was already switched off on the device, so only compelled code from Apple could open it. Apple countered that the phone stopped backing up because the Apple ID passcode was changed while the phone sat in government custody, which would make the FBI's own handling the cause.
Who disabled backups determines who bears responsibility for the standoff — and whether the legal compulsion of Apple was ever necessary. Weeks later the DoJ withdrew the case entirely after an outside method cracked the phone, and news outlets filed suit to learn what that method was.
First-order effects
- If the shooter disabled iCloud backup himself, the government's premise for compelling Apple holds and Apple's custody-negligence defense weakens; if the passcode reset caused it, the FBI undercut its own access path before ever reaching a judge.
Second-order effects
- The dispute pushed both sides toward workarounds that bypassed Apple altogether — the ACLU laid out how partial backup could defeat auto-erasing without Apple's help, and the eventual crack reportedly involved external forensics like NAND mirroring, shifting leverage away from the courtroom.
Third-order effects
- With the DoJ withdrawing once a private method worked, the structural question becomes whether future device standoffs get litigated at all or quietly routed through third-party forensics firms — and the AP/Vice/Gannett FOIA suit shows the methods themselves becoming the next transparency battleground.
The trend: The Apple–FBI confrontation marks the moment law enforcement began treating third-party exploit vendors as the practical route around encryption, with litigation as leverage rather than endpoint.