TVM-11 Vulnerability Management Reporting
The organisation defines and operates a process for tracking and reporting work on finding and fixing vulnerabilities, including telling the stakeholders concerned.
Source: CSA CCM v4.1, TVM-11. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.
Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
- Vulnerability tracking system records with status history · Vulnerability scanner / patch tooling
- Periodic vulnerability reports to system owners and management · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Escalation records for overdue remediation · Document repository
governing documentDocuments that govern the control
- Stakeholder notification list and sent notifications · Document repository
First move
Common gaps auditors find
- Tracking in spreadsheets that are not kept current
- System owners not told about vulnerabilities on their assets
- No escalation for overdue items
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-10 Threat Response · TVM-12 Vulnerability Management Metrics