12.3.1 Targeted risk analysis documented for requirements that specify one
For each PCI DSS requirement that specifies completion of a targeted risk analysis, that analysis is documented and identifies the assets being protected, the threats the requirement protects against, and the factors con
5
artefacts
0
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Evidence of review of each analysis within the last 12 months · Document repository
- Records of updated analyses triggered by the annual review or by environment change · Cloud console / configuration management
governing documentDocuments that govern the control
- Documented policy and procedure defining how targeted risk analyses are performed · Policy repository / GRC workspace
- Inventory of every PCI DSS requirement where the entity sets its own frequency, each with its targeted risk analysis · Policy repository / GRC workspace
- Each analysis showing assets, threats, likelihood and impact factors, and the justification for the chosen frequency · Document repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- A single enterprise-wide risk assessment offered in place of per-requirement targeted analyses
- Frequency chosen first and the analysis written afterwards to justify it
- Some flexible-frequency requirements have no targeted risk analysis at all
- Analyses documented once and never reviewed within 12 months
Do this for your whole sheet
Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.
Build my evidence sheet12.2.1 Acceptable use policies for end-user technologies · 12.3.2 TRA for customized approach