PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.1.3: 12.1.3 Security roles defined and acknowledged by all personnel

The security policy must spell out, without ambiguity, the information security roles and responsibilities that apply to every member of personnel. In addition, all personnel must know those responsibilities and must formally acknowledge them. The guidance notes that unclear roles risk misuse of information assets and inconsistent interaction with security staff. Customized approach objective: every person understands the part they play in safeguarding the entity's cardholder data.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 4 controls

C5 (Germany) · 3 controls

  • C5-HR-02 Employment terms and conditions
  • C5-OIS-01 Information Security Management System (ISMS)
  • C5-SP-01 Documentation, communication and provision of policies and instructions

FedRAMP High · 2 controls

  • AU-4 Audit Log Storage Capacity
  • SC-5 Denial-of-Service Protection

FedRAMP Moderate · 2 controls

  • AU-4 Audit Log Storage Capacity
  • SC-5 Denial-of-Service Protection

ISO 22301:2019 · 2 controls

  • 7.1 Resources
  • 8.3.4 Resource requirements

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-181 · 2 controls

  • ANSSI-HYG-39 Designate an Information System Security Officer and Make the Role Known

APRA CPS 234 · 1 control

  • CPS234-14 Definition of Information Security Roles and Responsibilities
  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data
  • GS-1 Align organization roles, responsibilities and accountabilities
  • CFTC-SS-2 Enterprise Risk Management and Governance Category

ISO 27001:2022 · 1 control

  • 8.6 Capacity management

ISO 27002:2022 · 1 control

  • 8.6 Capacity management

ISO 27018:2019 · 1 control

  • 12.1.3 Capacity management

NIS2 Directive · 1 control

  • Art.21.2.a Policies on risk analysis and on information system security
  • P1-1.3.3 P1-1.3.3 Staff know the policy and their own security duties

SOC 2 · 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 12: Information Security Policies

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

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