What evidence do auditors commonly ask for on TVM-06 External Library Vulnerabilities?

Software composition analysis tool configuration and reports; Library or dependency inventory per application; Records of library updates applied within policy timeframes; Exceptions for libraries that cannot be updated with compensating measures.

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

Dependencies scanned in some repositories only

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

`TVM-06` External Library Vulnerabilities

The organisation sets up, operates and evaluates processes, procedures and technical measures that find available updates for applications built on third-party or open source libraries, following its vulnerability management policy.

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

moderate

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

Software composition analysis tool configuration and reports · Cloud console / configuration management

periodic reviewEvidence produced at each review

Records of library updates applied within policy timeframes · Policy repository / GRC workspace

governing documentDocuments that govern the control

Library or dependency inventory per application · Policy repository / GRC workspace
Exceptions for libraries that cannot be updated with compensating measures · Document repository

First move

Start with the 1 of 4 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Dependencies scanned in some repositories only
Transitive dependencies not covered
Alerts raised but no remediation timeframes 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 sheet

TVM-05 Detection Updates · TVM-07 Penetration Testing