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.
Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), DP-3. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Storage account secure transfer setting · Identity provider / directory
- App Service HTTPS only configuration · Cloud console / configuration management
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- TLS configuration policy · Policy repository / GRC workspace
First move
Common gaps auditors find
- HTTP allowed on App Service
- TLS 1.0/1.1 still enabled
- Secure transfer required not enforced
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheetDP-2 Monitor anomalies and threats targeting sensitive data · DP-4 Enable data at rest encryption by default