Azure Security Benchmark
Data Protection

Azure Security Benchmark ASBv3-DP-1: Discover, classify, and label sensitive data

Maintain an inventory of sensitive data within the defined scope, using discovery tooling to find, classify and label it.

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

What else in your programme already covers this

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

FedRAMP High · 5 controls

  • CM-12 Information Location (CM-12)
  • CM-12(1) Information Location | Automated Tools to Support Information Location (CM-12(1))
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • MP-3 Media Marking
  • RA-2 Security Categorization

FedRAMP Moderate · 5 controls

  • CM-12 Information Location (CM-12)
  • CM-12(1) Information Location | Automated Tools to Support Information Location (CM-12(1))
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • MP-3 Media Marking
  • RA-2 Security Categorization

ISO 27001:2022 · 4 controls

  • 5.12 Classification of information
  • 5.13 Labelling of information
  • 5.34 Privacy and protection of personal identifiable information (PII)
  • 5.9 Inventory of information and other associated assets

ISO 27002:2022 · 4 controls

  • 5.12 Classification of information
  • 5.13 Labelling of information
  • 5.34 Privacy and protection of PII
  • 5.9 Inventory of information and other associated assets

NIST SP 800-53 Rev 5 · 4 controls

PCI DSS 4.0 · 4 controls

  • 1.4.4 1.4.4 Cardholder data stores not reachable from untrusted networks
  • 12.5.2 12.5.2 Annual and change-driven scope confirmation
  • 9.4.2 9.4.2 Classification of media by data sensitivity
  • 3.2.1 3.2.1 Data retention and disposal minimise stored account data
  • SEC07-BP01 Understand your data classification scheme
  • SEC07-BP03 Automate identification and classification
  • AUCDR-IS-3 Securely manage information assets over their lifecycle
  • AUCDR-IS-STEP2 Step 2 - Define the boundaries of the CDR data environment

CIS Controls v8 · 2 controls

  • CIS-3.2 Establish and Maintain a Data Inventory
  • CIS-3.7 Establish and Maintain a Data Classification Scheme

HIPAA Security Rule · 2 controls

  • NIST-CSF-ID.AM-05 Assets are prioritized based on classification, criticality, resources, and impact on the mission
  • NIST-CSF-ID.AM-07 Inventories of data and corresponding metadata for designated data types are maintained

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

  • ANSSI-HYG-04 Identify the Most Sensitive Information and Servers and Maintain a Network Diagram

APRA CPS 234 · 1 control

  • CPS234-20 Information Asset Classification

C5 (Germany) · 1 control

  • C5-AM-06 Asset Classification and Labelling

CMMC 2.0 · 1 control

ISO 27701:2019 · 1 control

  • 6.5.2 Information classification

NIST SP 800-172 · 1 control

  • 3.14.5e Review Persistent Storage and Remove CUI No Longer Needed

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 Data Protection

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

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