Azure Security Benchmark
Data Protection

Azure Security Benchmark DP-3: Encrypt sensitive data in transit

Enforce TLS 1.2 or higher for all data in transit and disable legacy protocols across Azure services.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 57 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CMMC 2.0 · 4 controls

FedRAMP High · 4 controls

  • AC-17(2) Protection of Confidentiality and Integrity Using Encryption
  • SC-13 Cryptographic Protection
  • SC-8 Transmission Confidentiality and Integrity
  • SC-8(1) Cryptographic Protection

FedRAMP Moderate · 4 controls

  • AC-17(2) Protection of Confidentiality and Integrity Using Encryption
  • SC-13 Cryptographic Protection
  • SC-8 Transmission Confidentiality and Integrity
  • SC-8(1) Cryptographic Protection

ISO 27701:2019 · 4 controls

  • 6.10.2 Information transfer
  • 6.11.1 Security requirements of information systems
  • 7.4.9 PII transmission controls
  • 8.4.3 PII transmission controls

NIST SP 800-171 Rev 3 · 4 controls

PCI DSS 4.0 · 4 controls

  • 12.3.3 12.3.3 Cryptographic cipher suite and protocol inventory reviewed annually
  • 2.2.7 2.2.7 Non-console administrative access encrypted
  • 4.2.1 4.2.1 Strong cryptography safeguards PAN over public networks
  • 8.3.2 8.3.2 Authentication factors unreadable with strong cryptography
  • ANSSI-HYG-18 Encrypt Sensitive Data Transmitted Over the Internet
  • ANSSI-HYG-21 Use Secure Protocols Wherever They Exist
  • ANSSI-HYG-32 Secure the Network Connection of Devices Used for Mobile Working

HIPAA Security Rule · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

NIST SP 800-66 Rev 2 · 3 controls

  • AUCDR-IS-2 Secure the network and systems within the data environment
  • AUCDR-PS-12 Privacy Safeguard 12 - Security of CDR data and destruction or de-identification of redundant CDR data

C5 (Germany) · 2 controls

  • C5-COS-08 Policies for data transmission
  • C5-CRY-02 Encryption of data for transmission (transport encryption)

CIS Controls v8 · 2 controls

  • CIS-12.6 Use of Secure Network Management and Communication Protocols
  • CIS-3.10 Encrypt Sensitive Data in Transit

ISO 27001:2022 · 2 controls

  • 5.14 Information transfer
  • 8.24 Use of cryptography

ISO 27002:2022 · 2 controls

  • 5.14 Information transfer
  • 8.24 Use of cryptography
  • CBPR-PR-27 Physical, technical and administrative safeguards
  • ASD37-17 TLS encryption between email servers (Limited)
  • NIST-CSF-PR.DS-02 The confidentiality, integrity, and availability of data-in-transit are protected
  • 161R1-SC-8 Transmission Confidentiality and Integrity

NIST SP 800-172 · 1 control

  • 3.1.3e Employ Secure Information Transfer Solutions

SOC 2 · 1 control

  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Data Protection

You are reading one control. How much of Azure Security Benchmark have you already done?

Azure Security Benchmark DP-3 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Azure Security Benchmark your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 71 of 85 Azure Security Benchmark controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 57 it maps to, and the evidence behind each claim, over MCP and REST.