PCI DSS · Requirement 12: Support information security with organizational policies and programs
12.1.2
Security policy reviewed at least annually
frameworkPCI DSS v4.0.1
sectionRequirement 12: Support information security with organizational policies and programs
csf 2.0GV.PO-01 GV.PO-02 GV.RM-01
topicsGovernance Policy
frameworks5 4 4
Official text · not licensableSummary (ControlMapping's wording): Security policy reviewed at least annually. The requirement text is PCI SSC's copyright; see PCI DSS v4.0.1.
Wrong or missing mapping? Report it
| Framework | Requirement | Title | Link | Source / reason |
|---|---|---|---|---|
| NIST CSF 2.0 | GV.PO-01GV.PO-02 | Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced; Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission | Crosswalk | Same topic: Governance Policy1 loosely related (not mappings)GV.RM-01 Risk management objectives are established and agreed to by organizational stakeholders Only shares CSF GV.RM-01: related, not a mapping |
| ISO 27001 | A.5.1A.5.37Clause 5.2 | Policies for information security; Documented operating procedures… | Crosswalk | Same topic: Governance Policy |
| CIS v8.1 | — | No requirement | No mapping in our data | No mapping in our data (most CIS links are editorial: CIS's published crosswalk covers 49 of 153 safeguards). |
| SOC 2 | CC1.1CC5.3 | Commitment to integrity and ethical values; Control activities deployed through policies and procedures | Editorial | Same topic: Governance Policy (editorial pick)3 loosely related (not mappings)CC3.1 Objectives specified clearly enough to identify risks Only shares CSF GV.RM-01: related, not a mapping |
| CMMC | — | No requirement | No mapping in our data | No mapping in our data. |
| 800-53 | PL-1PM-1 | Policy and Procedures; Information Security Program Plan | Crosswalk | Same topic: Governance Policy21 loosely related (not mappings)…and 13 more in the downloads |
| HIPAA | §164.316(a)§164.316(b)(2)(iii) | Policies and Procedures; Updates | Crosswalk | Same topic: Governance Policy22 loosely related (not mappings)§164.308(a)(1) Security Management Process Only shares CSF GV.PO-01, GV.PO-02: related, not a mapping §164.308(a)(3)(ii)(A) Authorization and/or Supervision Only shares CSF GV.PO-01, GV.PO-02: related, not a mapping §164.308(a)(3)(ii)(B) Workforce Clearance Procedure Only shares CSF GV.PO-01, GV.PO-02: related, not a mapping §164.308(a)(3)(ii)(C) Termination Procedures Only shares CSF GV.PO-01, GV.PO-02: related, not a mapping §164.308(a)(4) Information Access Management Only shares CSF GV.PO-01, GV.PO-02: related, not a mapping §164.308(a)(4)(ii)(B) Access Authorization Only shares CSF GV.PO-01, GV.PO-02: related, not a mapping §164.308(a)(4)(ii)(C) Access Establishment and Modification Only shares CSF GV.PO-01, GV.PO-02: related, not a mapping …and 14 more in the downloads |
| GDPR | Art.24(2) | Responsibility of the controller | Editorial | Same topic: Governance Policy (editorial pick) |
| NIS2 | 1.1 | Policy on the security of network and information systems | Crosswalk | Same topic: Governance Policy |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | Art.5(2)(b)Art.6(5)Art.9(4)(a) | Governance and organisation; ICT risk management framework… | Editorial | Same topic: Governance Policy (editorial pick)5 loosely related (not mappings)Art.24(1) General requirements for the performance of digital operational resilience testing Only shares CSF GV.RM-01: related, not a mapping |
| CPS 234 | Para 18Para 19 | Maintain an information security policy framework; Policies direct everyone with security obligations | Editorial | Same topic: Governance Policy (editorial pick)4 loosely related (not mappings)Para 13 Board ultimately responsible for information security Only shares CSF GV.RM-01: related, not a mapping Para 15 Maintain a capability commensurate with threats Only shares CSF GV.RM-01: related, not a mapping Para 27 Systematic testing programme for control effectiveness Only shares CSF GV.RM-01: related, not a mapping Para 31 Review the testing programme at least annually Only shares CSF GV.RM-01: related, not a mapping |
| Cyber Essentials | — | No requirement | No mapping in our data | No mapping in our data (Cyber Essentials covers five technical controls only). |
Crosswalk a published crosswalk (NIST, ENISA, CIS, PCI SSC) makes the link · Editorial ControlMapping's judgement where no crosswalk exists; the reason is shown · only shares a CSF 2.0 outcome: worth checking, not a mapping · No mapping in our data nothing mapped in our data; often new work, but check the coverage notes. How links are sourced.