Azure Security Benchmark
Governance and Strategy

Azure Security Benchmark ASBv3-GS-3: Define and implement data protection strategy

Define and implement an enterprise data protection strategy covering classification and protection standards, key and certificate management, access control and lifecycle handling.

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

What else in your programme already covers this

This control maps to 43 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.

C5 (Germany) · 3 controls

  • C5-AM-06 Asset Classification and Labelling
  • C5-COS-08 Policies for data transmission
  • C5-CRY-01 Policy for the use of encryption procedures and key management

CIS Controls v8 · 3 controls

  • CIS-3.1 Establish and Maintain a Data Management Process
  • CIS-3.3 Configure Data Access Control Lists
  • CIS-3.7 Establish and Maintain a Data Classification Scheme

ISO 27001:2022 · 3 controls

  • 5.1 Policies for information security
  • 5.12 Classification of information
  • 8.24 Use of cryptography

NIST SP 800-53 Rev 5 · 3 controls

PCI DSS 4.0 · 3 controls

  • 4.1.1 4.1.1 Requirement 4 policies and procedures maintained and communicated
  • 3.1.1 3.1.1 Requirement 3 policies and procedures maintained and in use
  • 3.2.1 3.2.1 Data retention and disposal minimise stored account data

APRA CPS 234 · 2 controls

  • SEC07-BP01 Understand your data classification scheme
  • SEC07-BP02 Apply data protection controls based on data sensitivity
  • CCM-DSP-01 Security and Privacy Policy and Procedures
  • CCM-DSP-07 Data Protection by Design and Default

FedRAMP High · 2 controls

  • MP-1 Policy and Procedures
  • SC-1 Policy and Procedures

FedRAMP Moderate · 2 controls

  • MP-1 Policy and Procedures
  • SC-1 Policy and Procedures

HIPAA Security Rule · 2 controls

  • 164.306 Security Standards: General Rules
  • 164.316(a) Policies and Procedures (Standard)

ISO 27002:2022 · 2 controls

  • 5.1 Policies for information security
  • 5.12 Classification of information

ISO 27701:2019 · 2 controls

  • 6.2.1 Management direction for information security
  • 6.5.2 Information classification
  • ANSSI-HYG-04 Identify the Most Sensitive Information and Servers and Maintain a Network Diagram

APPI · 1 control

  • APPI-A46 Security and Proper Handling of Anonymized Personal Information
  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data
  • CFTC-SS-37 Protection of Swap Data Repository Data
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced

SOC 2 · 1 control

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information

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 Governance and Strategy

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

Azure Security Benchmark ASBv3-GS-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 43 it maps to, and the evidence behind each claim, over MCP and REST.