/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Source: US government has demanded source code from tech firms through FISA orders and in civil cases filed under seal, with companies losing “most of the time”

Zack Whittaker / ZDNet :

ZDNet Zack Whittaker

Context & Ripple Effects

This report lands mid-fight over whether governments can compel software, not just data. A week earlier, the DOJ argued it could force Apple to turn over iOS source code and its signing key if the company kept resisting the court order, invoking the Lavabit case as precedent — and this sourcing shows such demands were already routine through FISA orders and civil suits filed under seal, with companies losing most of the time.

The stakes are clearest against Apple's own conduct: Sewell testified Apple had refused China's source-code request within the prior two years, so the question is whether US firms can refuse their own government when the legal deck is stacked against them.

First-order effects

  • Tech firms served under FISA or sealed civil orders face a binary with almost no win condition: hand over source code quietly, or litigate and lose most of the time, with the loss itself hidden from customers by the seal.

Second-order effects

  • Compliance becomes asymmetric across the market — large firms like Apple can absorb the cost of resistance while smaller firms without in-house legal expertise over-comply, as the FBI's NSL practice of asking for more than companies are obligated to give already demonstrates.
  • Secrecy compounds the problem downstream: Microsoft later disclosed that up to one-third of US government data demands carry secrecy clauses, meaning enterprise buyers cannot audit how often their vendors' code has been accessed.

Third-order effects

  • If compulsion of source code is normalized, 'who holds the code' becomes a procurement question — sovereign and localized code custody arrangements gain commercial value precisely because foreign customers cannot distinguish a US firm that resisted from one that complied under seal.
  • The pattern also sets up the encryption-backdoor fight: the government's later position that it had not yet needed FISC approval to compel backdoor construction suggests source-code demands are the quiet precursor to broader build-out orders.

The trend: Government access is expanding from customer data to the source code itself, making state compulsion of software a standing feature of the US-tech relationship rather than an emergency exception.