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

2.7 Allowlist Authorized Scripts

Restrict script execution to authorised scripts (for example specific PowerShell or Python files) using controls such as code signing and version control, blocking all others. Reassess at least every six months. Implementation Group: IG3 only (for enterprises facing sophisticated attackers or holding highly sensitive data). Asset type: Software. Security function: Protect.

Source: CIS Controls v8.1, 2.7. 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: IG3. Security function: Protect; 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
1
held by a system
2
at each review
moderate
to go live
Endpoint management (MDM / EDR)
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

  • Script execution policy settings (signed-only, constrained language mode or equivalent) · Endpoint management (MDM / EDR)

periodic reviewEvidence produced at each review

  • Code-signing certificate and signing process records · Endpoint management (MDM / EDR)
  • Blocked-script events and six-monthly review · Endpoint management (MDM / EDR)

governing documentDocuments that govern the control

none for this control

First move

Start with the 1 of 3 artefacts that already live in a system (Endpoint management (MDM / EDR)); keep the periodic reviews but log each one as a dated record with a named reviewer.

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.6 Allowlist Authorized Libraries · 3.1 Establish and Maintain a Data Management Process