Compliance program

CIS Controls v8.1 Close gaps, show proof

The Center for Internet Security (CIS) Controls are prioritized Safeguards against the most prevalent cyber attacks. "Ransomware grew again to 48% of all breaches," the Verizon 2026 Data Breach Investigations Report found. We check your security against the Controls, close gaps in planned steps and keep evidence current.

Who it is for
Any organization that wants widely used security basics to build on
How it runs
A project to assess and set up, then quarterly maintenance
What you get
CIS control mapping, gap report, roadmap and evidence package

What the CIS Controls v8.1 are

There are 18 CIS Critical Security Controls, each covering one area of security, such as your list of devices, user accounts or data recovery. Together they hold 153 Safeguards, and each Safeguard asks you to do one thing. A volunteer community has developed them since 2008.

Version 8.1 is still the current version in November 2026. CIS announced it on June 25, 2024, as a small update to v8 that works with earlier versions.

The update added a Govern function, taken from version 2.0 of the Cybersecurity Framework (CSF) by the National Institute of Standards and Technology (NIST). According to CIS, Govern helps organizations identify their policies and processes, and gives them "the evidence needed to demonstrate industry compliance".

CIS says almost all successful cyber attacks exploit "poor cyber hygiene". The Controls are prioritized, so you know which basics to put in place first.

Which CIS Implementation Group fits you

Implementation Groups (IGs) are how CIS sets priorities, and it says every organization should start with IG1.

  • 01Implementation Group 1CIS calls IG1 essential cyber hygiene and an emerging minimum standard for all organizations. Its 56 Safeguards aim at common attacks rather than targeted ones.
  • 02Implementation Group 2Adds 74 Safeguards, 130 in all, for organizations that employ technology staff and hold sensitive client information. Some of these Safeguards need enterprise-grade tools and specialist skills.
  • 03Implementation Group 3Adds the last 23, all 153 in total, for organizations that employ security specialists, answer to regulators and face skilled attackers aiming at them.

A CIS IG1 checklist in plain words

IG1's 56 Safeguards reach 15 of the 18 Controls, and CIS's Controls Navigator lists every Safeguard with its group.

  • Know your devices and softwareKeep lists of your devices and software, deal with unauthorized devices every week and check at least monthly that your software is still supported (Safeguards 1.1, 1.2, 2.1 and 2.2).
  • Control accounts and sign-insKeep a list of accounts and check it at least quarterly. Use unique passwords, disable unused accounts, keep admin accounts separate and require multi-factor authentication (MFA) for remote access, apps open to the internet and admin access (5.1 to 5.4, 6.3 to 6.5).
  • Install updates on a schedulePatch operating systems and apps automatically, monthly or more often, and keep a plan for fixing weak spots that you review at least monthly (7.2 to 7.4). Laptops that work offline are no exception, as our guide to patching laptops in the field explains.
  • Use secure settingsSet up computers and network equipment securely, and check monthly that network equipment runs current software. Lock idle sessions, run firewalls on servers and staff devices, and deal with the default accounts devices ship with (4.1 to 4.7, 12.1).
  • Protect sensitive dataKnow where it lives, limit who can open it, keep it only as long as you need it, dispose of it safely and encrypt the data on staff devices (3.2 to 3.6).
  • Keep audit logsCollect audit logs, the records of activity on your systems, and keep enough storage for them (8.2, 8.3).
  • Block common threatsUse supported browsers and email programs, filter out known dangerous websites, and run anti-malware that updates itself, with autorun turned off for removable drives (9.1, 9.2, 10.1 to 10.3).
  • Back up and keep a copy apartRun automated backups weekly or more often, protect the backup data and keep an isolated copy (11.2 to 11.4).
  • Train your peopleTrain staff at hire and at least once a year on scams, safe sign-ins, handling data, accidental data exposure, reporting incidents, spotting missing updates and the risks of unsafe networks (14.1 to 14.8).
  • Track your service providersKeep a list of the outside companies you rely on and review it every year (15.1).
  • Prepare for incidentsName the people who handle incidents, check your reporting contacts every year and give staff a set way to report an incident (17.1 to 17.3).
  • Write your processes downKeep written processes for data, secure settings, vulnerabilities, audit logs and data recovery, reviewed every year or after major changes (3.1, 4.1, 4.2, 7.1, 8.1, 11.1).

From CIS Controls gap assessment to maintenance

The first five steps are a project, and the last one repeats every quarter.

  1. 01 ScopeWe look at the factors CIS gives for choosing a group: size, data types, resources, threats and risk. You approve the scope and the group.
  2. 02 AssessWe check each Safeguard in your group against how your systems run today and list what is missing.
  3. 03 MapWe build a CIS control mapping that shows which systems, tools and written processes meet which Safeguards.
  4. 04 PlanYou get a gap report and a roadmap that puts the fixes in planned steps.
  5. 05 FixWe make the fixes you approve, or document them for your team or another provider to carry out.
  6. 06 MaintainEvery quarter, we review the program and bring the evidence package up to date, organized for a review or an audit.

