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/Snapshots or machine images shared publicly

Critical severity

Snapshots or machine images shared publicly

Disk snapshots, database snapshots or machine images that anyone with a cloud account can copy.

Updated 13 October 2026

What it looks like in each cloud

AWS

EBS snapshots, RDS snapshots or AMIs with public launch or copy permissions.

Google Cloud

Compute Engine images or snapshots with IAM bindings for allUsers or allAuthenticatedUsers.

Azure

Images published to a community gallery, or managed images shared beyond the intended tenant.

Why it matters

A snapshot is a complete copy of the disk: application code, configuration files and whatever secrets were on it. Public snapshots are routinely harvested for credentials.

How it happens

A snapshot is made public to share it with another account, because cross-account sharing felt harder, and is never made private again.

How to check

List every snapshot and image with its sharing permissions, and flag public or overly broad grants.

How to fix it

Make the snapshot private, share it with specific account IDs or projects instead, and block public sharing at the account or organisation level where the cloud offers 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

Not covered by the Foundations Benchmarks; AKRIBOS reports it anyway.

SOC 2

CC6.1 (logical access to data) and CC6.6 (external boundaries).

ISO/IEC 27001

A.8.3 Information access restriction, A.5.14 Information transfer.

DORA

Art. 9(3) confidentiality of data.

NIS2

Art. 21(2)(i) access control and asset management.

PCI DSS v4

Req. 3 (stored account data protected), 7.2 (need to know).

NIST CSF 2.0

PR.DS-01 (data at rest), PR.AA-05 (access).

BSI C5

AM (asset handling), IDM (access).

DNB Good Practice Information Security

Data classification; logical access management.

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.