RA-7 Risk Response
Requires the organisation to respond to findings from security and privacy assessments, monitoring and audits, so identified risk is treated rather than only recorded.
system holds itEvidence a system already holds
- Vulnerability scan reports for internal, external, and authenticated scopes · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Penetration test report with retest evidence · Vulnerability scanner / patch tooling
- Risk acceptance memos signed by accountable executives · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Control implementation statement for RA-7 citing the system mission and inheritance from common controls · Policy repository / GRC workspace
- Risk register with likelihood, impact, and treatment owners · Policy repository / GRC workspace
- Threat intelligence feed subscriptions and triage workflow · Policy repository / GRC workspace
First move
Common gaps auditors find
- Penetration tests scope narrow and exclude key applications
- Scan coverage gaps for containerised and ephemeral workloads
- Threat intelligence consumed but not operationalised into detections
- High severity vulnerabilities exceed remediation SLA without risk acceptance
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-5(11) Vulnerability Monitoring and Scanning | Public Disclosure Program. Establish a public reporting channel for receiving reports of vulnerabilities in organizational systems and system components · RA-9 Criticality Analysis. Identify critical system components and functions by performing a criticality analysis for [Assignment: organization-defined systems, system components, or system services] at [Assignment: organization-defined decision points in the system development life cycle]