PCI DSS 4.0
Req 3: Protect Stored Account Data

PCI DSS 4.0 3.1.1: 3.1.1 Requirement 3 policies and procedures maintained and in use

Every security policy and operational procedure that supports Requirement 3 (protection of stored account data) must be written down, kept current, actively followed in practice, and communicated to every party they affect. The guidance encourages revising these documents promptly whenever processes, technology or business objectives change rather than waiting for a scheduled review cycle. Customized approach objective: personnel involved in storing and protecting account data follow defined expectations, controls and oversight, so the supporting work is repeatable, consistent and matches what management intends.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 47 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 22301:2019 · 5 controls

  • 5.2.2 Communicating the business continuity policy
  • 7.5 Documented information
  • 7.5.2 Creating and updating
  • 7.5.3 Control of documented information
  • 8.4.4 Business continuity plans

ISO 27001:2022 · 5 controls

  • 5.1 Policies for information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.37 Documented operating procedures
  • 5.4 Management responsibilities
  • 6.3 Information security awareness, education and training

CMMC 2.0 · 4 controls

ISO 27002:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.37 Documented operating procedures
  • 6.3 Information security awareness, education and training

ISO/IEC 42001:2023 · 4 controls

  • 5.2 AI policy
  • 7.4 Communication
  • 7.5.1 General
  • 8.1 Operational planning and control

SOC 2 · 4 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)

HIPAA Security Rule · 3 controls

ISO 27701:2019 · 3 controls

  • 5.5.4 Communication
  • 5.5.5 Documented information
  • 6.2.1 Management direction for information security

NIST SP 800-53 Rev 5 · 3 controls

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

NIST Cybersecurity Framework 2.0 · 2 controls

  • 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
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission

NIST SP 800-66 Rev 2 · 2 controls

Azure Security Benchmark · 1 control

  • ASBv3-GS-3 Define and implement data protection strategy

C5 (Germany) · 1 control

  • C5-CRY-01 Policy for the use of encryption procedures and key management

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

  • CCM-DSP-01 Security and Privacy Policy and Procedures

NIST SP 800-171 Rev 3 · 1 control

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.1.1 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.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll PCI DSS 4.0 controls