Last updated: 16 November 2026
Quick answer: CIS Controls v8.1 is the current version of the Center for Internet Security’s prioritised set of 18 security controls and 153 safeguards. It keeps the v8 structure, adds the Govern function from NIST CSF 2.0, refines asset classes and definitions, and uses three Implementation Groups so organisations can start with 56 essential safeguards.
Most security leaders do not need another framework. They need a clear order of work. That is what the CIS Controls offer: a short, prioritised list of defensive actions that tackle the most common attacks first, with enough detail to hand directly to an operations team.
This guide explains what changed in CIS Controls v8.1, how the 18 controls and Implementation Groups work, how v8.1 maps to NIST CSF 2.0, ISO 27001 and NIS2, and how to run a practical gap assessment.
What is CIS Controls v8.1?
CIS Controls v8.1 is an update to version 8 published by the Center for Internet Security (CIS). It keeps the same 18 controls and 153 safeguards but improves the wording, definitions and framework alignment, so existing v8 programmes can move across without rework.
According to the CIS Controls v8.1 overview, the main changes are realigned mappings to NIST CSF 2.0, the addition of the Govern security function, revised asset classes with updated safeguard mappings, an expanded glossary, clarifications to certain safeguard descriptions and minor typographical corrections. CIS says v8.1 provides backwards compatibility with previous versions.
The controls are free to download and are written for organisations of any size. Unlike ISO 27001, they are not a management system standard and there is no formal certification against them. Their value is prioritisation.
What changed from CIS Controls v8 to v8.1?
The changes in v8.1 are refinements, not a redesign. The control numbers, safeguard numbers and Implementation Group structure stay the same, which matters if you have already mapped evidence to v8.
| Area | CIS Controls v8 | CIS Controls v8.1 |
|---|---|---|
| Controls and safeguards | 18 controls, 153 safeguards | 18 controls, 153 safeguards |
| Security functions | Identify, Protect, Detect, Respond, Recover | Adds Govern, in line with NIST CSF 2.0 |
| Framework alignment | Mapped to NIST CSF 1.1 | Realigned to NIST CSF 2.0 |
| Asset classes | Original asset classes | Revised asset classes and updated safeguard mappings |
| Glossary | Basic definitions | Expanded glossary with defined terms |
| Safeguard text | Original descriptions | Clarified descriptions and corrections |
The Govern function is the most visible change. Tagging safeguards by security function, now including Govern, makes it easier to show a board or auditor which parts of your programme are about oversight and which are about technical protection.
Common mistake: Treating v8.1 as a new project. If your team already tracks v8 safeguards, the practical work is to update descriptions, asset class tags and function tags in your control library, not to restart the assessment.
What are the 18 CIS Controls?
The 18 CIS Controls run from asset inventory through to penetration testing, in a deliberate order: you cannot protect what you do not know you have. The official CIS Controls list names them as follows.
- Inventory and Control of Enterprise Assets
- Inventory and Control of Software Assets
- Data Protection
- Secure Configuration of Enterprise Assets and Software
- Account Management
- Access Control Management
- Continuous Vulnerability Management
- Audit Log Management
- Email and Web Browser Protections
- Malware Defenses
- Data Recovery
- Network Infrastructure Management
- Network Monitoring and Defense
- Security Awareness and Skills Training
- Service Provider Management
- Application Software Security
- Incident Response Management
- Penetration Testing
Controls 1 to 6 are the foundation: know your assets and software, protect data, configure securely and control accounts and access. Controls 7 to 13 are about continuous defence. Controls 14 to 18 cover people, suppliers, software development, response and testing.
How do CIS Implementation Groups work?
Implementation Groups (IGs) divide the 153 safeguards into three cumulative tiers based on an organisation’s resources and risk. IG1 is the minimum for everyone, IG2 adds safeguards for organisations with more complex environments, and IG3 covers all safeguards for those facing sophisticated attackers.
| Group | Safeguards | Typical organisation |
|---|---|---|
| IG1 | 56 safeguards | Small or mid-sized organisation with limited IT and security staff |
| IG2 | IG1 plus 74 more (130 in total) | Organisation with multiple departments, dedicated IT staff and regulatory obligations |
| IG3 | IG1 and IG2 plus 23 more (all 153) | Organisation with security specialists, sensitive data and regulatory or targeted-attack exposure |
CIS describes IG1 as essential cyber hygiene, a foundational set of 56 safeguards that every enterprise should apply to guard against the most common attacks. The IG2 and IG3 counts above come from CIS’s own Implementation Group pages.
Which IG1 safeguards matter most?
Every IG1 safeguard counts, but a handful give most organisations the fastest reduction in risk:
- 1.1 Establish and maintain a detailed enterprise asset inventory.
- 2.1 Establish and maintain a software inventory.
- 4.1 Establish and maintain a secure configuration process.
- 5.1 Establish and maintain an inventory of accounts.
- 6.3 to 6.5 Require MFA for externally exposed applications, remote network access and administrative access.
- 7.1 Establish and maintain a vulnerability management process.
- 11.1 Establish and maintain a data recovery process.
- 14.1 Establish and maintain a security awareness programme.
- 17.1 Designate personnel to manage incident handling.
In practice: Choose your target IG per business unit, not only for the whole company. A regulated payments subsidiary may need IG3 while a small marketing office in the same group is well served by IG1.
How does CIS Controls v8.1 map to NIST CSF 2.0, ISO 27001 and NIS2?
CIS Controls v8.1 works best as the operational layer beneath a governance framework. NIST CSF 2.0 and ISO 27001 tell you what outcomes and management processes you need; CIS tells your team which technical safeguards to implement first.
NIST released version 2.0 of the Cybersecurity Framework in February 2024, adding the Govern function. CIS v8.1’s realignment means each safeguard now maps to a CSF 2.0 function, so you can report CIS progress in CSF terms. Our overview of the NIST Cybersecurity Framework covers the CSF side.
In the EU, Article 21(2) of the NIS2 Directive lists minimum cybersecurity risk-management measures, including incident handling, business continuity and backups, supply chain security, vulnerability handling, cyber hygiene and training, cryptography, access control and asset management, and multi-factor authentication. CIS safeguards give concrete ways to meet many of them, although NIS2 also requires governance, reporting and management accountability that CIS does not cover.
| Requirement area | CIS Controls v8.1 | ISO 27001:2022 Annex A | NIS2 Article 21(2) |
|---|---|---|---|
| Asset inventory | Controls 1 and 2 | 5.9 Inventory of information and other associated assets | (i) asset management |
| Access and MFA | Controls 5 and 6 | 5.15 to 5.18, 8.5 | (i) access control, (j) MFA |
| Vulnerabilities | Control 7 | 8.8 Management of technical vulnerabilities | (e) vulnerability handling and disclosure |
| Backups | Control 11 | 8.13 Information backup | (c) backup management and disaster recovery |
| Training | Control 14 | 6.3 Awareness, education and training | (g) cyber hygiene and training |
| Suppliers | Control 15 | 5.19 to 5.22 | (d) supply chain security |
| Incidents | Control 17 | 5.24 to 5.28 | (b) incident handling |
Treat the table as a starting point for your own mapping, not an official crosswalk. CIS publishes its own mappings to other frameworks, which you should use for audit purposes. For ISO-certified organisations, CIS safeguards can also serve as implementation guidance behind your ISO 27001 Annex A controls.
Maintaining these mappings by hand across several frameworks is slow. Enactia’s AI-powered GRC platform cross-maps CIS Controls, NIST CSF, ISO 27001 and NIS2 in its Compliance Universe, so evidence for one safeguard counts wherever it applies. To try it with your own control set, start your 14-day free trial.
How do you run a CIS Controls v8.1 gap assessment?
Run the assessment safeguard by safeguard against your target IG, score both policy and implementation, and turn the gaps into a prioritised roadmap. Six steps cover most programmes.
- Set scope and target IG. Decide which entities, networks and cloud tenants are in scope and which IG each should reach.
- Collect evidence. For each safeguard, gather the policy, the configuration or report that shows it works, and the owner.
- Score consistently. Use a simple scale, for example not implemented, partially implemented, implemented on some systems, and fully implemented and automated.
- Prioritise. Fix IG1 gaps first, then focus on safeguards that address your highest risks in the risk register.
- Assign and track. Turn each gap into a task with an owner, due date and acceptance criteria.
- Reassess. Repeat at least annually and after major changes such as a cloud migration or acquisition.
CIS offers its own assessment tool, CIS CSAT, and a risk method, CIS RAM, which some teams use alongside their GRC tooling. Whatever tool you use, a structured compliance assessment with evidence attached to each safeguard makes the results defensible to auditors and regulators.
In practice: Measure implementation, not just policy. A written patching policy scores nothing if the vulnerability scanner shows critical findings older than your own deadline.
Key takeaways
- CIS Controls v8.1 keeps 18 controls and 153 safeguards and is backwards compatible with v8.
- The main changes are the Govern function, realignment to NIST CSF 2.0, revised asset classes and a larger glossary.
- IG1 covers 56 essential cyber hygiene safeguards; IG2 adds 74 and IG3 adds 23.
- CIS works best as the operational layer under NIST CSF, ISO 27001 or NIS2, not as a replacement.
- Score implementation with evidence and fix IG1 gaps first.
Frequently asked questions
What is the difference between CIS Controls v8 and v8.1?
CIS Controls v8.1 keeps the same 18 controls, 153 safeguards and three Implementation Groups as v8. It adds the Govern security function, realigns mappings to NIST CSF 2.0, revises asset classes and safeguard mappings, expands the glossary and clarifies some safeguard descriptions. CIS states that v8.1 is backwards compatible, so v8 work carries over.
How many safeguards are in CIS Controls v8.1?
There are 153 safeguards across 18 controls. Implementation Group 1 contains 56 safeguards, described by CIS as essential cyber hygiene. IG2 adds 74 safeguards for a total of 130, and IG3 adds the remaining 23, covering all 153. Organisations choose a target group based on their resources, data sensitivity and threat exposure.
Can you get certified against CIS Controls?
No formal certification exists for the CIS Controls in the way that accredited bodies certify ISO 27001. Organisations assess themselves or engage an independent assessor to review implementation. Many use CIS as practical guidance to meet the requirements of certifiable or regulatory frameworks such as ISO 27001, SOC 2 or NIS2.
Is CIS Controls v8.1 enough to comply with NIS2?
Not on its own. CIS safeguards help implement many of the technical measures in NIS2 Article 21(2), such as access control, multi-factor authentication, backups and vulnerability handling. NIS2 also requires management body accountability, risk analysis, incident reporting to authorities and supply chain governance, which need processes beyond the CIS safeguards.
Which Implementation Group should we target?
Start with IG1 regardless of size, because it covers the safeguards against the most common attacks. Move to IG2 if you have multiple business units, dedicated IT staff or regulated data. Consider IG3 if you hold highly sensitive data, face targeted attacks or regulators expect advanced capabilities such as penetration testing and application security.
Use CIS Controls v8.1 as your security to-do list
The strength of the CIS Controls is focus. They turn broad framework requirements into a concrete, ordered list of safeguards your team can implement, measure and improve. Pair them with a governance framework, keep one set of evidence, and report progress in the terms your board and regulators use. For a governance view, see our guide to the NIST CSF 2.0 Govern function.
To see how CIS, NIST CSF, ISO 27001 and NIS2 can run from one control library, contact us or book a demo or start your 14-day free trial.
