PCI DSS 4.0
Req 9: Restrict Physical Access

PCI DSS 4.0 9.4.2: 9.4.2 Classification of media by data sensitivity

Every item of media with cardholder data must be classified according to how sensitive the data is. The guidance adds that media should be identified so its classification status is apparent, which does not mean it needs a literal confidential label. Applicability: all entities holding cardholder data on media. Customized approach objective: media are classified and given appropriate protection.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 28 controls across 17 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 · 3 controls

  • 5.12 Classification of information
  • 5.13 Labelling of information
  • 7.10 Storage media

ISO 27002:2022 · 3 controls

  • 5.12 Classification of information
  • 5.13 Labelling of information
  • 7.10 Storage media

FedRAMP High · 2 controls

  • MP-3 Media Marking
  • RA-2 Security Categorization

FedRAMP Moderate · 2 controls

  • MP-3 Media Marking
  • RA-2 Security Categorization

ISO 27701:2019 · 2 controls

  • 6.5 Asset management
  • 6.5.2 Information classification
  • 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 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

APRA CPS 234 · 1 control

  • SEC07-BP01 Understand your data classification scheme
  • ASBv3-DP-1 Discover, classify, and label sensitive data

C5 (Germany) · 1 control

  • C5-AM-06 Asset Classification and Labelling

CIS Controls v8 · 1 control

  • CIS-3.7 Establish and Maintain a Data Classification Scheme

CMMC 2.0 · 1 control

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 Req 9: Restrict Physical Access

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 9.4.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 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. 415 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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