RV.2.1 Assess, Prioritize, and Remediate Vulnerabilities
Assess each vulnerability against business risk, exploitability, and customer impact, then prioritize remediation accordingly. Track remediation against agreed service level objectives by severity.
4
artefacts
0
held by a system
0
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
none for this control
governing documentDocuments that govern the control
- Vulnerability SLA matrix by severity · Policy repository / GRC workspace
- Remediation tracker with aging report · Policy repository / GRC workspace
- Exception process for accepted risk · Policy repository / GRC workspace
- Executive view of overdue vulnerabilities · 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
- SLAs defined but routinely missed without escalation
- exceptions never expire
- no visibility into customer exposure when prioritizing
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 sheetRV.1.3 Vulnerability Disclosure Policy · RV.2.2 Develop and Implement Remediation Plans