What evidence do auditors commonly ask for on TVM-05 Detection Updates?

Update schedule and configuration for signature and rule updates; Logs showing update timestamps across detection tools; Threat intelligence feed subscriptions and ingestion records; Exceptions report for tools that failed to update.

What is the most common gap auditors find on TVM-05?

Updates set to weekly but failing silently on some sensors

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

`TVM-05` Detection Updates

The organisation sets up, operates and evaluates processes, procedures and technical measures that refresh its detection tooling, its threat signatures and its compromise indicators every week or more often.

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

easy

to go live

Cloud console / configuration management

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

Update schedule and configuration for signature and rule updates · Cloud console / configuration management
Logs showing update timestamps across detection tools · SIEM / log platform

periodic reviewEvidence produced at each review

Threat intelligence feed subscriptions and ingestion records · Document repository
Exceptions report for tools that failed to update · Document repository

governing documentDocuments that govern the control

none for this control

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

Common gaps auditors find

Updates set to weekly but failing silently on some sensors
Indicators of compromise imported manually and irregularly
No monitoring of update status

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-04 Threat Analysis and Modelling · TVM-06 External Library Vulnerabilities