TVM-05 External Library Vulnerabilities
Track third party and open source libraries used by applications for available updates, and act on them under the vulnerability management policy.
4
artefacts
1
held by a system
1
at each review
moderate
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
- Tooling output identifying outdated or vulnerable libraries · Document repository
periodic reviewEvidence produced at each review
- Records of library updates applied and their timeframes · Document repository
governing documentDocuments that govern the control
- A software bill of materials or dependency inventory per application · Policy repository / GRC workspace
- Handling of libraries that cannot be updated · Document repository
First move
Start with the 1 of 4 artefacts that already live in a system (Document repository); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Dependency scanning enabled on new repositories only
- Findings raised with no owner, so the backlog grows
- Transitive dependencies not scanned, so the real exposure is understated
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