← PCI DSS 4.0.1 · Req 12 — Policies and programmes
12.3.1 — Targeted risk analyses
Requirement
For each PCI DSS requirement that lets the entity set its own frequency, a targeted risk analysis identifies the assets and threats, the factors affecting likelihood and impact, and justifies the chosen frequency; each analysis is reviewed at least once every 12 months.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| SOC 2 | CC3.1 | Objectives and risk identification | risk-assessment |
| SOC 2 | CC3.2 | Risk analysis and response | risk-assessment |
| SOC 2 | CC3.3 | Fraud risk | risk-assessment |
| HIPAA | 164.308(a)(1)(ii)(A) | Risk analysis (R) | risk-assessment |
| HIPAA | 164.308(a)(1)(ii)(B) | Risk management (R) | risk-assessment |
| GLBA | 314.4(b) | Written risk assessment | risk-assessment |
| NIST CSF 2.0 | ID.RA-05 | Risks are prioritised to inform response | risk-assessment |
| GDPR | Art.35 | Data protection impact assessment | risk-assessment |