Encryption: who controls the state’s access to our messages?

The economic cost of a backdoor · Part 3 of 7

A legal authorization has to become a technical instruction and, eventually, a flow of data. Along the way, people activate access, protect secrets and check the records. This investigation follows that infrastructure and its funding in France, the United States and China.

For 2025, the U.S. Courts report records 296 federal wiretaps in which encryption was encountered. In 269 of them, the authorities reported being unable to decrypt the communications. Published on June 30, 2026, the report gives a concrete measure of the difficulty investigators face. It also leaves open the question that matters to a business, an engineer or a taxpayer: what would have to be built to make an additional route of access possible, and who would bear the consequences? ^R01

An authorization sets an objective and a scope. To deliver a result, it needs a technical capability: a carrier able to isolate the targeted communications, a provider holding a key, an accessible device, or a mechanism added for the purpose. This is where the debate over backdoors acquires an economic dimension. An access function has to be designed, operated, protected and supervised. That work may continue after the case that made it necessary has closed.

This third article follows the passage from law to infrastructure. French, American and Chinese legislation offers different answers to the question of assistance. Technical standards help explain the work required to put those answers into practice. Read together, they reveal a shared concern: the scope of an individual request can differ substantially from the reach of the system built to execute it.

Investigative obstacles, with limits to the evidence

The same U.S. report records 229 state wiretaps in which encryption was encountered, including 217 with a reported inability to obtain plaintext. These figures count reported wiretaps, using information collected about the investigations to which they relate. They count neither messages nor people. An inaccessible communication may deny investigators useful evidence; the outcome of the investigation also depends on the other evidence available. ^R01R02

Method and scope

Report published on 30 June 2026. Unit: one reported wiretap that encountered encryption, with information also covering its investigation. Calculations: 296 − 269 = 27 federally; 229 − 217 = 12 at state level. These remainders do not establish a count of successful decryptions. Non-federal reporting guidance defaults some missing answers about access to plaintext to “No”; the number of such defaults in the 2025 data remains unknown. This documented state-reporting rule is separate from federal reporting arrangements. The 249 federal and 80 state authorisations without a corresponding prosecutor report remain outside the bars. FISA interceptions are excluded. The figures measure neither messages nor people nor investigations wholly defeated by encryption.

The gray portions of the chart need explaining. The arithmetic remainders are 27 for federal wiretaps and 12 for state wiretaps. They are labeled “Other wiretaps with encryption encountered.” The non-federal reporting guide provides for a missing answer to the question about inability to obtain plaintext to be filled in as “No.” We found no public count of answers completed in this way for 2025 in the documents examined. Treating these remainders as counts of successful decryption would therefore go beyond the evidence. ^R02

The coverage has further limits. The report identifies 249 federal authorizations and 80 state authorizations for which no corresponding prosecutor’s report was received. Interceptions governed by the Foreign Intelligence Surveillance Act, or FISA, are excluded. These gaps prevent the bars from yielding a general rate of investigations stalled by encryption. They do not erase the difficulties that were reported. ^R01R25

That is the strongest starting point for taking investigators’ requests seriously: some potentially useful content remains beyond their reach. Evaluating a response then requires knowing what it would make readable, under which circumstances and with what additional exposure. A count of judicial requests, on its own, supplies none of those answers.

The different operations behind an access demand

“Access” covers several different operations. A provider may hand over data it can already read. A person may know the secret needed to decrypt a file. A mechanism may capture content on the device where it appears. A legislative change may seek to require a capability that the product did not previously have. Each situation involves different resources, rules and risks. The legislation examined here has to be read at that level of detail. ^R03R06R09R12

In this article, a backdoor means an additional route for reading content introduced into an architecture to provide privileged access beyond the readers allowed by its original protection. This is a working definition. A demand for data already accessible to a provider does not, by itself, establish that such a route has been added.

U.S. law draws this distinction clearly. The Communications Assistance for Law Enforcement Act, or CALEA, requires interception capabilities from carriers within its scope. Section 1002 also limits those obligations: the subchapter does not authorize law enforcement to impose a specific technical design, and it excludes information services from the requirements of subsection (a). Its decryption provision has two cumulative conditions: the carrier must have supplied the encryption and must possess the information needed to decrypt. This provision has a defined scope; it does not summarize every U.S. power to obtain access to data. ^R03

