Skip to main content
Five Steps for Cloud Compliance Readiness·A practical playbook for security teamsDownload
Compliance

CIS AWS Benchmarks Compared: Four Benchmarks, 306 Controls, and Where Level 2 Sits

Four CIS AWS benchmarks, 306 controls in total. See how the Level 1 and Level 2 split differs per benchmark, and how to scan them read-only.

CConfigCobra Team17 November 20262 min read

CIS publishes more than one benchmark for AWS. ConfigCobra assesses four of them, with 306 controls in total. The benchmarks are not evenly balanced: some are almost entirely Level 1, and one is Level 2 from top to bottom. This post lays out the numbers so you can plan the order of your work.

The four benchmarks

BenchmarkVersionControlsLevel 1Level 2
CIS Amazon Web Services Foundations Benchmarkv7.0.0704129
CIS AWS Compute Services Benchmarkv2.0.0827210
CIS AWS Database Services Benchmarkv2.0.098935
CIS AWS Storage Services Benchmarkv1.0.056056

The counts add up: 70 + 82 + 98 + 56 = 306.

What the split tells you

Level 1 is the safer, minimal-impact profile. Level 2 is the stricter, security-focused one. Across the four benchmarks that works out to 206 Level 1 controls and 100 Level 2 controls, but the totals hide how different each benchmark is.

  • Foundations (70) is the most balanced: 41 Level 1 and 29 Level 2. It is the only one that mixes both profiles in meaningful numbers.
  • Compute (82) and Database (98) are mostly Level 1, with 10 and 5 Level 2 controls. Database is the largest of the four.
  • Storage (56) has no Level 1 controls at all. All 56 are Level 2, so there is no minimal-impact subset to start with.

Planning the order of work

The Level 1 controls across Compute and Database (72 and 93) make up most of the safe, minimal-impact work, so they are a sensible first pass. The Foundations benchmark mixes both levels, so it benefits from being read control by control rather than treated as one block. Storage deserves a deliberate plan: every one of its 56 controls is in the stricter profile, so each change is worth reviewing before it goes in.

Scanning without write access

ConfigCobra connects to AWS with read-only access via assume-role. It never writes to your AWS accounts. Your AWS accounts in scope are covered, and you can set the scan to run daily, weekly or monthly, or start an ad hoc scan whenever you need one.

Each control carries a severity estimate. That estimate is ConfigCobra's own prioritisation: CIS publishes no severity for its controls, so use it to order remediation, not as a benchmark rating.

Check the impact before you change anything

For a failing control, remediation impact analysis shows which AWS resources and identities a fix would affect, with an impact level of High, Medium, Low or None, before you apply it. That matters most for the stricter Level 2 controls. Your AWS resources also appear in the inventory next to your other clouds, with findings linked to the objects they concern.

Try it on your own AWS accounts

The 14-day free trial gives full access to every available module and control. If you would rather talk it through first, get in touch.

See this on your own tenant

ConfigCobra checks Microsoft 365, Azure, Google Cloud and AWS against the CIS benchmarks, read-only. 14-day free trial with full access.

Get in touch

Let's talk.

Whether you're evaluating ConfigCobra, running an audit, or managing a client fleet — we respond within one business day.

Free trial