PCI DSS 4.0 6.1.2: 6.1.2 Requirement 6 roles and responsibilities assigned

What else in your programme already covers this

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

SOC 2 · 5 controls

SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)
SOC2-CC1.5 CC1.5 Accountability for internal control responsibilities (COSO principle 5)
SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

CMMC 2.0 · 2 controls

AT.L2-3.2.1 Role-Based Risk Awareness
AT.L2-3.2.2 Role-Based Training

NIST SP 800-53 Rev 5 · 2 controls

NIST800-PM-10 PM-10 Authorization Process
NIST800-PS-9 PS-9 Position Descriptions

AWS Well-Architected Security Pillar · 1 control

SEC11-BP08 Build a program that embeds security ownership in workload teams

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

CCM-HRS-09 Personnel Roles and Responsibilities

FedRAMP High · 1 control

PS-9 Position Descriptions (PS-9)

ISO 22301:2019 · 1 control

5.3 Roles, responsibilities and authorities

ISO 27001:2022 · 1 control

5.2 Information security roles and responsibilities

ISO 27002:2022 · 1 control

5.2 Information security roles and responsibilities

ISO 27701:2019 · 1 control

5.3.3 Organizational roles, responsibilities and authorities

ISO/IEC 42001:2023 · 1 control

5.3 Roles, responsibilities and authorities

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

NIST SP 800-171 Rev 3 · 1 control

03.15.01 Policy and Procedures

NIST SP 800-218 · 1 control

SP800-218-PO.2.1 Roles and Responsibilities for Secure Development

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.

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

PCI DSS 4.0 6.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 280 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202249.6% covered · 141 gaps If you hold FedRAMP Moderate49.3% covered · 142 gaps If you hold NIST SP 800-53 Rev 547.5% covered · 147 gaps If you hold ISO 27002:202243.2% covered · 159 gaps If you hold CIS Controls v838.2% covered · 173 gaps If 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 each Browse the graph free