The economic question follows immediately. Producing available data takes work. Creating a new route for reading it entails a design decision and subsequent maintenance. Conflating the two can assign the cost of transforming a service to a routine administrative response, or reduce that transformation to a formality.

France’s different routes to assistance

French criminal law provides a first example. Under the conditions it specifies, Article 434-15-2 of the Criminal Code criminalizes refusing to provide or use secret means of decryption known to the person served with the demand. For this analysis, the decisive point is whether that person possesses the knowledge. The provision penalizes a refusal within a defined framework; its wording alone does not establish a duty to create an entirely new capability. ^R09

In its decision of March 30, 2018, the Constitutional Council upheld the challenged first paragraph. Its reasoning takes account, among other things, of knowledge of the secret means of decryption and the already identified data to which the request relates. The decision concerns the provision examined. Assessing another technique would require examining its own legal powers and safeguards. ^R10

Computer data capture follows a different route. Within the framework for special investigative techniques, the Code of Criminal Procedure allows the collection of data that is stored, displayed on a screen, entered or received through certain peripherals. The device is then the point of access to the content. Authorizing the measure, implementing it technically and overseeing its execution are separate functions. Depending on the procedural setting, authorization involves either the judge responsible for liberties and detention, acting on a prosecutor’s application, or an investigating judge after receiving the prosecutor’s opinion. In the urgent circumstances defined by the code, the investigating judge may act before receiving that opinion. Appointing a technician takes place within the framework of an authorised measure. ^R11R12

Intelligence gathering under the administrative framework follows another regime. Article L. 871-1 of the Internal Security Code governs the provision of decryption information by certain providers and, in its second sentence, its use by providers, who may demonstrate that they cannot comply. The implementing rules require a written decision stating its reasons, issued by the prime minister or a delegate, notified to the provider and communicated to the chair of the Commission nationale de contrôle des techniques de renseignement, France’s intelligence oversight commission, known as the CNCTR. That communication has its own role in the procedure. ^R06R07

The CNCTR also describes on-site and remote oversight of implementation, with access to records and the intelligence concerned within its remit. These checks can examine how an authorized technique has been used. Assessing a system’s security also requires knowing who can change its permissions, alter its logs or redirect its delivery destination. Legal oversight and technical scrutiny meet here, examining different aspects of the same process. ^R14R22

For a provider, these distinctions are practical. The team handling a request must identify its legal basis, the authority issuing it, the data concerned and the capability actually available. The internal arrangements required cannot be inferred from the word “decryption” appearing in a demand.

Instructions and data travel on separate paths

Consider an abstract example: a competent authority requests the communications of an identified target over a specified period. The example describes the functions of a system. It does not reproduce a particular case or network.

One path carries the instructions. The request arrives, its scope is translated into technical parameters, and the necessary permissions are activated. A second path carries the data: the content or associated information is collected, prepared and delivered to the intended recipient. This distinction is familiar in computer security. The US National Institute of Standards and Technology’s (NIST) zero trust architecture separates the decision to allow access, the establishment of a connection and the enforcement of the rules. ^R23

Method and scope

An original, qualitative functional model rather than a reproduction of an actual infrastructure. Amber arrows show instructions; turquoise arrows show data; dotted lines show records available for review. Separating functions distinguishes the access decision from execution and scrutiny. Eligible actors, procedures and exact powers depend on applicable law. ETSI and NIST standards describe technical functions; legal authority comes from the governing framework. A secure delivery circuit leaves the initial capability to obtain plaintext as a separate question.

The lawful interception architecture published by the European Telecommunications Standards Institute (ETSI) in August 2026 likewise describes separate roles and functions, spanning the requesting authority, the provider and the recipient of the results. A standard gives systems a common language; applicable law determines the authorizations. Security then depends on what each component can do and on the checks performed between them. ^R20

The delivery path itself needs protection. Another ETSI specification provides encryption mechanisms for handing over intercepted information over IP. That protection aims to prevent the result from being exposed in transit. It addresses a separate question from reading the original content: securing the delivery channel does not explain how the provider obtained the plaintext. ^R21

The U.S. provisions illustrate this transition to execution. For activation within a carrier’s switching premises, Section 1004 of CALEA requires lawful authorization and the affirmative intervention of an officer or employee of the carrier. Section 229(b)(2) provides for rules requiring secure and accurate records of interceptions and access, whether authorized or unauthorized. The framework thus combines a condition for activation with a recordkeeping obligation. ^R04