How CIS maps to NIST CSF 2.0, HIPAA and NERC CIP

CIS's v8.1 Navigator links the Safeguards to frameworks including NIST CSF 2.0, the Health Insurance Portability and Accountability Act (HIPAA) and the North American Electric Reliability Corporation's Critical Infrastructure Protection (NERC CIP) Standards for the power grid. On November 9, 2026, CIS also published a mapping of v8.1 to version 2 of the Cross-Sector Cybersecurity Performance Goals (CPGs) from the Cybersecurity and Infrastructure Security Agency (CISA).

CIS states that its Controls are "not a replacement for any existing regulatory, compliance, or authorization scheme". Its mappings to other frameworks are meant as "a starting point for action".

For health care, and for critical infrastructure organizations connected to electric utilities, our HIPAA compliance and IT-scoped NERC CIP programs start from those rules. Our NIST CSF program tracks how mature your security is across that framework's six areas.

What a CIS Controls program can and cannot promise

Our program aligns your security with the CIS Controls and keeps organized evidence that shows it. It does not certify you, and it does not replace a formal CIS assessment by an outside firm.

CIS's accreditation program is for service providers. It gives the provider, not its clients, a "stamp of approval".

Some gaps cannot be closed without downtime, vendor support or a business exception. Accepting that risk is a business decision, and it stays with you.

What we assess and fix, What you approve and decide

CyberBlip

  • Assess your controls against your group
  • Map your setup to the Safeguards
  • Make approved fixes, or write them up for your team
  • Update the evidence every quarter
  • Report progress and what to fix next

You

  • Approve the scope and the Implementation Group
  • Authorize every change to your systems
  • Make the business and risk decisions
  • Name a person inside to own the program
  • Review the evidence we collect

Questions about the CIS Controls

We are a small business with no security staff. Is IG1 realistic?

Yes. CIS describes the typical IG1 organization as small to mid-sized, with limited technology and security know-how, and IG1 Safeguards are meant to work with common off-the-shelf hardware and software. We work fully managed, alongside your in-house team, or for a single project.

Does IG1 require a penetration test?

No. Penetration testing is CIS Control 18, and none of its Safeguards are in IG1. The same is true of Control 13 (network monitoring) and Control 16 (application software security). If your group or a customer calls for a test, we run penetration testing as a project with our testing partner.

Is a CIS Controls program a one-time project?

No. After the first project, we review the program every quarter. CIS says Safeguard work "is not a one-time activity" because environments, threats and business goals change, and many IG1 Safeguards run on a schedule of their own.

Are the CIS Controls free to use?

Yes. CIS says the Controls are "free to use by anyone to improve their own cybersecurity." The work is in checking each Safeguard against your systems, closing the gaps and keeping the records up to date, and that is the part we take on with you.

How is this different from a cybersecurity risk assessment?

A cybersecurity risk assessment looks at your security risks broadly and ranks what to fix first. A CIS Controls program checks you Safeguard by Safeguard against the group you choose, and the work continues each quarter. If you have not settled on a standard yet, the risk assessment can come first.

Sources

Show all 14 sourcesHide sources
  1. 2026 Data Breach Investigations Report Verizon, 2026
  2. CIS Critical Security Controls Center for Internet Security
  3. CIS Critical Security Controls Version 8.1 Center for Internet Security
  4. Center for Internet Security (CIS) Releases CIS Controls v8.1 with New Governance Recommendations Center for Internet Security, 2024-06-25
  5. The 18 CIS Critical Security Controls Center for Internet Security
  6. CIS Critical Security Controls Implementation Groups Center for Internet Security
  7. CIS Critical Security Controls Implementation Group 1 Center for Internet Security
  8. CIS Critical Security Controls Implementation Group 2 Center for Internet Security
  9. CIS Critical Security Controls Implementation Group 3 Center for Internet Security
  10. Guide to Implementation Groups (IG): CIS Critical Security Controls v8.1 Center for Internet Security, 2024-11-25
  11. CIS Controls Navigator v8.1 Center for Internet Security
  12. CIS Controls FAQ Center for Internet Security
  13. CIS Controls Accreditation Center for Internet Security
  14. CIS Controls v8.1 Mapping to CISA's Cross-Sector CPGs v2 Center for Internet Security, 2026-11-09

Next step

Find out where you stand

Tell us how we can best support you.

Icons: Tabler Icons, MIT License. License text: /licenses/tabler-icons.txt