RDS snapshot is public

Severity: High
Service: RDS
Check ID: RDS_PUBLIC_SNAPSHOT

What this check finds

This is a copy of the contents of a database and may contain sensitive information. These are very easy for attackers to find.

Passing looks like: RDS snapshots are private.

How to fix it

Make the RDS snapshot private.

AWS CLI

aws rds modify-db-snapshot-attribute --db-snapshot-identifier SNAPSHOT_ID --attribute-name restore --values-to-remove all

Names in capitals are placeholders for your own resource. Review a command before you run it.

AWS console

RDS → Snapshots → select snapshot → Actions → Share snapshot → remove 'all'.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to RDS snapshot is public
Framework	Controls
PCI-DSS v4.0.1	3.5 Primary account number (PAN) is secured wherever it is stored
NIST SP 800-53 Rev5 (Moderate)	AC-3 Access Enforcement SC-7 Boundary Protection
NIST Cybersecurity Framework 2.0	PR.AA-05 Access permissions and authorizations are enforced with least privilege PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
ISO/IEC 27001:2022 Annex A	A.5.15 Access control A.8.20 Networks security

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More RDS checks

All RDS checks