A simple error shows why these distinctions matter. An incorrectly translated identifier could direct a valid request toward the wrong target. An inadequately checked destination could send the result to the wrong recipient. These are operational scenarios; no frequency is estimated here. They show why accurate execution forms part of the cost of a measure even when its legal basis is established.

When an authorization ends, the infrastructure may remain

The duration of a measure is an essential limit. Several time frames apply to the same access capability. The authorized period governs an operation. The equipment or software executing it may have been deployed earlier and may remain available afterward. Data already collected follows the retention and processing rules applicable to its use.

Method and scope

Qualitative timelines without a time scale. Point positions and line lengths are illustrative; they measure neither durations nor proportions. Maintaining a capability beyond an operation is a possibility in this model, without a claim about any particular operator. In the cited ETSI lifecycle, the inactive state stops production of intercepted information, with an exception allowing delivery of already captured communications. Legal retention and deletion rules require separate assessment.

The ETSI standard reflects this separation: moving to the inactive state stops the production of intercepted information while still allowing the delivery of communications already captured. Collection ending and every copy disappearing are therefore separate events. The timeline illustrates that logic without assigning a universal retention period. ^R20

The economic implication is an inference: if a capability remains installed, its components, permissions and interfaces continue to require appropriate management. A one-off request may use infrastructure that persists. The budget for the operation and the budget for maintaining that infrastructure need not follow the same timetable.

The question becomes more acute when a reading capability is added to a widely distributed product. An authorization may concern a single person. The mechanism designed to answer future requests may serve a much larger population. The difference depends on the design: selection by target, separation of environments, custody of secrets and the actual means of activation. Only a precise account of the architecture makes it possible to assess that reach.

Audit trails need controls of their own

An audit log records events: an activation, a change in permissions, a delivery of data. Its value for oversight depends on how it is protected. If the same technical identity can trigger an operation and erase its record, the reviewer relies on evidence that the person or system under review can alter.

NIST addresses this problem through separation of duties, least privilege, which limits permissions to necessary operations, and protection of audit information. The controls it describes include separate storage and restricted administrative permissions. These measures help limit the power concentrated in a single account or role and must be adapted to the system concerned. ^R22

Separation has a tangible cost. ETSI states that keeping trust domains separate requires network and personnel resources. Where domains are combined to simplify the architecture, the standard calls for security analysis and compensating measures. The trade-off is therefore present within the mechanism itself: a leaner arrangement can concentrate more technical power. ^R20

That concentration also attracts attackers. In its April 24, 2025 alert on the campaign known as Salt Typhoon, the FBI described the theft of call data logs, a limited number of private communications and the copying of certain information subject to U.S. court-ordered law enforcement requests. It attributed the campaign to actors affiliated with China. The source records the U.S. authorities’ findings and attribution; it does not establish that lawful interception interfaces were the points of entry or that end-to-end encryption was broken. ^R26

For this analysis, the case chiefly illustrates the value of information gathered around lawful access. An interception chain contains data, targets, parameters and records. Protecting it requires considering each of those objects.

The strongest argument for an organized access system lies precisely in the ability to define responsibilities, limits and evidence of use. The standards show that this engineering work exists. A further difficulty arises when a general route of access is demanded for content that the provider was previously unable to read. The research report Keys Under Doormats raised the complexity and governance problems associated with such exceptional access in 2015. Any particular architecture still needs to be assessed through its own mechanisms. ^R24

China’s rules combine assistance with cryptographic protection

The Chinese comparison requires reading two sets of provisions together. Since the amendment that took effect on January 1, 2026, the general obligation to provide technical assistance appears in Article 30 of the Cybersecurity Law, formerly Article 28. It requires network operators to support public security and state security bodies in their lawful national security and criminal investigation activities. The renumbering resulted from the insertion of new articles; the assistance obligation predates 2026. ^R15R16

The Counterterrorism Law is more explicit about the technology. Article 18 refers to the technical interfaces and decryption assistance expected of telecommunications operators and internet service providers for the lawful prevention and investigation of terrorist activities covered by the law. It describes neither a universal key nor a single architecture imposed on every product. The details of a request and its implementation have to be established separately. ^R17

