A provider that runs one encrypted service in several countries can face lawful access rules that pull its architecture in different directions, and most of the notices involved are secret. The UK Investigatory Powers Act 2016, Australia's Assistance and Access Act 2018, the proposed EU Child Sexual Abuse Regulation and the US CLOUD Act and CALEA all touch the same question: what can a government make a provider do about data it has encrypted? This comparison sets the four regimes side by side by instrument, encryption limit, secrecy, oversight and penalty, then explains the threat model and design consequences of each and works through scenarios a multinational provider will recognise. It is for security architects, product security and legal teams at messaging, cloud, device and telecoms providers, and for enterprise buyers. Status line: checked against legislation.gov.uk, the Federal Register of Legislation (Australia), the European Parliament Legislative Observatory, the Council of the EU and the US Code on 14 November 2026.
Key takeaways
- The short answer differs by country. The UK can require removal of electronic protection the operator itself applied; Australia expressly forbids requiring a systemic weakness or new decryption capability; the EU proposal is unadopted and both co-legislators' positions keep encrypted services out of mandatory detection; US law does not require providers to be able to decrypt.
- Key custody is the variable that matters everywhere. UK s.253(5), US 47 U.S.C. 1002(b)(3) and the CLOUD Act's possession, custody or control test all turn on what the provider itself holds, so who holds keys decides exposure more than where data sits.
- Secrecy is built in. UK recipients may not disclose a technical capability or notification notice without permission, and Australian disclosure of notice information is an offence carrying up to five years' imprisonment, which limits what providers can tell customers.
- Change governance is now regulated in the UK. Since 20 June 2025 a UK notification notice can require an operator to tell the Home Secretary before making specified changes to its services, which reaches security roadmaps, not only intercept.
- The EU file is moving but not law. The CSA Regulation proposal of 11 May 2022 is in trilogue; a separate interim regulation allowing voluntary detection runs until 3 April 2028 and does not apply to end-to-end encrypted communications.
Regulations and frameworks at a glance
Instruments follow the order of the title; detailed single-law guides are linked below.
| Instrument | Jurisdiction | Encryption-relevant tool | Who decides and approves | Status as of 14 November 2026 |
|---|---|---|---|---|
| Investigatory Powers Act 2016, Part 9 (ss.253, 255, 258A) | United Kingdom | Technical capability notice (TCN), which may include removal of electronic protection applied by or on behalf of the operator; notification notice for proposed changes | Secretary of State; TCN also needs Judicial Commissioner approval | In force; 2024 amendments in force from 14 October 2024, notification notices from 20 June 2025 |
| Online Safety Act 2023, s.121 | United Kingdom | Ofcom notice to use accredited technology to identify child sexual exploitation and abuse (CSEA) content, whether communicated publicly or privately | Ofcom, after a skilled person's report and a warning notice | Section in force from 10 January 2024 |
| Telecommunications and Other Legislation Amendment (Assistance and Access) Act 2018 (Part 15, Telecommunications Act 1997) | Australia | Technical assistance request (TAR), technical assistance notice (TAN), technical capability notice (TCN), all limited by the s.317ZG systemic weakness prohibition | Agency heads for TAR and TAN; Attorney-General for TCN, with the Minister's approval | In force |
| Proposed Regulation laying down rules to prevent and combat child sexual abuse, COM(2022) 209, procedure 2022/0155(COD) | European Union | Risk assessment and mitigation, removal and blocking orders; detection orders in the Commission text | National competent authorities, supported by a new EU Centre | Proposal; Parliament mandate November 2023, Council position 26 November 2025, trilogues since 9 December 2025 |
| Regulation (EU) 2026/1881 (interim voluntary detection) | European Union | Temporary derogation allowing voluntary detection by providers | Providers, voluntarily | Published 28 July 2026, applies until 3 April 2028, excludes end-to-end encrypted communications |
| CLOUD Act 2018 (18 U.S.C. 2713, 2523) | United States | Disclosure of data in the provider's possession, custody or control regardless of location; executive agreements | US courts under the Stored Communications Act; Attorney-General certifies agreements | In force since 23 March 2018 |
| CALEA 1994 (47 U.S.C. 1001 to 1010) | United States | Interception capability for telecommunications carriers, with an express encryption carve-out in 1002(b)(3) | Courts and the FCC | In force |
How the four regimes compare on encryption
The question practitioners actually ask is whether a government can force an encryption backdoor. The answer depends on four design points, compared here.
| Question | UK (IPA and OSA) | Australia (Assistance and Access) | EU (CSA proposal) | US (CLOUD Act and CALEA) |
|---|---|---|---|---|
| Can the state require decryption? | A TCN may impose obligations relating to removal by the operator of electronic protection applied by or on behalf of that operator (s.253(5)), subject to necessity, proportionality, feasibility and cost tests | A notice must not require a systemic weakness or vulnerability in a form of electronic protection, including a new decryption capability (s.317ZG) | Parliament excluded end-to-end encryption from detection orders; the Council position contains no mandatory detection orders | No duty to decrypt subscriber-applied encryption unless the carrier provided it and holds the means (47 U.S.C. 1002(b)(3)); executive agreements may not create an obligation to be capable of decrypting (2523(b)(3)) |
| Can the state mandate a design? | Obligations come from regulations that must be reasonable and practicable (s.253(4)); notification notices reach planned changes (s.258A) | Must not prevent a provider rectifying a systemic weakness (s.317ZG); no standing obligations on industry | Providers choose technology subject to safeguards and audit in the Parliament text | CALEA does not authorise requiring any specific design or prohibiting any feature (1002(b)(1)) |
| Who is reached? | Postal and telecommunications operators, including persons outside the UK (s.253(8)); OSA reaches regulated user-to-user and search services | Designated communications providers, including software developers, device suppliers and providers of electronic services with end-users in Australia (s.317C) | Online service providers, classified into high, medium and low risk categories (Council position) | Electronic communication and remote computing service providers (CLOUD Act); carriers, broadband and interconnected VoIP (CALEA) |
| Secrecy | No disclosure of a TCN or national security notice without permission (s.255(8)); same for notification notices (s.258A(8)) | Unauthorised disclosure of notice information is an offence, up to 5 years' imprisonment (s.317ZF) | Removal, blocking and delisting orders are issued by national competent authorities (Council position) | Stored Communications Act process may carry non-disclosure orders; see the ECPA guide |
| Independent check | Judicial Commissioner approval of TCNs (double lock) | Minister's approval for TCNs (s.317TAAA); optional assessment by a technical expert and a former judge (s.317WA) | National competent authorities, supported by the EU Centre; Parliament text adds independent public audit of detection technology | Court-issued warrants and orders; comity motion for conflicts with qualifying foreign law |
| Consequence of non-compliance | Civil proceedings by the Secretary of State for an injunction or specific performance (s.255(10)) | Civil penalty up to 47,619 penalty units for a body corporate, 238 otherwise (s.317ZB) | Penalty payments for failing risk mitigation duties (Council position) | Court enforcement of orders; CALEA civil penalties (see the CALEA guide) |
United Kingdom: capability notices and notification of change
Threat model: the UK model assumes the state may need to reach content from services that operators already handle in the clear or can decrypt, and that operators might otherwise design that ability away. The TCN keeps a capability in place; the notification notice gives the Home Office advance sight of changes that could remove it. For section-by-section detail see the UK Investigatory Powers Act Guide for Security Teams.
- Architecture in words: a warrant authorises access; a TCN makes sure the operator can assist when the warrant arrives. The obligation list in s.253(5) includes providing facilities, handling apparatus, removing electronic protection the operator applied, maintaining security and handling information. Reach is extraterritorial: notices may go to persons outside the UK and require conduct outside it (s.253(8)).
- Safeguards: the Secretary of State must consult the recipient and weigh benefits, technical feasibility, cost and other effects, with particular regard to feasibility and cost where removal of electronic protection is involved (s.255(2) to (4)).
- Second lever: Ofcom can require a regulated user-to-user service to use accredited technology to identify CSEA content communicated privately (OSA s.121), after a skilled person's report (s.122) and a warning notice (s.123). This is content moderation, separate from IPA intercept. See the UK Online Safety Act.
- Failure modes for providers: shipping an encryption change without checking whether a notification notice applies; key management where the operator holds content keys by default, which is exactly the "electronic protection applied by or on behalf of" the operator; and incident or transparency communications that would reveal a notice.
Australia: assistance notices bounded by a systemic weakness test
Threat model: the Australian model accepts that agencies want help from a wide range of providers, but writes a hard limit into the statute so that help cannot weaken security for everyone. The Home Affairs overview says the framework cannot require backdoors or anything that would make communications of innocent persons less secure, and cannot be used to access communications without an existing warrant or authorisation. For the related network security obligations see Australia Telecommunications Sector Security Reforms (TSSR).
| Instrument | Given by | Nature | Key procedural point |
|---|---|---|---|
| TAR (s.317G) | Director-General of Security, of ASIS or of ASD, or the chief officer of an interception agency | Voluntary | The provider must be told compliance is voluntary (s.317HAA) |
| TAN (s.317L) | Director-General of Security or the chief officer of an interception agency | Compulsory, using existing capability | A state or territory agency needs the AFP Commissioner's approval first (s.317LA) |
| TCN (s.317T) | Attorney-General, on request of the Director-General of Security or an interception agency chief officer | Compulsory, can require a new capability | Minister's written approval (s.317TAAA); consultation of at least 28 days (s.317W); optional two-person assessment (s.317WA) |
- The limit: s.317B defines a systemic weakness as one that affects a whole class of technology, and excludes a weakness selectively introduced to one or more target technologies. Section 317ZG says a notice or request must not have the effect of requiring a systemic weakness or vulnerability in a form of electronic protection, including a new decryption capability, and must not prevent a provider fixing one.
- Warrant boundary: a notice has no effect where the act would need a warrant or authorisation under listed laws such as the Telecommunications (Interception and Access) Act 1979 (s.317ZH).
- Costs: providers comply on a no-profit, no-loss basis unless agreed otherwise, with terms set by a costs negotiator or arbitrator (s.317ZK).
- Failure modes for providers: treating "selectively introduced to a target technology" as automatically safe without assessing spill-over to other users; not requesting a s.317WA assessment when a TCN proposal touches cryptography; and missing that software developers and device suppliers count as designated communications providers.
European Union: the CSA Regulation proposal and the interim regime
Threat model: the EU file is not about intercept warrants. It targets the spread of child sexual abuse material and grooming on hosting and messaging services, and the encryption debate arises from whether detection can be mandated on services the provider cannot read. Treat everything here as provisional: the Legislative Observatory shows the file still awaiting Parliament's first reading position.
- Commission proposal: COM(2022) 209 of 11 May 2022 proposed risk assessment, detection orders and an EU Centre on Child Sexual Abuse.
- Parliament mandate (November 2023): the LIBE committee report excluded end-to-end encryption from detection orders to keep communications secure and confidential, made detection orders a last resort, and let providers choose technologies subject to safeguards and an independent public audit.
- Council position (26 November 2025): three risk categories (high, medium, low), risk assessment and mitigation duties, removal, blocking and delisting orders, permanent voluntary detection, and the EU Centre. Reporting on the position notes it excludes mandatory detection orders, including for encrypted services.
- Interim regime: the earlier temporary derogation lapsed on 3 April 2026. Regulation (EU) 2026/1881 restored voluntary detection from its entry into force after publication on 28 July 2026, until 3 April 2028, and does not apply to end-to-end encrypted communications.
- Failure modes for providers: planning on the 2022 text rather than current positions, and assuming the interim regime covers encrypted messaging.
United States: data control and carrier capability
Threat model: US law reaches what a provider controls and what a carrier can intercept, but it has repeatedly declined to make providers able to decrypt. The question for a provider is therefore what it holds in a usable form. Detailed guides: CLOUD Act Guide, CALEA and US Electronic Communications Privacy Act and Stored Communications Act Guide for Security Teams.
- CLOUD Act: 18 U.S.C. 2713 requires electronic communication and remote computing service providers to preserve, back up or disclose communications and records in their possession, custody or control, whether stored inside or outside the United States.
- Executive agreements: 18 U.S.C. 2523 lets the Attorney-General, with the Secretary of State, certify agreements under which a foreign government can serve orders directly on US providers. Such an agreement "shall not create any obligation that providers be capable of decrypting data", nor stop them decrypting (2523(b)(3)).
- CALEA: carriers must be able to isolate and deliver communications and call-identifying information, but CALEA does not authorise requiring any specific design or prohibiting any feature (1002(b)(1)), and a carrier is not responsible for decrypting subscriber encryption unless it provided the encryption and holds the information needed to decrypt (1002(b)(3)).
- Failure modes for providers: offering "encryption" where the provider manages the keys and assuming that removes CLOUD Act exposure; carriers offering a carrier-provided encryption feature without recognising the 1002(b)(3) consequence; and weak security around intercept platforms, covered in Lawful Intercept System Security.
Worked scenarios
Scenario 1: end-to-end encrypted messaging app with UK, Australian, EU and US users. Keys live only on user devices. In the US, there is no content the provider can decrypt, so 2713 reaches metadata and account records it holds. In Australia, a TCN cannot require a new decryption capability that amounts to a systemic weakness. In the EU, both co-legislators' positions keep encrypted services out of mandatory detection, though risk assessment duties will apply. In the UK, the main exposure is a TCN or a notification notice covering a planned change: the provider should route encryption roadmap decisions through legal review before release and plan for secrecy obligations.
Scenario 2: SaaS provider with provider-managed encryption at rest. The provider holds the keys, so data is in its possession, custody or control for CLOUD Act purposes, and in the UK the protection is applied "by or on behalf of" the operator. Moving to customer-held keys (hold your own key) changes both answers. See the BYOK, HYOK and External Key Management Guide.
Scenario 3: mobile carrier offering a carrier-branded encrypted calling feature. Under CALEA 1002(b)(3) the carrier-provided encryption, with the carrier holding keys, falls inside its decryption responsibility. In Australia the carrier is a designated communications provider and can receive TANs. The design choice is whether the carrier should hold keys at all.
Decision guidance and trade-offs
| Design choice | Effect on lawful access exposure | Trade-off |
|---|---|---|
| End-to-end encryption, keys on endpoints | Least content the provider can be compelled to produce in all four regimes | Harder account recovery, server-side search, abuse detection and backup; metadata still reachable |
| Customer-held keys (HYOK or external key manager) | Shifts control of content keys to the customer; changes the possession, custody or control analysis | Customer operational burden; some service features unavailable |
| Provider-managed keys with strong access controls | Provider can be compelled; strong internal controls protect against misuse, not compulsion | Simplest operations; highest compellability |
| Data minimisation and short retention | Less metadata exists to disclose under any regime | Weaker forensics and analytics; check retention notices and sector rules |
| Separate legal entities per region | May affect which entity holds data; does not defeat control tests on its own | Cost and complexity; group control can still reach data |
Small providers: start by mapping key custody and the data you could hand over; most small SaaS firms are reached through the CLOUD Act style control test and through Australia's broad provider definition rather than through capability notices. Large providers: run a standing lawful access function that reviews cryptographic changes, runs the secrecy process and records decisions with counsel.
Where identity fits
Lawful access touches the machine identities that hold or broker keys. Service accounts with decrypt rights, workload identities on disclosure platforms and AI agents that read customer content are, in practice, the provider holding the means to decrypt. Scope those identities tightly, log every decrypt and export operation, and require two-person approval for any action taken to satisfy a legal order. See the Encryption and Key Management Requirements Map for the mandates to encrypt that sit beside these access rules.
Compliance steps
- Inventory key custody: for each product, record who generates, stores and can use content keys, and which identities can call decrypt.
- Map jurisdictions: record whether each entity could be a UK telecommunications operator, an Australian designated communications provider, an EU hosting or messaging provider, or a US ECS, RCS or carrier.
- Build a legal order process: one intake route, counsel review, a secrecy register for notices that cannot be disclosed, and evidence of every action taken.
- Gate cryptographic change: add a lawful access review to change management for anything that alters encryption, key custody or logging, and keep the review record.
- Prepare for the EU text: start the service risk assessment now, since every version of the proposal requires one.
- Test and review: rehearse an order in a tabletop and review yearly.
Detection and measurement
- Decrypt events by privileged identities: volume of key management decrypt and export calls by identities outside normal workloads, reviewed weekly.
- Order handling time: median days from order receipt to counsel decision.
- Change coverage: percentage of cryptographic changes with a recorded lawful access review (target 100 percent).
- Key custody coverage: percentage of products with a current key custody record.
Common failure patterns
- Treating "encrypted" as "unreachable": provider-managed encryption is reachable under the CLOUD Act and within UK s.253(5) because the provider applied it.
- Leaking a secret notice through routine communications: release notes, transparency reports or support replies that reveal a UK or Australian notice can breach s.255(8) or s.317ZF.
- Ignoring the change notification route: UK operators that have assisted under the Act can be told to notify planned changes; skipping legal review of encryption releases creates avoidable conflict.
- Overbroad decrypt rights: service accounts and agents with standing decrypt access widen what can be compelled and what an attacker can take.
Practitioner checklist
- Key custody recorded for every product, including backups and logs.
- Jurisdiction map showing which of the four regimes reaches each legal entity.
- Legal order intake, counsel review and secrecy register in place.
- Lawful access review step in cryptographic change management.
- Decrypt and export permissions limited to named workloads, with two-person approval for order-driven actions.
- Metadata retention minimised and documented.
- EU CSA risk assessment drafted against current negotiating texts.
Standards and references
- legislation.gov.uk: Investigatory Powers Act 2016, section 253 Technical capability notices
- legislation.gov.uk: Investigatory Powers Act 2016, section 258A Notices requiring notification of proposed changes
- Federal Register of Legislation: Telecommunications Act 1997, Volume 2 (Part 15 Industry assistance)
- Australian Department of Home Affairs: Data encryption and the Assistance and Access Act
- European Parliament Legislative Observatory: Combating child sexual abuse online, 2022/0155(COD)
- Council of the EU: Council reaches position on law protecting children from online abuse
- US Code (Cornell LII): 18 U.S.C. 2713 Required preservation and disclosure regardless of location
- US Code (Cornell LII): 47 U.S.C. 1002 Assistance capability requirements
This guide summarises encryption and lawful access laws in the UK, Australia, the EU and the US for security practitioners and is not legal advice; confirm obligations with counsel and the primary texts. Related NHI Mgmt Group resources: UK Investigatory Powers Act Guide for Security Teams · CLOUD Act Guide · End-to-End Encryption and Messaging Protocols Guide · Client-Side vs Server-Side Encryption