TVM-03 Vulnerability Remediation Schedule
Have defined routes for both scheduled and emergency response to a discovered vulnerability, chosen according to the risk that vulnerability carries.
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
- Records of emergency responses invoked and the outcome · Document repository
- Evaluation evidence that the paths work under pressure · Document repository
governing documentDocuments that govern the control
- The documented scheduled and emergency response paths with their trigger criteria · Document repository
- The risk criteria that select between the two paths · 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
- Emergency path undefined, so urgent vulnerabilities queue behind routine work
- Trigger criteria absent, making the choice of path arbitrary
- Emergency path used so often it has become the normal route
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-02 Malware Protection Policy and Procedures · TVM-04 Detection Updates