Alongside these duties, the Cryptography Law provides for lawful use of commercial cryptography and protections for certain proprietary information. It also prohibits forced transfers of commercial cryptographic technology through administrative means. These provisions have to be read alongside the assistance obligations; they do not establish a general exemption from every decryption request. ^R18

The 2025 regulation on critical information infrastructure gives this protective policy a practical form. Effective since August 1, 2025, it requires, among other things, qualified personnel for key management, operations and auditing, funding for cryptographic activities, and assessments before operation and at least annually afterward. Regulatory scrutiny of a key management mechanism does not establish that the secret values of the keys are handed over. ^R19

These Chinese government texts document written obligations. They cannot, on their own, reconstruct providers’ architectures or confidential practices. Their economic significance is that the state can require both cooperation with its agencies and sustained investment in cryptographic security. For a business within their scope, both requirements form part of its operating framework. How they fit together in practice depends on the requests, the product and the conditions of oversight.

Public budgets cover some of the bill

The picture of a provider left to fund every form of cooperation alone is too simple. Under Article R. 873-1 of France’s Internal Security Code, the full costs of implementing L. 871-1 are met from the budget of the prime minister’s services, provided they have actually been incurred and are duly substantiated. The provision sets a funding rule; it supplies no figure for actual expenditure. ^R08

The Postal and Electronic Communications Code also distinguishes different kinds of work. Within the scope of Article D. 98-7, studies, engineering, design and deployment, as well as maintenance or rental, are covered by an agreement with the state. Processing requests is subject to rates set by ministerial order. The same framework requires the relevant minister to approve the technical choices. ^R13

Funding therefore attaches to defined tasks: building capabilities, maintaining them and handling a request. Agreements and tariffs allocate certain costs between the business and the state. For the economy as a whole, the work still has to be done; reimbursement changes who finances it.

The United States also provides for cost payments under CALEA. Section 1008 distinguishes equipment by deployment date and makes payments conditional on matters including available appropriations and, where applicable, a determination of whether compliance is reasonably achievable. It does not provide general insurance against every economic consequence of an access mechanism. ^R05

One figure shows why keeping these scopes separate matters. The U.S. report for 2025 publishes an average cost of $92,963 in current dollars, covering 804 authorizations with reported cost data, for installing and monitoring wiretaps. The reporting instructions allow some expenditure associated with several related wiretaps to be grouped on a single form. This average describes the operations reported within that framework. It provides no measure of the additional cost of introducing a backdoor. ^R01R02

Estimating that additional cost would require comparing a service with and without the proposed capability: design work, operations, oversight, replacement of components, incidents attributable to the change, and customers’ responses. Observed compliance expenditure supplies only part of that comparison. The reimbursement provisions cited do not put a price on a customer’s loss of confidentiality or its possible commercial consequences.

This investigation therefore produces no worldwide monetary total. The verified documents support a more precise conclusion: cooperation has direct costs that the law can allocate; creating an additional capability requires its own technical and economic assessment. Adding figures that measure other things would give a hypothesis the appearance of measurement.

Assessing the consequences of an additional reader

A proposal for access can be examined by following how it would work. What information can the provider already read? What new capability would it have to acquire? Who can activate it, change its target or destination, and then verify what happened? What becomes of it when the authorization ends? These questions connect promised safeguards to actions that can be checked.

The investigators’ argument remains: access to certain communications may supply evidence they lack. The economic response is to examine the means needed to obtain that benefit and how their costs would be shared. The arrangements for separation, oversight and funding show how concrete that discussion can become. They also set a standard for scrutiny: a lasting capability calls for assessment over its entire life, including its authorized users, its administrators and the people whose data it could expose.

The signature on an authorization begins the process. Control of the infrastructure determines what follows.

Reading guide

End-to-end encryption: protection designed so that the endpoints of a conversation hold the means to read its content. Devices and their copies retain their own security considerations. ^R27 Plaintext: content in readable form, before encryption or after decryption. Control plane: the functions that decide on and activate an operation. Audit log: records intended to support examination of what happened. Least privilege: limiting technical permissions to the operations needed for a role. ^R23R22

Method and scope

This documentary investigation is current to November 7, 2026, covering the legislation, statistics and specifications accessible by that date. The references distinguish publication dates, effective dates and statistical periods. Chinese documents are read as government sources for written legal requirements; their explanatory translations are l0g’s own. The investigation contains no invented interview and does not audit a commercial infrastructure. The mechanism diagrams are teaching models; only the wiretap chart represents observed counts. The references explain the passages used and the scope of each document.

