CM-8 System component inventory
Requires an accurate inventory of system components that covers every component, avoids duplicate or cross system accounting, is held at the granularity needed for tracking and reporting, carries the information the orga
4
artefacts
1
held by a system
1
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Reconciliation of the inventory against a discovery scan or cloud asset listing · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Defined review frequency and evidence of review at that cadence · Cloud console / configuration management
governing documentDocuments that govern the control
- Component inventory with the defined accountability fields populated · Policy repository / GRC workspace
- Rules preventing duplicate accounting across system boundaries · Policy repository / GRC workspace
First move
Start with the 1 of 4 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Cloud and container assets absent because inventory is built from a fixed asset register
- Ownership field blank, so no one is accountable for individual components
- Inventory reviewed annually while the estate changes weekly
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 sheetCM-7 Least functionality · CM-9 Configuration management plan