
The CIS Controls: Implementation Group 1 as a starting list
The CIS Controls are one of the few security frameworks that tell you what to do rather than what to achieve. That makes them usable for an organisation without its own security team, provided you do not try to do everything at once. This article explains how the framework is built, why Implementation Group 1 is the right way in, and how to work through it without the list ending up in a folder.
The CIS Controls cover eighteen topics with concrete measures underneath, called safeguards, divided into three implementation groups. Implementation Group 1 is the foundation and has 56 safeguards in version 8.
Choose your group by what you protect, not by how big you are. For most SMEs, IG1 is the start and, for now, also the finish.
Work through IG1 as a baseline with four columns: status, evidence, owner and next step. The goal is not 56 ticks, but one column further each year and no line slipping back.
What the CIS Controls are
The CIS Controls, in full the CIS Critical Security Controls, are a list of security measures from the Center for Internet Security, a US non-profit. The framework has eighteen controls: topics such as the inventory of devices, account management and data recovery. Underneath sit concrete measures, which CIS calls safeguards. Version 8 was published in 2021 and updated to version 8.1 in 2024.
Two things make it usable for organisations without a security team. Each safeguard is a single, testable action, for example: keep an inventory of devices and review it at set intervals. That is different from an objective such as “the organisation has visibility of its assets”. And the safeguards are divided into implementation groups, so you do not have to do everything at once.
Do not confuse them with the CIS Benchmarks. Those come from the same organisation but cover something else: the exact settings per product, such as a version of Windows or a web browser. The Controls say that you have a secure configuration; a Benchmark says what that looks like for one product. The latter is hardening, and a job of its own.
Three implementation groups: where you start
- IG1: the foundation. CIS itself calls this “essential cyber hygiene”. Intended for organisations with limited IT expertise in house and data that is not especially sensitive. In version 8 that is 56 safeguards.
- IG2: IG1 and more. For organisations with their own IT staff, several departments or sites, and data that is sensitive or subject to stricter rules.
- IG3: everything. For organisations with a security team, and with data or services where an attack has serious consequences for others.
The groups stack: whoever does IG2 also does IG1. Choose your group by what you protect, not by how big you are. A small practice holding medical records belongs in IG2 sooner than a larger business with a web shop and little sensitive data.
IG1 as a starting list for SMEs
For most SMEs, IG1 is the right start, and often the finish for the time being. It is a list you can put in a spreadsheet, with an honest answer on every line. In plain English it covers:
- Inventory (controls 1 and 2): which devices and which software you have, and what you do with anything that should not be there.
- Data and configuration (3 and 4): knowing where sensitive data sits and how long you keep it, encrypting devices, screen locking, firewalls on, default accounts removed.
- Accounts and access (5 and 6): a list of accounts, unique passwords, separate admin accounts, disabling dormant accounts, MFA for external access and administration, and revoking access when people leave.
- Vulnerabilities and logs (7 and 8): a process for updates, automatic patching of operating systems and applications, and logging that is switched on and retained.
- Email, browser and malware (9 and 10): only supported browsers and email clients, DNS filtering, anti-malware that updates itself.
- Recovery (11): automated backups, protected recovery data, an isolated copy and a recovery process.
- Network (12): network equipment kept up to date.
- People, suppliers and incidents (14, 15 and 17): an awareness programme, a list of service providers, and knowing who does what, and whom to call, in an incident.
Three controls are not in IG1: network monitoring (13), application security (16) and penetration testing (18). That is not a judgement that they are unimportant, but that they only pay off once the foundation is in place. A pen test on an estate without an inventory mostly tells you what you could already have known.
How to work through IG1
Do not start by buying; start with a baseline per safeguard. Four columns are enough:
- Status: not, partly, largely or everywhere. “Partly” is the honest answer on almost every line, and the most interesting one.
- Evidence: how you can see it. A setting, a report, a list. No evidence means “not”, even if the policy says so.
- Owner: one name per line.
- Next step: what it takes to move one column to the right.
Then work in blocks, not from 1 to 56. Inventory first, because without a list of devices and accounts you cannot mark any other line as “everywhere”. Then accounts and MFA, then backup and recovery, then the rest.
A scan fills in some of those columns but not all: a machine sees missing updates, not a recovery process. What a scan does and does not tell you is covered in IT security assessment. Repeat the baseline every year. The goal is not 56 times “everywhere”, but a column that moves along each year and no line that slips back.
CIS alongside ISO 27001, NIS2 and Cyber Essentials
The CIS Controls do not compete with the frameworks you already know; they make them concrete. CIS publishes its own mappings to, among others, the NIST Cybersecurity Framework and ISO/IEC 27001, so you can see which safeguard belongs to which requirement.
ISO 27001 asks for a management system: assess risks, choose and justify controls, and repeat that every year. How you carry out a control is largely left open. IG1 then fills in part of those controls; it does not replace the system around them.
Cyber Essentials, the UK government-backed scheme, has five technical controls that overlap heavily with IG1: firewalls, secure configuration, user access control, malware protection and security updates. IG1 goes further, with backup, logging, awareness and incident response. NIS2 does not prescribe the CIS Controls either; it asks for appropriate measures and national law decides how they are assessed. IG1 is a sound way to organise those measures and keep the evidence ready, not a substitute for what a regulator asks.
Where a CIS programme stalls
- Starting at IG2 or IG3 because it feels more complete. You end up with 153 safeguards all half in place, instead of 56 you can demonstrate.
- Mistaking Benchmarks for Controls and spending weeks on the settings of one product while the inventory does not yet exist.
- Ticking on policy. “We have a password policy” is no evidence of unique passwords; a report from the password manager is.
- Buying a tool per control. Much of IG1 is already in what you have, such as Microsoft 365 and your endpoint protection. The question is usually not whether it can be done, but whether it is switched on.
- No owner per line, so the spreadsheet disappears into a folder after the first baseline and starts again from zero a year later.
Where our work stops
What we do. We carry out the IG1 baseline with you, implement the technical safeguards in your environment (inventory, accounts and MFA, updates, backup, endpoint and email protection, logging) and record the evidence per line so you can show it. We are ISO/IEC 27001 certified; that says how we work, not how your environment stands.
What we do not do. We are not affiliated with the Center for Internet Security and do not speak on its behalf. The CIS Controls are not a certification standard, and we certify nobody: we do not issue a statement that you are “CIS compliant”, nor certify you for Cyber Essentials or ISO 27001. An accredited body assesses those, and what NIS2 legally requires of you is a question for a lawyer or the regulator, not for us.
Questions about the CIS Controls
The five we are asked most often.
What are the CIS Controls?
The CIS Controls are a list of eighteen security topics from the Center for Internet Security, with concrete measures underneath called safeguards. They are divided into three implementation groups, so an organisation can start with the foundation and expand later.
What is CIS Implementation Group 1 (IG1)?
IG1 is the first and smallest implementation group, described by CIS itself as essential cyber hygiene. In version 8 it has 56 safeguards covering inventory, accounts, updates, backup, malware protection, awareness and incident response, among others. It is aimed at organisations with limited IT expertise in house.
How many CIS Controls are there?
There are eighteen controls in versions 8 and 8.1. Beneath them are 153 safeguards, divided into three implementation groups that build on each other: IG1 is the foundation, IG2 contains IG1 plus further measures, and IG3 contains everything.
What is the difference between CIS Controls and CIS Benchmarks?
The Controls say which measures an organisation should take, such as having a secure configuration. The Benchmarks describe, per product such as a version of Windows or a browser, which settings make up that secure configuration. The Controls are the what; the Benchmarks are part of the how.
Can you get certified against the CIS Controls?
The CIS Controls are not a certification standard like ISO 27001 or Cyber Essentials. You can use them to organise measures and record evidence, and that evidence helps in an ISO 27001 audit or a NIS2 assessment. We certify nobody and do not issue statements of compliance.
Further reading
Where the CIS Controls connect.
Shall we baseline IG1 together?
We go through the 56 safeguards with you, fill in status, evidence and owner per line, and tell you the order in which to tackle them.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.