Further reading

The sixth part on alternative routes to evidence examines available sources, investigative resources and the work of establishing evidence.

The fifth part on hijacked access and damage distinguishes affected capabilities, recovery and the distribution of losses.

The fourth part on iCloud, borders and switching costs examines safeguards, contracts and migration planning.

The first part on Parliament’s proposed encryption safeguard examines the French proposal. The second part on devices and backups follows copies of a business secret. The glossary also explains end-to-end encryption and backdoors.

The sharing image depicts an authorisation activating a mechanism for access to communications, with a separate oversight circuit. The visual metaphor depicts no actual installation.

Sources

1. R01 · Administrative Office of the U.S. Courts · 2026-06-30 · Accessed 7 November 2026Wiretap Report 2025
   Passages and scope

   Judicial report covering 2025, published on 30 June 2026: 296 federal wiretaps encountered encryption, with 269 reported failures to obtain plaintext; the state figures are 229 and 217. It lists 249 federal and 80 state authorizations without a corresponding prosecutor report. The published average of $92,963 covers 804 authorizations with cost data for installation and monitoring. The figures describe submitted reports, subject to coverage limits.

   Additional primary document

   Additional primary document

2. R02 · Administrative Office of the U.S. Courts · Accessed 7 November 2026Guidance for Completing Non-Federal WT-2 Wiretap Reports : Updated September 2024
   Passages and scope

   Non-federal WT-2 guidance, updated September 2024: encryption fields 10F and 10G, combined costs for some related wiretaps, and code 01109 defaulting a missing answer about inability to obtain plaintext to “No”. The reviewed documents do not quantify the use of this default in 2025. The documented state-reporting rule should not be assumed to apply to federal reports.

3. R03 · Office of the Law Revision Counsel, U.S. House of Representatives · Accessed 7 November 202647 U.S.C. §1002 : Assistance capability requirements
   Passages and scope

   CALEA section 1002: assistance capabilities for covered carriers and limits concerning system design and information services. Its decryption provision depends on encryption supplied by the carrier and possession of the necessary information. This section has its own scope within US law.

   Additional primary document

   Additional primary document

4. R04 · Office of the Law Revision Counsel, U.S. House of Representatives · Accessed 7 November 202647 U.S.C. §1004 : Systems security and integrity
   Passages and scope

   CALEA section 1004: lawful authorization and affirmative intervention by a carrier officer or employee to activate interception within switching premises. Its reference to 47 U.S.C. §229(b)(2) concerns rules requiring secure and accurate records. Written duties and their actual implementation require separate assessment.

   Additional primary document

5. R05 · Office of the Law Revision Counsel, U.S. House of Representatives · Accessed 7 November 202647 U.S.C. §1008 : Payment of costs of telecommunications carriers
   Passages and scope

   CALEA section 1008: payment mechanisms, distinctions according to equipment deployment date and conditions including available appropriations and reasonable achievability. It addresses specified compliance costs rather than general compensation for every economic consequence.

6. R06 · Légifrance / République française · Accessed 7 November 2026French Internal Security Code : Title VII, duties of operators and providers, Articles L. 871-1 to L. 871-7
   Passages and scope

   Internal Security Code article L. 871-1: provision of decryption conventions by covered providers and, in the second sentence, their implementation with the provider’s ability to demonstrate technical inability. The two duties and their conditions need to be distinguished. Other articles in the title supplement the cooperation framework.

   Additional primary document

7. R07 · Légifrance / République française · 2016-01-31 · Accessed 7 November 2026French Internal Security Code : Articles R. 871-1 to R. 871-5, cryptographic assistance duties
   Passages and scope

   Articles R. 871-1 to R. 871-5: procedure for decryption conventions, a written and reasoned decision by the Prime Minister or delegate, notification to the provider and communication to the CNCTR chair. Authorization, notification and oversight retain distinct purposes.

8. R08 · Légifrance / République française · 2016-01-31 · Accessed 7 November 2026French Internal Security Code : Article R. 873-1, funding implementation of L. 871-1
   Passages and scope

   Article R. 873-1: the Prime Minister’s services budget covers all actually incurred and duly justified costs of implementing L. 871-1. It establishes a funding rule within its scope and provides no observed expenditure amount.

