Skip to content

End-to-End Encryption

What is End-to-End Encryption?

Encryption of data throughout its entire journey from sender to recipient, preventing any intermediary from accessing the content.

Information Security

Each of these is named in at least one of the same controls as end-to-end encryption. The number is how many controls name both.

What the standards actually require on end-to-end encryption

Requirements naming end-to-end encryption across 6 standards, quoted from the control text.

Where technically supported, agencies use end-to-end encryption by default for internet-based voice, video conferencing and instant messaging while keeping the logging and archival capabilities they need to meet records management and accountability requiremen...

us-executive-order-14144-strengthening-and-promoting-innovation-in-the-nations-cybersecurity::4(e)(ii) · Sec. 4(e)(ii) Use end-to-end encryption by default while keeping records capability →

Protect communications using end-to-end encryption (preventing intermediaries from accessing content) and traffic-pattern hiding (proxy and onion routing) to limit metadata exposure; choose mechanisms commensurate with the threat model and the data category.

ENISA-DPE-5.1 · Communication channels (end-to-end encryption, proxy/onion routing) →

Not exports, reexports or transfers: launching items into space; transfers of technology or software between persons in the United States who are not foreign persons;

ear-export-administration-regulations::734.18 · 734.18 Activities that are not exports, reexports, or transfers →

Article 7 imposes phased interoperability on Number-Independent Interpersonal Communication Services (N-IICS) designated as CPS: (1) free-of-charge interoperability access on request to any other N-IICS, with messaging functionality (text, image, audio, video)...

DMA-Art.7 · N-IICS interoperability (Article 7) →

Advanced control principles for external connections (required, with baseline and intermediate, of an AI whose inherent risk is high). The security implications of every change to external or third-party connections are validated and documented beforehand;

hkma-cyber-resilience-assessment-framework-c-raf::7.1.A · 7.1 External connections: advanced level →

Questions people ask about end-to-end encryption

What is End-to-End Encryption?
Encryption of data throughout its entire journey from sender to recipient, preventing any intermediary from accessing the content.
Why is End-to-End Encryption important for compliance?
End-to-End Encryption is a key concept in Information Security. Understanding end-to-end encryption helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 1,016 frameworks with 316K cross-framework control mappings.
Which compliance frameworks address End-to-End Encryption?
End-to-End Encryption appears in the requirement text of US Executive Order 14144 - Strengthening and Promoting Innovation in the Nation's Cybersecurity, ENISA Data Protection Engineering - From Theory to Practice, ITU-T X.805 - Security Architecture for End-to-End Communications, EAR - Export Administration Regulations, EU Digital Markets Act. Across these standards we have identified 9 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about End-to-End Encryption?
Explore our compliance framework pages to see how end-to-end encryption applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 1,016 frameworks.

See how End-to-End Encryption applies across compliance frameworks

Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.

Written and maintained by Gerard Blokdyk, The Art of Service.