EvidenceSheet
CIS Controls v8.1 · CIS Control 2: Inventory and Control of Software Assets

2.4 Utilize Automated Software Inventory Tools

Where possible use software inventory tooling across the enterprise so installed software is discovered and recorded automatically. Implementation Groups: IG2 and IG3 (not in the IG1 baseline; applies from IG2 upward). Asset type: Software. Security function: Detect.

Source: CIS Controls v8.1, 2.4. 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: IG2, IG3. Security function: Detect; asset type: Software.

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.

3
artefacts
2
held by a system
0
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

  • Inventory agent or tool coverage report against the asset register · Policy repository / GRC workspace
  • Automated software inventory export · Policy repository / GRC workspace

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Integration showing tool output updating the software 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

2.3 Address Unauthorized Software · 2.5 Allowlist Authorized Software