CIS Critical Security Controls® · v8.1

The CIS Critical Security Controls® are a prioritized set of 18 Controls broken into 153 Safeguards, published by the Center for Internet Security. Safeguards are sorted into three Implementation Groups, so an organization can adopt the IG1 baseline on its own rather than taking on the whole set at once.

153

requirements tracked

Core plans

Access

Scope

How much of the standard Keel models

Models its declared scope in full

Keel authors every leaf requirement in the scope declared below, all 153 of them, with nothing inside that scope left out. A test fails the build if the authored count and the declared count ever diverge, so this framework cannot quietly lose requirements after the fact.

Authored in Keel: 153 requirements
In Keel’s scored scope: 153 leaf requirements

Keel publishes this for every framework it ships, complete or not, so a readiness percentage can be read against a denominator you can see. Compare every framework

In Keel

What Keel tracks for CIS Critical Security Controls

Every Control and Safeguard is authored as a tracked requirement, at Safeguard level
Safeguards are crosswalked to the other frameworks in the catalog, so a control evidenced once is recorded against each framework it satisfies
Progress is tracked across every Control and Safeguard

Shared canonical controls

CIS Critical Security Controls shares canonical controls with FedRAMP Rev5 Class D, FedRAMP Rev5 Class C and ISO/IEC 27001 and others in the catalog. Implement one of those controls and it counts toward every framework it satisfies, so adding CIS Critical Security Controls rarely means starting from scratch.

Shares canonical controls with

ISO/IEC 27001 shares canonical controls
PCI DSS shares canonical controls
SOC 2 shares canonical controls
SOX (Sarbanes-Oxley) Section 404 shares canonical controls
NIST Cybersecurity Framework shares canonical controls
NIST SP 800-53 shares canonical controls
FedRAMP Rev5 Class B shares canonical controls
FedRAMP Rev5 Class C shares canonical controls
FedRAMP Rev5 Class D shares canonical controls
FedRAMP 20x shares canonical controls
FedRAMP Consolidated Rules shares canonical controls
NIST SP 800-171 shares canonical controls
HIPAA shares canonical controls
GDPR shares canonical controls
COPPA shares canonical controls
Google Play Families no shared canonical controls
Amazon Appstore Child-Directed Apps no shared canonical controls
Apple App Store Kids Category no shared canonical controls
PIPEDA shares canonical controls
ISO 9001 shares canonical controls
AI Governance Essentials no shared canonical controls
ISO/IEC 42001 no shared canonical controls
NIST AI Risk Management Framework no shared canonical controls
EU AI Act no shared canonical controls
ESG Essentials shares canonical controls
US Employment Law - Federal Baseline shares canonical controls

A framework is lit when at least one canonical control satisfies both CIS Critical Security Controls and that framework. Unlit means none of them do, which is an absence rather than a judgment about that standard. 19 of 26 are lit here.

Other frameworks: ISO/IEC 27001 · PCI DSS · SOC 2 · SOX (Sarbanes-Oxley) Section 404 · NIST Cybersecurity Framework · NIST SP 800-53 · All frameworks