AWS Well-Architected Security Pillar
Data Protection

AWS Well-Architected Security Pillar SEC07-BP01: Understand your data classification scheme

Understand and document the classification scheme that applies to the data the workload processes, including handling requirements, storage locations, owners and the legal obligations attached to each class.

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

What else in your programme already covers this

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

ISO 27001:2022 · 5 controls

  • 5.12 Classification of information
  • 5.13 Labelling of information
  • 5.31 Legal, statutory, regulatory and contractual requirements
  • 5.34 Privacy and protection of personal identifiable information (PII)
  • 5.9 Inventory of information and other associated assets

FedRAMP High · 3 controls

  • CM-12 Information Location (CM-12)
  • MP-3 Media Marking
  • RA-2 Security Categorization

FedRAMP Moderate · 3 controls

  • CM-12 Information Location (CM-12)
  • MP-3 Media Marking
  • RA-2 Security Categorization

ISO 27002:2022 · 3 controls

  • 5.12 Classification of information
  • 5.31 Legal, statutory, regulatory and contractual requirements
  • 5.9 Inventory of information and other associated assets
  • NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
  • 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-171 Rev 3 · 3 controls

NIST SP 800-53 Rev 5 · 3 controls

  • ASBv3-DP-1 Discover, classify, and label sensitive data
  • ASBv3-GS-3 Define and implement data protection strategy

CIS Controls v8 · 2 controls

  • CIS-3.1 Establish and Maintain a Data Management Process
  • CIS-3.7 Establish and Maintain a Data Classification Scheme
  • ANSSI-HYG-04 Identify the Most Sensitive Information and Servers and Maintain a Network Diagram
  • AUCDR-IS-STEP2 Step 2 - Define the boundaries of the CDR data environment

C5 (Germany) · 1 control

  • C5-AM-06 Asset Classification and Labelling

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

ISO 27701:2019 · 1 control

  • 6.5.2 Information classification

PCI DSS 4.0 · 1 control

  • 9.4.2 9.4.2 Classification of media by data sensitivity

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 AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC07-BP01 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar 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 42 it maps to, and the evidence behind each claim, over MCP and REST.