EvidenceSheet

1.1 Establish and Maintain Detailed Enterprise Asset Inventory

Keep a complete, accurate and current register of every enterprise asset able to hold or process data: end-user devices (portable and mobile included), network gear, IoT and other non-computing devices, and servers, whether attached on premises, virtually, remotely or in the cloud, and including devices that regularly join the network though the enterprise does not control them. Each record carries the static network address where one exists, the hardware (MAC) address, the machine name, the data asset owner, the department and whether the device is approved to connect. Mobile device management tooling may feed the register for phones and tablets. Review and refresh it at least twice a year. Implementation Groups: IG1, IG2 and IG3 (part of the IG1 essential cyber hygiene baseline, so every enterprise applies it). Asset type: Devices. Security function: Identify.

Source: CIS Controls v8.1, 1.1. 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 CIS Controls v8.1 in the compliance library.

Scope: Implementation Groups: IG1, IG2, IG3. Security function: Identify; asset type: Devices.

Each safeguard shows its Implementation Groups. IG1 is the essential baseline for every enterprise, IG2 adds to it, IG3 is all 153. Version 8.1 adds the Govern security function and asks for more processes to be documented; numbering is unchanged from v8.

4
artefacts
2
held by a system
1
at each review
easy
to go live
Policy repository / GRC workspace
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

  • Exported enterprise asset register with MAC address, hostname, owner, department and approval flag per row · Policy repository / GRC workspace
  • MDM enrolment report for mobile devices · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

  • Dated record of the last two six-monthly register reviews with reviewer name · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • Cloud account resource listings reconciled to the register · Policy repository / GRC workspace

First move

Automate the pull from your Policy repository / GRC workspace. Version-controlled policy set with approval metadata; review dates tracked as records, not a calendar note.

Common gaps auditors find

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

1.2 Address Unauthorized Assets