- CIS Benchmarks are consensus-developed configuration guides published by the Center for Internet Security, free to download as PDF for non-commercial use and covering more than 100 platforms across 25+ vendor product families
- They are distinct from CIS Controls: the Controls are 18 prioritised controls, broken down into specific safeguards (153 in version 8.1), that set what a security programme needs to do, while Benchmarks tell you exactly how to configure a specific system
- CIS's Community Defense Model v2.0 (2021) puts a number on the payoff: Implementation Group 1, the basic hygiene safeguards that secure configuration sits under, defends against 77% of the MITRE ATT&CK (sub-)techniques associated with malware in that model. It measures coverage of attack techniques, not a measured drop in real-world attacks
- Misconfiguration remains one of the most common root causes behind cloud and infrastructure breaches, which is why ISO 27001, PCI DSS and most audit frameworks expect a documented hardening baseline
- Implementing a Benchmark is not a one-off project. Without a tested rollout, an exceptions process and ongoing drift monitoring, systems move away from the baseline over time
What CIS Benchmarks actually are
A CIS Benchmark is a document that tells you, setting by setting, how to configure a specific operating system, cloud platform, piece of software or network device so that it is harder to attack. They are published by the Center for Internet Security (CIS), a US nonprofit, and cover the platforms most organisations actually run: Windows Server and desktop editions, the major Linux distributions, Amazon Web Services, Microsoft Azure, Google Cloud, Kubernetes and Docker, Microsoft 365, Google Workspace, common browsers, and network devices from vendors including Cisco and Palo Alto Networks. There are more than 100 Benchmarks in total, spanning over 25 vendor product families, and CIS updates each one as new platform versions ship.
CIS Benchmark recommendations go through a consensus process before publication. Volunteer subject-matter experts, drawn from industry, government and academia, propose, review and vote on each setting, which is why the guidance reads as practical operator advice rather than a vendor's own hardening documentation. Each recommendation is assessed as either "Automated", meaning a tool such as CIS-CAT can check compliance, or "Manual", meaning a person has to verify it because the setting cannot be checked reliably by a tool. Manual does not mean less important. These labels replaced the older "Scored" and "Not Scored" terms, which you may still see in older Benchmark versions.
The Benchmarks themselves are free to download as PDF for non-commercial use, under CIS's terms of use. What costs money is the tooling built around them. CIS-CAT Pro, part of CIS SecureSuite membership, is an assessment tool that checks a system against a Benchmark and produces a compliance score and remediation report. CIS Hardened Images are a separate product: virtual machine images pre-configured to a Benchmark and sold through the AWS, Azure, Google Cloud and Oracle Cloud marketplaces. A hardened image gives you a secure starting point for the operating system; it does not secure the applications and data you run on it. A free version, CIS-CAT Lite, offers limited features and covers a selected set of Benchmarks, for organisations that want to try automated assessment before committing to a paid tier.
CIS Benchmarks vs CIS Controls: the distinction that gets lost
CIS also publishes the CIS Controls, and the two are often confused in conversation, including inside IT teams that use both. The Controls are 18 prioritised controls, each broken down into specific safeguards (153 in version 8.1), with the safeguards assigned to three Implementation Groups, IG1 to IG3, by organisational maturity. They describe what a security programme needs to cover: asset inventory, access control, data protection, incident response, and so on. The safeguards are concrete and operational, but they stay platform-neutral. Benchmarks operate one level down, turning one of those controls, secure configuration, into exact, testable settings for a specific platform.
| Dimension | CIS Controls | CIS Benchmarks |
|---|---|---|
| Scope | Prioritised security safeguards for the whole organisation | Deep, platform-specific configuration |
| Answers | What security actions the organisation needs to take | How to configure a specific system to deliver that action |
| Example | Safeguard 4.1: establish and maintain a secure configuration process | Set the account lockout threshold to 5 attempts on Windows Server 2022 |
| Analogy | The blueprint for a secure building | The fitting instructions for a specific lock on a specific door |
The two are designed to work together rather than substitute for each other. CIS Control 4, Secure Configuration of Enterprise Assets and Software, addresses secure configuration at the programme level, and its Safeguard 4.1 calls for establishing and maintaining a documented secure configuration process. CIS Benchmarks are the platform-specific guidance most organisations use to put that process into practice, not a source the Control itself mandates over an equivalent baseline.
Who actually needs to care about this
The conceptual case for secure configuration is easy to agree with and easy to leave unactioned. It becomes concrete once you recognise your own situation in it. A Benchmark is worth implementing when you:
- Run Windows or Linux servers, virtual machines, or manage endpoints at any meaningful scale
- Operate Microsoft 365, Google Workspace or other SaaS platforms holding company data
- Run workloads in AWS, Azure or Google Cloud and want a baseline beyond the provider's own defaults
- Process payment card data, or handle other regulated or sensitive information
- Need documented, auditor-ready evidence of secure configuration for ISO 27001, PCI DSS, NIST CSF or NIS2
- Provision infrastructure through Terraform, Ansible or similar tooling and want systems configured to an approved baseline from the start
- Manage enough systems that configuration can no longer depend on whoever happened to build each one
None of that means implementing every recommendation on every system. The right baseline depends on the platform, the business requirement and what a given system can tolerate operationally, which is exactly what a phased rollout is for.
Why secure configuration is worth this much attention
Default configurations exist to get a system running with the fewest support calls, not to resist an attacker. Providers have tightened some defaults: Amazon S3 has blocked public access on new buckets by default since April 2023, and Microsoft enables security defaults, including MFA and blocking of legacy authentication, on new Entra ID tenants. A freshly installed server or a long-lived tenant can still favour convenience: broader permissions than most users need, legacy protocols left enabled for compatibility, logging turned down to reduce noise. None of that is a bug. It is simply not the configuration a security team would choose, and many organisations never go back and choose one deliberately.
That gap is where a large share of real-world incidents originate, and the cause usually lies in what happens after the defaults: permissions granted for a project, exceptions nobody revisits, integrations kept alive for legacy systems, changes made later. A storage bucket whose public-access block was switched off during a migration, a service account with far more privilege than it uses, a temporary firewall rule that was never removed: these are configuration failures, not zero-day exploits, and they are also the failures that are cheapest to prevent. Misconfiguration keeps showing up as a leading root cause in breach reports across cloud and self-hosted infrastructure alike, because complex platforms keep accumulating configuration changes that nobody checks against a baseline.
A Benchmark closes that gap by giving you a specific, tested answer instead of a general principle. "Harden your servers" is advice nobody can act on directly. "Disable SMBv1, enforce a minimum password length of 14 characters, disable the built-in guest account, and restrict anonymous SID and name translation" is something an engineer can implement and an auditor can verify. That specificity, multiplied across every setting a platform exposes, is the actual value of a Benchmark over generic hardening advice.
Without a Benchmark: "The server is hardened."
With a Benchmark: "The server was assessed against the CIS Windows Server Benchmark. Every Automated recommendation was checked by a tool, every Manual recommendation was reviewed by a person, and each one either passes or is logged as a documented exception with a compensating control."
Structure, levels and implementation
Two companion articles go deeper into the practical side.
Inside a CIS Benchmark covers the five-part structure every recommendation follows, the platforms Benchmarks exist for, and how to choose between Level 1 and Level 2.
Implementing CIS Benchmarks and using them in audits covers a phased rollout that avoids breaking production, how Benchmarks map to ISO 27001, PCI DSS and other frameworks, and the mistakes that most often undo the work.
How Cyvra helps
Cyvra's Cybersecurity Consultancy, Cybersecurity Assessment and Audits & Compliance services build secure configuration baselines that hold up under audit, not just on the day they are built.
- Benchmark-based hardening: Level 1 and Level 2 rollouts scoped to your actual estate, piloted before wider deployment
- Exceptions register: documented, auditor-ready records of any recommendation that can't be applied and why, with compensating controls where needed
- Drift monitoring: recurring compliance scanning so a hardened baseline stays hardened, not just at audit time
- Compliance mapping: secure configuration evidence mapped directly to ISO 27001, PCI DSS, NIST CSF and NIS2 requirements
We assess your current configuration against the appropriate CIS Benchmarks, document justified exceptions, prioritise remediation and produce evidence you can point to for ISO 27001, PCI DSS or other compliance programmes. Contact our Cybersecurity Consultancy or Audits & Compliance team to start with a configuration baseline review.