PCI DSS 4.0
Req 3: Protect Stored Account Data

PCI DSS 4.0 3.5.1.2: Disk-level encryption with logical access controls

If disk-level or partition-level encryption is used to render PAN unreadable, it is implemented only on removable media or together with another mechanism that meets 3.5.1, with logical access separate from native OS authentication.

What else in your programme already covers this

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

CIS Controls v8 · 5 controls

  • CIS-3.11 Encrypt Sensitive Data at Rest
  • CIS-3.3 Configure Data Access Control Lists
  • CIS-3.9 Encrypt Data on Removable Media
  • CIS-4.11 Enforce Remote Wipe Capability on Portable End-User Devices
  • CIS-6.7 Centralize Access Control

ISO 27001:2022 · 5 controls

  • 5.18 Access rights
  • 7.10 Storage media
  • 8.2 Privileged access rights
  • 8.24 Use of cryptography
  • 8.3 Information access restriction

SOC 2 · 5 controls

  • SOC2-C1.1 Confidential information is identified and protected during receipt, processing, storage
  • SOC2-CC5.2 COSO principle 11: Selects and develops general controls over technology
  • SOC2-CC6.1 Implements logical access security software, infrastructure and architectures over protected information assets
  • SOC2-CC6.3 Role-based access and least privilege are enforced
  • SOC2-CC6.5 Discontinues logical and physical protections over physical assets only after the ability to read or recover data and software from those assets has been diminished and is no longer required to meet the entity's

ISO 27002:2022 · 4 controls

  • 5.18 Access rights
  • 7.10 Storage media
  • 8.24 Use of cryptography
  • 8.5 Secure authentication

NIST SP 800-53 Rev 5 · 4 controls

FedRAMP High · 3 controls

  • AC-19(5) Full Device or Container-Based Encryption
  • AC-3 Access Enforcement
  • SC-28(1) Cryptographic Protection

FedRAMP Moderate · 3 controls

  • AC-19(5) Full Device or Container-Based Encryption
  • AC-3 Access Enforcement
  • SC-28(1) Cryptographic Protection
  • ASBv3-PA-7 Follow just enough administration (least privilege) principle
  • DP-4 Enable data at rest encryption by default

CMMC 2.0 · 2 controls

  • AC-19(5) Full Device or Container-Based Encryption
  • AC-3 Access Enforcement
  • AC-19(5) Full Device or Container-Based Encryption
  • AC-3 Access Enforcement
  • ANSSI-HYG-31 Encrypt Sensitive Data, in Particular on Equipment That May Be Lost

C5 (Germany) · 1 control

  • C5-CRY-03 Encryption of sensitive data for storage

ISO 27701:2019 · 1 control

  • 6.7.1 Cryptographic controls
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected
  • AC-3 Access Enforcement

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 3: Protect Stored Account Data

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

PCI DSS 4.0 3.5.1.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 249 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 45 it maps to, and the evidence behind each claim, over MCP and REST.