PCI DSS · Requirement 12: Support information security with organizational policies and programs
12.3.2
Targeted risk analysis for customised approach
frameworkPCI DSS v4.0.1
sectionRequirement 12: Support information security with organizational policies and programs
csf 2.0GV.RM-06 ID.RA-07
topics—
frameworks0 0 3
Official text · not licensableSummary (ControlMapping's wording): Targeted risk analysis for customised approach. 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.RM-06ID.RA-07 | A standardized method for calculating, documenting, categorizing, and prioritizing cybersecurity risks is established and communicated; Changes and exceptions are managed, assessed for risk impact, recorded, and tracked | No mapping. Only shares CSF GV.RM-06, ID.RA-07: related, not a mapping | |
| ISO 27001 | A.5.1A.8.32Clause 6.1.2Clause 6.1.3 | Policies for information security; Change management… | No mapping. Only shares CSF GV.RM-06, ID.RA-07: related, not a mapping | |
| 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 | CC3.1CC5.1CC9.1 | Objectives specified clearly enough to identify risks; Control activities that mitigate risks… | No mapping. Only shares CSF GV.RM-06: related, not a mapping | |
| CMMC | CM.L2-3.4.3CM.L2-3.4.4RA.L2-3.11.1 | System Change Management; Security Impact Analysis… | No mapping. Only shares CSF ID.RA-07, GV.RM-06: related, not a mapping | |
| 800-53 | CA-7CM-3CM-4PM-9 | Continuous Monitoring; Configuration Change Control… | No mapping. Only shares CSF ID.RA-07, GV.RM-06: related, not a mapping+4 more loosely related (not mappings) | |
| HIPAA | §164.308(a)(1)(ii)(A)§164.308(a)(1)(ii)(B)§164.308(a)(1)(ii)(D)§164.308(a)(8) | Risk Analysis; Risk Management… | No mapping. Only shares CSF GV.RM-06, ID.RA-07: related, not a mapping+1 more loosely related (not mappings) | |
| GDPR | Art.24(1)Art.32(2) | Responsibility of the controller; Security of processing | No mapping. Only shares CSF GV.RM-06: related, not a mapping | |
| NIS2 | 2.16.47.1 | Risk management framework; Change management, repairs and maintenance… | No mapping. Only shares CSF GV.RM-06, ID.RA-07: related, not a mapping | |
| Essential Eight | — | No requirement | No mapping in our data | No mapping in our data (Essential Eight links are editorial only). |
| DORA | Art.5(2)(a)Art.6(1)Art.6(8)Art.16(1) | Governance and organisation; ICT risk management framework… | No mapping. Only shares CSF GV.RM-06: related, not a mapping+1 more loosely related (not mappings)Art.24(1) General requirements for the performance of digital operational resilience testing Only shares CSF GV.RM-06: related, not a mapping | |
| CPS 234 | Para 13Para 15Para 27Para 31 | Board ultimately responsible for information security; Maintain a capability commensurate with threats… | No mapping. Only shares CSF GV.RM-06: 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.