Skip to content
StratQuad

CIS Critical Security Controls

5 min read

A prioritised set of 18 controls and 153 safeguards, grouped so an organisation can start with essential hygiene and build up as its risk and resources grow.

At a glance

Owner
Center for Internet Security (CIS)
Version
v8.1
Published
25 Jun 2024
Applies to
Organisations of any size and sector; widely used by SMEs, managed service providers and as a mapping layer between other frameworks
Mandatory
Voluntary; sometimes required by contract, cyber insurers or US state law safe harbours
Assessed by
Self assessment, commonly with the free CIS Controls Self Assessment Tool (CSAT); no certification scheme
Cost model
Free to download after registration; commercial use of the content is licensed

Key points

  • 18 controls containing 153 safeguards, each a specific, measurable action.
  • Safeguards are split into three Implementation Groups. IG1 is 56 safeguards of essential hygiene, IG2 adds 74 and IG3 adds the final 23.
  • Version 8.1, released on 25 June 2024, adds a Govern security function in line with NIST CSF 2.0 and new asset classes. It did not change which safeguards sit in which Implementation Group.
  • There is no certification. The Controls are used for self assessment, as a roadmap, and as a common language for mapping to ISO/IEC 27001, NIST CSF, the CAF and Cyber Essentials.

What it is

The CIS Controls are a list of defensive actions, ranked by how effective each is against common attacks. They began in 2008, were long known as the SANS Top 20, and are now maintained by the Center for Internet Security, a US non profit, with input from practitioners across industry and government.

Where ISO/IEC 27001 tells you to run a management system and the CAF describes outcomes, the CIS Controls tell you what to do. A safeguard reads like "Establish and maintain a detailed enterprise asset inventory". That makes them useful as a working plan, especially for teams without the time to interpret outcome based frameworks.

The 18 controls

  • 1 Inventory and Control of Enterprise Assets
  • 2 Inventory and Control of Software Assets
  • 3 Data Protection
  • 4 Secure Configuration of Enterprise Assets and Software
  • 5 Account Management
  • 6 Access Control Management
  • 7 Continuous Vulnerability Management
  • 8 Audit Log Management
  • 9 Email and Web Browser Protections
  • 10 Malware Defences
  • 11 Data Recovery
  • 12 Network Infrastructure Management
  • 13 Network Monitoring and Defence
  • 14 Security Awareness and Skills Training
  • 15 Service Provider Management
  • 16 Application Software Security
  • 17 Incident Response Management
  • 18 Penetration Testing

The order is deliberate. Controls 1 and 2 come first because you cannot protect, patch or monitor assets you do not know about.

Implementation Groups

Implementation Groups decide where to start. Each group includes everything in the groups below it.

GroupSafeguardsCumulativeIntended for
IG15656Every organisation. CIS calls it essential cyber hygiene: the minimum defence against the most common, opportunistic attacks. Typically small organisations with limited IT staff.
IG274130Organisations with dedicated IT staff, several departments, sensitive data and regulatory obligations.
IG323153Organisations with security specialists, highly sensitive data or services, and exposure to targeted, sophisticated attackers.

Practitioner note

Pick an Implementation Group from your risk profile, not your size. A small payroll bureau or a care provider holding health data may need IG2 safeguards, such as centralised audit log collection (8.9) and a data classification scheme (3.7), well before it has the headcount IG2 assumes. Record the reasoning, so an auditor or insurer can see why some IG2 or IG3 safeguards are in scope and others are not.

What changed in v8.1

Changes from v8 to v8.1

  • Govern function. A new Govern security function identifies the policies, processes and plans an organisation needs to direct its programme and evidence it. It aligns the Controls with NIST CSF 2.0, which added Govern as its sixth function.
  • Security function mapping. Every safeguard's function mapping (Identify, Protect, Detect, Respond, Recover, Govern) was realigned to NIST CSF 2.0.
  • Asset classes. New asset classes were added and safeguard to asset mappings revised.
  • Wording. Several safeguard descriptions were clarified, and glossary terms such as "plan", "process" and "sensitive data" were expanded.
  • Implementation Groups unchanged. No safeguard moved between groups, so existing IG assessments remain valid.

CIS has since issued minor corrections as v8.1.x point releases. Check the change log before citing a safeguard's exact wording.

Using it in the UK

The CIS Controls have no legal standing in the UK, but they sit comfortably alongside UK schemes.

  • Cyber Essentials. Its five technical controls (firewalls, secure configuration, security update management, user access control and malware protection) are broadly covered by IG1. IG1 goes further on asset inventory, data recovery, audit logging and incident response, which Cyber Essentials does not assess.
  • CAF and DSPT. The Controls give concrete actions behind CAF outcomes such as B2 (identity and access control), B4 (system security), B5.c (backups) and C1 (security monitoring).
  • ISO/IEC 27001. CIS publishes mappings to Annex A. Many organisations use the Controls as the implementation detail beneath an ISMS.
  • CIS Benchmarks. These are separate documents: detailed secure configuration guides for specific operating systems and platforms. Safeguard 4.1 asks for a documented secure configuration process, and the Benchmarks are the usual way to meet it.

How it is assessed

There is no certification and no accredited assessor scheme. Organisations self assess, usually with CIS CSAT. Each safeguard is scored on whether a policy exists and how far it is implemented, automated and reported. Consultancies also offer independent assessments, but the result is a report, not a certificate.

Evidence expected

Credible evidence for IG1 includes: an asset inventory reconciled against discovery data (1.1), a software inventory (2.1), documented secure configuration baselines (4.1), an account inventory with disabled dormant accounts (5.1, 5.3), MFA on external applications and remote access (6.3, 6.4), patch records against defined timescales (7.3, 7.4), an isolated copy of recovery data (11.4), training records (14.1) and a named incident handler with contact details (17.1, 17.2).

Common gaps

Common nonconformity

  • Starting at Control 7 with a vulnerability scanner while Controls 1 and 2 are incomplete, so the scanner only sees known assets.
  • Treating IG1 as complete on the strength of policies, with no evidence the safeguards operate.
  • MFA on email but not on remote access, VPN or administrative accounts.
  • Backups taken but never restored under test, and no copy isolated from the production network.
  • Service providers (Control 15) with no inventory, no security requirements in contracts and no review.
  • Scoring every safeguard as partly implemented, which hides the few that matter most.

Relationship to other frameworks

The CIS Controls are prescriptive and technical. NIST CSF 2.0 and the CAF are outcome based, and ISO/IEC 27001 is a certifiable management system. They work best together: CSF or the CAF to describe the target, the CIS Controls to plan the work, and ISO/IEC 27001 where a certificate is needed. CIS publishes official mappings, and OpenCRE links them to other standards.

Sources

Suggest a correction