What evidence do auditors commonly ask for on TVM-10 Threat Response?

Threat response procedure with prioritisation criteria; Threat register ranked by risk with chosen mitigations; Reference framework mapping, for example MITRE ATT&CK or NIST CSF, used in decisions; Records of mitigations deployed against prioritised threats; Review of threat response decisions.

CSA CCM v4.1 · TVM - Threat & Vulnerability Management

`TVM-10` Threat Response

The organisation prioritises and mitigates threats through a risk-based approach, drawing on an industry recognised framework to steer threat decisions and the protective measures chosen.

Source: CSA CCM v4.1, TVM-10. 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.

artefacts

held by a system

at each review

hard

to go live

Document repository

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

none for this control

periodic reviewEvidence produced at each review

Records of mitigations deployed against prioritised threats · Document repository
Review of threat response decisions · Document repository

governing documentDocuments that govern the control

Threat response procedure with prioritisation criteria · Policy repository / GRC workspace
Threat register ranked by risk with chosen mitigations · Policy repository / GRC workspace
Reference framework mapping, for example MITRE ATT&CK or NIST CSF, used in decisions · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Threats tracked but not ranked
Mitigation choices not linked to a framework
No record of why some threats were accepted

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 sheet

TVM-09 Vulnerability Prioritization · TVM-11 Vulnerability Management Reporting