1.5 Use a Passive Asset Discovery Tool
Use a passive discovery tool to identify assets connected to the enterprise’s network. Review and use scans to update the enterprise’s asset inventory at least weekly, or more frequently.
4
artefacts
1
held by a system
2
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
- Evidence the safeguard is implemented: Use a Passive Asset Discovery Tool · Document repository
- Records showing the safeguard is operating (logs, reports, reviews) · SIEM / log platform
governing documentDocuments that govern the control
- Policy/standard covering CIS Control 1 (Inventory and Control of Enterprise Assets) · 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 IG3 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 sheet1.4 Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory · 2.1 Establish and Maintain a Software Inventory