Editing End-to-end encryption (section)

=== Compliance and regulatory requirements for content inspection ===
While E2EE can offer privacy benefits that make it desirable in consumer-grade services, many businesses have to balance these benefits with their regulatory requirements. For example, many organizations are subject to mandates that require them to be able to decrypt any communication between their employees or between their employees and third parties.<ref>{{cite news|title=Why GDPR Makes it Urgent to Scan Encrypted Traffic for Data Loss|url=https://blog.sonicwall.com/en-us/2017/11/why-gdpr-makes-it-urgent-to-scan-encrypted-traffic-for-data-loss/|work=SonicWall|date=28 November 2017}}</ref>
This might be needed for archival purposes, for inspection by [[Data loss prevention software|Data Loss Prevention (DLP)]] systems, for litigation-related [[Electronic discovery|eDiscovery]] or for detection of [[Antivirus software|malware]] and other threats in the data streams. For this reason, some enterprise-focused communications and information protection systems might implement encryption in a way that ensures all transmissions are encrypted with the encryption being terminated at their internal systems (on-premises or cloud-based) so they can have access to the information for inspection and processing.