TVM-08 Vulnerability Prioritization
Prioritise which vulnerabilities to fix first using a risk-based model built on an industry recognised framework rather than raw severity alone.
4
artefacts
0
held by a system
2
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 the model includes context such as exposure and asset criticality · Document repository
- Review of the model's effectiveness · Document repository
governing documentDocuments that govern the control
- The prioritisation model and the recognised framework it derives from · Document repository
- Prioritised backlog showing the model applied · 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
- Prioritisation by base severity score alone, ignoring exploitability and exposure
- Model documented but the backlog is worked in a different order
- Asset criticality unavailable, so context cannot be applied
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-07 Vulnerability Identification · TVM-09 Vulnerability Management Reporting