9. R09 · Légifrance / République française · 2016-06-04 · Accessed 7 November 2026French Criminal Code : Article 434-15-2
   Passages and scope

   Criminal Code article 434-15-2: conditions governing refusal to provide or implement a secret decryption convention known to the person required to cooperate. That knowledge is a determining element of the provision.

10. R10 · Conseil constitutionnel, texte intégral diffusé par Légifrance · 2018-03-31 · Accessed 7 November 2026French Constitutional Council : Decision No. 2018-696 QPC, M. Malek B.
    Passages and scope

    Decision 2018-696 QPC of 30 March 2018: review of the challenged first paragraph of article 434-15-2. The reasoning addresses knowledge of the decryption convention and the already identified data covered by the request. Its scope remains the provision examined.

11. R11 · Légifrance / République française · Accessed 7 November 2026French Code of Criminal Procedure : Articles 706-95-11 to 706-95-19, common provisions for special investigative techniques
    Passages and scope

    Criminal Procedure Code articles 706-95-11 to 706-95-19: common provisions for special investigative techniques, including authorization and oversight according to the procedural setting. Appointing a technical implementer remains distinct from authorizing the measure. The code provides an urgency exception allowing the investigating judge to act before the prosecutor’s opinion.

12. R12 · Légifrance / République française · Accessed 7 November 2026French Code of Criminal Procedure : Articles 706-102-1 to 706-102-5, capture of computer data
    Passages and scope

    Articles 706-102-1 to 706-102-5: computer-data capture under criminal procedure. Covered categories include stored, displayed and typed data and data received by specified peripherals. The endpoint can therefore provide access to content.

13. R13 · Légifrance / République française · 2023-11-03 · Accessed 7 November 2026French Postal and Electronic Communications Code : Articles D. 98-3 and D. 98-7, scope and means of cooperation
    Passages and scope

    Postal and Electronic Communications Code articles D. 98-3 and D. 98-7: scope of cooperation capabilities, approval of technical choices and funding. D. 98-7 IV distinguishes an agreement for specified work or capabilities from rates set by order for processing requests.

14. R14 · Commission nationale de contrôle des techniques de renseignement (CNCTR) · Accessed 7 November 2026Oversight of the implementation of intelligence techniques
    Passages and scope

    Institutional description of CNCTR oversight of intelligence-technique implementation: on-site and remote checks and access to intelligence and records within its remit. It describes the commission’s oversight rather than auditing a particular architecture.

15. R15 · Comité permanent de l’Assemblée populaire nationale ; republication par la Cyberspace Administration of China (CAC), source indiquée : China NPC · 2025-12-29 · Accessed 7 November 2026Cybersecurity Law of the People’s Republic of China : consolidated after the 2025 amendment
    Passages and scope

    China’s Cybersecurity Law as consolidated after the 2025 amendment: article 30 contains the technical-support and assistance duty for the competent authorities’ lawful activities. The text establishes a written duty; provider-specific implementation requires further evidence.

16. R16 · Comité permanent de l’Assemblée populaire nationale ; republication CAC, source indiquée : Xinhua · 2025-10-29 · Accessed 7 November 2026Decision of the Standing Committee of the National People’s Congress amending the Cybersecurity Law
    Passages and scope

    2025 decision amending China’s Cybersecurity Law, effective 1 January 2026: insertion and renumbering of articles. The former article 28 assistance duty becomes article 30; the obligation predates that effective date.

17. R17 · Comité permanent de l’Assemblée populaire nationale ; reproduction du ministère de l’Industrie et des Technologies de l’information (MIIT) · 2022-01-29 · Accessed 7 November 2026Counterterrorism Law of the People’s Republic of China : as amended in 2018
    Passages and scope

    China’s Counterterrorism Law, article 18, as amended in 2018: technical interfaces and decryption assistance from telecom operators and internet providers for the covered lawful activities. Design and implementation conditions require separate examination.

    Additional primary document

18. R18 · Comité permanent de l’Assemblée populaire nationale ; reproduction de l’autorité nationale chargée de la cryptographie, source indiquée : China NPC · 2019-10-28 · Accessed 7 November 2026Cryptography Law of the People’s Republic of China and Promulgation Order No. 35
    Passages and scope

    China’s Cryptography Law: lawful use of commercial cryptography, protection of specified proprietary information and prohibition of forced transfer of that technology through administrative means. These provisions must be read alongside other applicable legal duties.

    Additional primary document

