RA-3 Risk assessment
Requires a risk assessment that identifies threats and vulnerabilities, judges how likely each is and how badly the organization would be harmed by unauthorized access, use, disclosure, disruption, modification or destru
5
artefacts
0
held by a system
3
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
- Risk assessment report covering threats, vulnerabilities, likelihood and impact · Vulnerability scanner / patch tooling
- Distribution record to the defined personnel · Policy repository / GRC workspace
- Evidence results feed organizational and mission level risk decisions · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Analysis of adverse effects on individuals from personal information processing · Policy repository / GRC workspace
- Update history showing reassessment at the defined frequency and after significant change · Policy repository / GRC workspace
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
- Assessment addresses organizational harm only and ignores harm to individuals
- Performed once at authorization and never refreshed after major change
- Results never reach the people who make risk decisions
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 sheetRA-2 Security categorization · RA-5 Vulnerability monitoring and scanning