16.4 Establish and Manage an Inventory of Third-Party Software Components
Establish and manage an updated inventory of third-party components used in development, often referred to as a “bill of materials,” as well as components slated for future use. This inventory is to include any risks tha
4
artefacts
1
held by a system
1
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
system holds itEvidence a system already holds
- Configuration / tooling output demonstrating the safeguard · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Records showing the safeguard is operating (logs, reports, reviews) · SIEM / log platform
governing documentDocuments that govern the control
- Evidence the safeguard is implemented: Establish and Manage an Inventory of Third-Party Software Components · Vendor register / contract repository
- Policy/standard covering CIS Control 16 (Application Software Security) · Policy repository / GRC workspace
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
- Safeguard implemented for some assets but not all in scope
- No evidence of ongoing operation (point-in-time only)
- Implementation Group IG2 baseline not met
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 sheet16.3 Perform Root Cause Analysis on Security Vulnerabilities · 16.5 Use Up-to-Date and Trusted Third-Party Software Components