19. R19 · Autorité nationale de la cryptographie (NCA), Cyberspace Administration of China et ministère de la Sécurité publique · 2025-06-27 · Accessed 7 November 2026Provisions on the Use of Commercial Cryptography in Critical Information Infrastructure : Joint Order No. 5
    Passages and scope

    Chinese rules on commercial cryptography in critical information infrastructure, effective 1 August 2025: qualified staff, funding and security assessments, including before operation and at least annually thereafter. Assessing key management and disclosing secret key values remain distinct operations.

20. R20 · European Telecommunications Standards Institute (ETSI) · 2026-08 · Accessed 7 November 2026ETSI TS 104 007 V1.3.1 : Lawful Interception (LI); Lawful Interception Architecture
    Passages and scope

    ETSI TS 104 007, version 1.3.1, August 2026: roles, flows and lifecycle of lawful interception. Transition to the inactive state preserves an exception for delivery of previously captured communications. Separating trust domains uses network and personnel resources. The standard provides a technical architecture; applicable law determines legal powers.

    Additional primary document

21. R21 · European Telecommunications Standards Institute (ETSI) · 2026-08 · Accessed 7 November 2026ETSI TS 102 232-1 V3.38.1 : Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery
    Passages and scope

    ETSI TS 102 232-1, version 3.38.1, August 2026: IP delivery of intercepted information, including payload-encryption mechanisms and transport protection. Encrypting delivery is a separate problem from obtaining readable original content.

22. R22 · National Institute of Standards and Technology (NIST) · 2020-09 · Accessed 7 November 2026NIST SP 800-53 Rev. 5 : Security and Privacy Controls for Information Systems and Organizations
    Passages and scope

    NIST SP 800-53, revision 5: AC-5 on separation of duties, AC-6 on least privilege and AU-9 on protecting audit information, including separate storage and restricted administration. The publication page also announces the August 2025 catalogue release 5.2.0. These controls provide a framework for adaptation; citing them establishes their content rather than actual deployment.

    Additional primary document

    Additional primary document

23. R23 · NIST ; Scott Rose, Oliver Borchert, Stu Mitchell et Sean Connelly · 2020-08 · Accessed 7 November 2026NIST SP 800-207 : Zero Trust Architecture
    Passages and scope

    NIST SP 800-207, August 2020, section 3: policy engine, policy administrator and enforcement point, with logical separation of control and data planes. The article uses these concepts in an explanatory model; this general security framework confers no interception powers.

    Additional primary document

24. R24 · Harold Abelson et al. ; MIT Computer Science and Artificial Intelligence Laboratory · 2015-07-07 · Accessed 7 November 2026Keys Under Doormats: Mandating insecurity by requiring government access to all data and communications
    Passages and scope

    MIT presentation of 7 July 2015 and record for report MIT-CSAIL-TR-2015-026: the authors analyse complexity, cryptographic guarantees and governance challenges associated with exceptional access. This is a technical argument, with no monetary estimate used here and no validation of a particular implementation.

    Additional primary document

25. R25 · Administrative Office of the U.S. Courts · Accessed 7 November 2026FAQs : Wiretap Reports
    Passages and scope

    Judicial FAQ on reporting scope: Title III interceptions, exclusion of FISA interceptions, reporting schedule and categories outside collection. It clarifies statistical coverage and bounds interpretation of the 2025 data.

26. R26 · Federal Bureau of Investigation · 2025-04-24 · Accessed 7 November 2026FBI Seeking Tips about PRC Targeting of U.S. Telecommunications
    Passages and scope

    FBI alert of 24 April 2025, also published by IC3: Salt Typhoon attributed to PRC-affiliated actors, theft of call logs and some communications, and copying of information subject to court-ordered requests. These findings are attributed to US authorities. The alert establishes neither a universal intrusion route nor a break in end-to-end encryption.

    Additional primary document

27. R27 · IETF / RFC Editor ; Beurdouche et al. · 2025-04 · Accessed 7 November 2026RFC 9750 : The Messaging Layer Security (MLS) Architecture
    Passages and scope

    RFC 9750, the April 2025 informational MLS architecture: content protection, multiple devices, transport and limits concerning application-retained histories. Adding a device and restoring earlier messages are distinct functions. Scope depends on the protocol and the application’s own functions.

    Additional primary document