TVM-09 Vulnerability Management Reporting
Track and report vulnerability identification and remediation activity, including notification to the stakeholders who need to know.
4
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
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 stakeholders were notified of vulnerabilities affecting them · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- The tracking system holding identified vulnerabilities through to closure · Policy repository / GRC workspace
- Reports issued and their recipients · Document repository
- Ageing analysis of open findings · 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
- Tracking held in scanner output rather than a system with ownership and dates
- Reports produced for security only, never reaching asset owners
- No ageing view, so long-open findings are invisible
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 sheetTVM-08 Vulnerability Prioritization · TVM-10 Vulnerability Management Metrics