Latest feature: Compare your cloud architecture against known frameworks such as NIS and SOC2.Compare your cloud against NIS and SOC2.

Book a demo
AKRIBOS AI
ProductComplianceEngineersSecurityFAQ
Sign InTry AKRIBOSTry AKRIBOS
Home/Compliance/CIS Benchmarks

CIS Benchmarks

The baseline configuration standard for AWS, Google Cloud and Azure.

Updated 13 October 2026

The CIS Foundations Benchmarks are consensus-built configuration guides published by the Center for Internet Security, one each for AWS, Google Cloud and Azure. Unlike most frameworks they are prescriptive: each recommendation names a specific setting, the value it should have and how to verify it.

That makes CIS the natural starting point. It is what SOC 2 and ISO 27001 auditors usually accept as evidence that cloud infrastructure is configured securely, and it is the baseline most cloud security tooling measures against.

Official text: CIS Benchmarks at the Center for Internet Security.

Who needs it

Any team running production workloads in AWS, Google Cloud or Azure. CIS is often required by customers, cyber-insurers and partners before they sign, and it is the quickest way to show an auditor that the technical side of a SOC 2 or ISO 27001 scope is in order.

Two levels, one baseline

Each benchmark splits its recommendations into Level 1, settings every environment should have and that carry little operational impact, and Level 2, defence-in-depth settings for environments that need them. Most teams close every Level 1 gap first and decide on Level 2 per workload.

Where the benchmark stops

CIS tells you whether a setting is right, one setting at a time. It does not tell you whether two individually acceptable settings add up to an exposure, which is where most real incidents start. AKRIBOS reads your estate as a whole first and maps what it finds back to the benchmark, so a failing recommendation is shown together with the attack path it enables.

What CIS asks of your cloud

The control areas that map onto infrastructure configuration in AWS, Google Cloud and Azure.

Identity and access

MFA on the root or owner account, no root access keys, password and key-rotation policies, and no policies that grant full administrative rights.

Storage

Public access blocked on object storage, encryption on block storage and databases, and no publicly reachable database instances.

Logging

Audit trails enabled in every region, log file validation on, configuration recording on, and logs encrypted and retained.

Monitoring

Alerts on unauthorised API calls, console sign-ins without MFA, use of the root account, and changes to IAM, network and logging configuration.

Networking

No administrative ports open to the whole internet, default security groups that allow nothing, and flow logs on every network.

How AKRIBOS checks CIS

Mapped to your resources

Every CIS control is evaluated against the actual accounts, roles, networks and storage in your estate, with the setting behind each result.

Findings come with the fix

A failing control is shown with the exact change as CLI commands or Terraform. You review and approve; nothing is applied on its own.

Evidence over time

Scheduled reviews and a full audit trail give you a dated record of each control for the whole audit period, not just the day of the audit.

Common issues under CIS

Misconfigurations that fail CIS controls, with the control reference for each.

Storage bucket open to the internet

Critical

Object storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.AWS Foundations 2.1.4 (Block Public Access); Google Cloud Foundations 5.1 (no anonymous or public access); Azure Foundations 3.x (public access on blob containers disallowed).

Read more

Root or owner account without MFA

Critical

The most privileged identity in the account protected by a password alone.AWS Foundations 1.4 (no root access key), 1.5 and 1.6 (MFA and hardware MFA for root); Google Cloud Foundations 1.2 (MFA for all users); Azure Foundations 1.1.x (MFA for privileged users).

Read more

Database reachable from the internet

Critical

A managed database with a public address and a firewall that lets the world in.AWS Foundations 2.3.3 (RDS instances not publicly accessible); Google Cloud Foundations 6.x (Cloud SQL not open to the world, SSL required); Azure Foundations 4.x (public network access disabled).

Read more

Snapshots or machine images shared publicly

Critical

Disk snapshots, database snapshots or machine images that anyone with a cloud account can copy.Not covered by the Foundations Benchmarks; AKRIBOS reports it anyway.

Read more

Over-permissive IAM policies

High

Identities, often service accounts, that can do anything in the account because a wildcard or a basic role was easier than a scoped policy.AWS Foundations 1.16 (no policies with full administrative privileges); Google Cloud Foundations 1.x (service account and basic role restrictions); Azure Foundations 1.x (custom roles with limited scope).

Read more

SSH or RDP open to 0.0.0.0/0

High

Management ports reachable from any address on the internet.AWS Foundations 5.2 and 5.3 (no ingress from 0.0.0.0/0 or ::/0 to administrative ports); Google Cloud Foundations 3.6 and 3.7; Azure Foundations 6.x (RDP and SSH not open from the internet).

Read more

Audit logging incomplete

High

Gaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.AWS Foundations 3.1 (CloudTrail in all regions), 3.2 (log file validation), 3.8 and 3.9 (S3 data events); Google Cloud Foundations 2.1 (audit logging configured); Azure Foundations 5.x (diagnostic settings and Activity Log retention).

Read more

Long-lived or unused credentials

High

Access keys, service account keys and client secrets that never rotate and are no longer needed.AWS Foundations 1.12 (credentials unused for 45 days disabled), 1.13 (one active key per user), 1.14 (keys rotated every 90 days); Google Cloud Foundations 1.4 and 1.7 (service account keys); Azure Foundations 1.x (unused accounts and credentials).

Read more

Instance metadata without session tokens

High

Compute instances that answer metadata requests, including their temporary credentials, to any process that can reach the local metadata address.AWS Foundations 5.6 (EC2 metadata service requires IMDSv2).

Read more

Trust policies open to any account

High

Roles or bindings that let identities outside your organisation assume access, often for a vendor integration that was set up too generously.Not covered directly by the Foundations Benchmarks; AKRIBOS reports it as part of the attack-path analysis.

Read more

Data at rest without the encryption you intended

Medium

Volumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.AWS Foundations 2.2.1 (EBS volume encryption), 2.3.1 (RDS encryption at rest); Google Cloud Foundations 4.x (CMEK on disks); Azure Foundations 7.x (disk encryption).

Read more

Transport encryption not enforced

Medium

Endpoints that still accept plaintext or outdated TLS, even though an encrypted path exists.AWS Foundations 2.1.1 (S3 bucket policy denies HTTP requests); Google Cloud Foundations 6.x (Cloud SQL requires SSL); Azure Foundations 3.1 and 3.x (secure transfer required, minimum TLS 1.2).

Read more

Network flow logs off

Medium

No record of which addresses talked to which, so traffic to and from a compromised host cannot be reconstructed.AWS Foundations 3.7 (VPC flow logging in all VPCs); Google Cloud Foundations 3.8 (VPC Flow Logs on every subnet); Azure Foundations 6.x (NSG flow logs with retention).

Read more

Default network with permissive rules

Medium

Workloads running in the cloud-created default network, which ships with rules nobody would write deliberately.AWS Foundations 5.4 (default security group restricts all traffic); Google Cloud Foundations 3.1 (default network does not exist in a project).

Read more

CIS questions

Which benchmarks does AKRIBOS check?

The CIS Foundations Benchmarks for AWS, Google Cloud and Azure. Every recommendation is shown with the resource, the setting behind the result and the fix.

Is CIS compliance a certification?

No. CIS publishes the benchmarks; there is no certificate. Teams use the benchmark as the technical baseline for SOC 2, ISO 27001 and customer security reviews, and share their results as evidence.

Level 1 or Level 2?

Start with Level 1 across the board, then apply Level 2 where the workload warrants it. Both levels are part of the benchmark, so you can see the Level 2 gap before you commit to closing it.

Does a passing benchmark mean we are secure?

It means your settings match a well-chosen baseline. It does not catch exposures that come from the combination of resources, such as a role with broad permissions that a public workload can assume. AKRIBOS reports those as attack paths alongside the benchmark results.

Other frameworks

SOC 2

Evidence that your cloud controls work, not just that they exist.

Read more

ISO/IEC 27001

The international standard for an information security management system, applied to your cloud.

Read more

DORA

The EU Digital Operational Resilience Act, applied to the cloud behind your financial services.

Read more

NIS2

EU-wide cyber risk-management obligations for essential and important entities.

Read more

PCI DSS v4

Requirements for every environment that stores, processes or transmits cardholder data.

Read more

NIST CSF 2.0

The US framework of outcomes: Govern, Identify, Protect, Detect, Respond, Recover.

Read more

BSI C5

Germany's cloud computing compliance criteria catalogue.

Read more

DNB Good Practice Information Security

What De Nederlandsche Bank expects of the financial institutions it supervises.

Read more
All frameworks

Attackers don't wait for your next audit. Neither does AKRIBOS.

Connect AWS, Google Cloud or Azure and get your first review today.

Run your first reviewRun your first review
Cinematic desert landscape at dusk with a lone silhouette standing before a warm amber glow, surrounded by dark rolling hills and a deep blue sky.
AKRIBOS

The AI agent that reviews and hardens your cloud, right from your terminal or our dashboard.

Navigation

How It WorksAttack PathsContinuous ReviewsComplianceCommon Cloud IssuesFor EngineersSecurityFAQ

Information

ContactPrivacy PolicyTerms of ServiceData Processing AgreementResponsible Disclosure

Socials

LinkedIn

© 2026 AKRIBOS AI B.V. All rights reserved.

AKRIBOS is a trade name of AKRIBOS AI B.V., registered with the Netherlands Chamber of Commerce (KvK) under number 83548335, Amsterdam, The Netherlands.