ID.RA-06 Risk responses are chosen, prioritized, planned, tracked, and communicated
Risk responses are chosen, prioritized, planned, tracked, and communicated. Control from NIST Cybersecurity Framework 2.0 framework, domain: ID - Identify.
5
artefacts
1
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
- Tracking dashboard for treatment progress · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Approval records for risk acceptance · Policy repository / GRC workspace
- Periodic re evaluation of treatment effectiveness · Document repository
governing documentDocuments that govern the control
- Risk treatment plan per risk · Policy repository / GRC workspace
- Communication to stakeholders on chosen responses · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Treatments default to acceptance
- Acceptance approvals not at appropriate level
- Dashboard tracks tasks, not outcomes
- Re evaluation skipped
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 sheetID.RA-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization · ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked