# CIS Controls v8 2.7 — Allowlist Authorized Scripts

- Source: https://support.icompaas.com/compliance/cis-controls-v8/2-7-allowlist-authorized-scripts
- Section: [Compliance](https://support.icompaas.com/compliance) › [CIS Critical Security Controls v8](https://support.icompaas.com/compliance/cis-controls-v8) › Control 2 — Inventory and Control of Software Assets
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**CIS Controls v8**·Control `2.7`·medium·Component: **Protect**

## What this control requires

> Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
> 
> — CIS Controls v8, Control 2.7

### In plain English

Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. In practice, this means you can prove you ensure version-level controls on a defined cadence.

## Why it matters

The CIS Controls are an industry-vetted, prioritised defence: skipping a safeguard widens the attack surface that the safeguards above and below it assume is closed. Audit frameworks (FedRAMP, PCI DSS, HIPAA) all cite CIS as evidence of due care.

## What an auditor looks for

A CIS-aligned reviewer wants to see (a) which Implementation Group you are targeting, (b) a documented owner for the safeguard, and (c) a tooling or process artefact (config, scan output, ticket) that proves the safeguard runs on the cadence the control demands.

Within **Protect**, the assessor will trace your implementation back to the catalogue reference (Control 2.7) and look for objective evidence on the latest two assessment cycles.

## How to implement

#### Secure Development

**Pipeline.** Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline.

**Branch protection.** Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence.

#### Code Review Testing

**Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

### Operational checklist

-   **Ensure.** Document the trigger, the owner and the cadence.
-   **Allowlist.** Document the trigger, the owner and the cadence.
-   **Block.** Document the trigger, the owner and the cadence.
-   **Protect.** Document the trigger, the owner and the cadence.
-   **Scope:** version, digital signatures, version control.

## Evidence to collect

-   **Code Repo Scan.** Source-control evidence — branch protection, required reviewers, CI status, SCA / SAST reports.

Source control pipelines (GitHub, GitLab) enforce SDLC guardrails. Focus: Allowlist Authorized Scripts.

## Common pitfalls

-   CI security checks set to warn-only; the merge button is faster than the security feedback.

## How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

-   [**SOC 2 (2017 TSC) CC7.2** — Anomaly Detection](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc7-2-anomaly-detection)
-   [**GDPR Article 75** — Secretariat](https://support.icompaas.com/compliance/gdpr/article-75-secretariat)
-   [**BSI C5:2020 OPS-03** — Capacity Management - Controlling of Resources](https://support.icompaas.com/compliance/bsi-c5-2020/ops-03-capacity-management-controlling-of-resources)

## Related controls in CIS Controls v8

-   [**Control 14.6** — Train Workforce Members on Recognizing and Reporting Security Incidents](https://support.icompaas.com/compliance/cis-controls-v8/14-6-train-workforce-members-on-recognizing-and-reporting-security-incidents)
-   [**Control 16.3** — Perform Root Cause Analysis on Security Vulnerabilities](https://support.icompaas.com/compliance/cis-controls-v8/16-3-perform-root-cause-analysis-on-security-vulnerabilities)
-   [**Control 16.12** — Implement Code-Level Security Checks](https://support.icompaas.com/compliance/cis-controls-v8/16-12-implement-code-level-security-checks)
-   [**Control 16.13** — Conduct Application Penetration Testing](https://support.icompaas.com/compliance/cis-controls-v8/16-13-conduct-application-penetration-testing)

## References

-   [Center for Internet Security — CIS Controls v8](https://www.cisecurity.org/controls/v8)
-   Catalogue identifier: `Control 2.7`

Topics: governance risksecure developmentcode review testingdevsecops

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.