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/Common issues/Data at rest without the encryption you intended

Medium severity

Data at rest without the encryption you intended

Volumes, snapshots or databases created without encryption, or without the customer-managed keys your policy requires.

Updated 13 October 2026

What it looks like in each cloud

AWS

EBS volumes and snapshots without encryption, EBS default encryption off in a region, RDS instances with storage encryption disabled.

Google Cloud

Persistent disks and Cloud SQL instances are encrypted by Google by default; the gap is resources that must use customer-managed keys (CMEK) and do not.

Azure

Managed disks and storage accounts using platform-managed keys where policy requires customer-managed keys, or disk encryption disabled on VMs.

Why it matters

Encryption at rest is table stakes for every framework and most customer contracts. The failure mode is quiet: one old region without default encryption, or a snapshot copied without it, and the attestation is wrong.

How it happens

Default encryption is a per-region setting that was never enabled in the regions added later. Snapshots and copies inherit whatever the source had. Key policies are written for new resources and old ones are left alone.

How to check

Enumerate every volume, snapshot, database and storage account, with its encryption state and key type, and compare against the policy for the data it holds.

How to fix it

Turn on default encryption in every region, re-create or copy unencrypted resources with encryption, and apply customer-managed keys where the data classification calls for it.

Frameworks that require this

The controls this issue falls under. AKRIBOS reports the finding once and maps it to each framework you have in scope.

CIS Benchmarks

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).

SOC 2

CC6.1 (protection of data at rest) and C1.1 (confidential information) when Confidentiality is in scope.

ISO/IEC 27001

A.8.24 Use of cryptography.

DORA

Art. 9(3) protection of data, Art. 9(4)(d) cryptographic keys.

NIS2

Art. 21(2)(h) cryptography and encryption.

PCI DSS v4

Req. 3.5 (stored PAN unreadable), 3.6 and 3.7 (key management).

NIST CSF 2.0

PR.DS-01 (data at rest protected).

BSI C5

CRY (encryption of data at rest, key management).

DNB Good Practice Information Security

Cryptography.

How AKRIBOS handles it

AKRIBOS finds this during a read-only review of every connected account, project and subscription, shows the exact resource and setting behind the finding, and ranks it by the attack path it enables rather than in isolation. The fix is proposed as CLI commands or Terraform for you to review and approve, and the approval is recorded in the audit trail together with the compliance controls it satisfies.

Related issues

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.

Read more

Root or owner account without MFA

Critical

The most privileged identity in the account protected by a password alone.

Read more

Database reachable from the internet

Critical

A managed database with a public address and a firewall that lets the world in.

Read more
All common issues

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.