Skip to main content

📝 AWS RDS Snapshot is publicly accessible 🟢

  • Contextual name: 📝 Snapshot is publicly accessible 🟢
  • ID: /ce/ca/aws/rds/snapshot-publicly-accessible
  • Located in: 📁 AWS RDS

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Similar Internal Rules​

RulePoliciesFlags
✉️ dec-x-b33429051

Logic​

Description​

Open File

Description​

Ensure that your AWS Relational Database Service (RDS) database snapshots are not publicly accessible (i.e., shared with all AWS accounts and users) to protect your private data.

Rationale​

RDS snapshots contain both the data and configurations of your database instances. If these snapshots are publicly accessible, unauthorized users can access sensitive information, leading to data breaches and other security issues. Keeping RDS snapshots private helps maintain the confidentiality and integrity of your data.

Publicly sharing an AWS RDS database snapshot grants another AWS account permission to copy the snapshot and create database instances from it. It is strongly recommended not to share your database snapshots with all AWS accounts. If necessary, you can share your RDS snapshots with specific AWS accounts without making them public.

Audit​

This policy marks an AWS RDS snapshot as INCOMPLIANT if the snapshot type is public or if the snapshot's restore attribute is set to all.

An AWS RDS snapshot is marked as INAPPLICABLE when:

... see more

Remediation​

Open File

Remediation​

Case A: Make a snapshot private (accessible only by a current AWS Account)​

From Console​
  • Log in to the AWS management console and navigate to the RDS dashboard at https://console.aws.amazon.com/rds/.
  • In the left navigation panel, click on Snapshots.
  • Select Manual Snapshots from the Filter dropdown menu to display only manual database snapshots.
  • Select the RDS snapshot that you want to make private.
  • Click Snapshot Actions button from the dashboard top menu and select Share Snapshot option.
  • On the Manage Snapshot Permissions page, select Private next to DB Snapshot Visibility to make the selected snapshot accessible only from the current AWS account. Click Save to apply the changes.
  • Repeat steps no. 5 – 7 to restrict public access to other RDS database snapshots created within the current region.
  • Change the AWS region from the navigation bar and repeat the audit process for other regions.
From Command Line​
  • Run modify-db-snapshot-attribute command (OSX/Linux/UNIX) using the snapshot name as --db-snapshot-identifier to remove the permissions for restoring database instances from the selected snapshot and make it private:

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [RDS.1] RDS snapshot should be private11
💼 Cloudaware Framework → 💼 Public and Anonymous Access69
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)3546
💼 FedRAMP High Security Controls → 💼 AC-4 Information Flow Enforcement (M)(H)23164
💼 FedRAMP High Security Controls → 💼 AC-4(21) Physical or Logical Separation of Information Flows (M)(H)1138
💼 FedRAMP High Security Controls → 💼 AC-6 Least Privilege (M)(H)81133
💼 FedRAMP High Security Controls → 💼 AC-21 Information Sharing (M)(H)2
💼 FedRAMP High Security Controls → 💼 SA-9(5) Processing, Storage, and Service Location (M)(H)1
💼 FedRAMP High Security Controls → 💼 SC-7 Boundary Protection (L)(M)(H)10632
💼 FedRAMP High Security Controls → 💼 SC-7(3) Access Points (M)(H)2
💼 FedRAMP High Security Controls → 💼 SC-7(4) External Telecommunications Services (M)(H)17
💼 FedRAMP High Security Controls → 💼 SC-7(20) Dynamic Isolation and Segregation (H)2
💼 FedRAMP High Security Controls → 💼 SC-7(21) Isolation of System Components (H)16
💼 FedRAMP Low Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)46
💼 FedRAMP Low Security Controls → 💼 SC-7 Boundary Protection (L)(M)(H)23
💼 FedRAMP Moderate Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)46
💼 FedRAMP Moderate Security Controls → 💼 AC-4 Information Flow Enforcement (M)(H)150
💼 FedRAMP Moderate Security Controls → 💼 AC-4(21) Physical or Logical Separation of Information Flows (M)(H)38
💼 FedRAMP Moderate Security Controls → 💼 AC-6 Least Privilege (M)(H)633
💼 FedRAMP Moderate Security Controls → 💼 AC-21 Information Sharing (M)(H)2
💼 FedRAMP Moderate Security Controls → 💼 SA-9(5) Processing, Storage, and Service Location (M)(H)1
💼 FedRAMP Moderate Security Controls → 💼 SC-7 Boundary Protection (L)(M)(H)728
💼 FedRAMP Moderate Security Controls → 💼 SC-7(3) Access Points (M)(H)2
💼 FedRAMP Moderate Security Controls → 💼 SC-7(4) External Telecommunications Services (M)(H)17
💼 GDPR → 💼 Art. 25 Data protection by design and by default1010
💼 GDPR → 💼 Art. 46 Transfers subject to appropriate safeguards22
💼 ISO/IEC 27001:2013 → 💼 A.9.4.1 Information access restriction1719
💼 NIST CSF v1.1 → 💼 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties1534
💼 NIST CSF v1.1 → 💼 PR.DS-5: Protections against data leaks are implemented4150
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events83
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events89
💼 NIST CSF v2.0 → 💼 ID.AM-03: Representations of the organization's authorized network communication and internal and external network data flows are maintained31
💼 NIST CSF v2.0 → 💼 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties57
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected81
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected68
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected66
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage40
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement15417
💼 NIST SP 800-53 Revision 5 → 💼 AC-3(7) Access Enforcement _ Role-based Access Control7
💼 NIST SP 800-53 Revision 5 → 💼 AC-4 Information Flow Enforcement325972
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(21) Information Flow Enforcement _ Physical or Logical Separation of Information Flows3338
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege102126
💼 NIST SP 800-53 Revision 5 → 💼 AC-21 Information Sharing22
💼 NIST SP 800-53 Revision 5 → 💼 SA-9(5) External System Services _ Processing, Storage, and Service Location11
💼 NIST SP 800-53 Revision 5 → 💼 SC-7 Boundary Protection29332
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(3) Boundary Protection _ Access Points2
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(4) Boundary Protection _ External Telecommunications Services17
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(9) Boundary Protection _ Restrict Threatening Outgoing Communications Traffic7
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(11) Boundary Protection _ Restrict Incoming Communications Traffic15
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(16) Boundary Protection _ Prevent Discovery of System Components16
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(20) Boundary Protection _ Dynamic Isolation and Segregation2
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(21) Boundary Protection _ Isolation of System Components16
💼 PCI DSS v3.2.1 → 💼 1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment, and specifically deny all other traffic.1014
💼 PCI DSS v3.2.1 → 💼 1.3 Prohibit direct public access between the Internet and any system component in the cardholder data environment.7710
💼 PCI DSS v3.2.1 → 💼 1.3.1 Implement a DMZ to limit inbound traffic to only system components that provide authorized publicly accessible services, protocols, and ports.57
💼 PCI DSS v3.2.1 → 💼 1.3.2 Limit inbound Internet traffic to IP addresses within the DMZ.7
💼 PCI DSS v3.2.1 → 💼 1.3.4 Do not allow unauthorized outbound traffic from the cardholder data environment to the Internet.4
💼 PCI DSS v3.2.1 → 💼 1.3.5 Permit only “established” connections into the network.7
💼 PCI DSS v3.2.1 → 💼 1.3.6 Place system components that store cardholder data in an internal network zone, segregated from the DMZ and other untrusted networks.3
💼 PCI DSS v3.2.1 → 💼 7.2.1 Coverage of all system components.5
💼 PCI DSS v4.0.1 → 💼 1.3.1 Inbound traffic to the CDE is restricted.14
💼 PCI DSS v4.0.1 → 💼 1.3.2 Outbound traffic from the CDE is restricted.14
💼 PCI DSS v4.0.1 → 💼 1.4.1 NSCs are implemented between trusted and untrusted networks.9
💼 PCI DSS v4.0.1 → 💼 1.4.2 Inbound traffic from untrusted networks to trusted networks is restricted.7
💼 PCI DSS v4.0.1 → 💼 1.4.4 System components that store cardholder data are not directly accessible from untrusted networks.3
💼 PCI DSS v4.0.1 → 💼 7.3.1 An access control system(s) is in place that restricts access based on a user's need to know and covers all system components.5
💼 PCI DSS v4.0 → 💼 1.3.1 Inbound traffic to the CDE is restricted.14
💼 PCI DSS v4.0 → 💼 1.3.2 Outbound traffic from the CDE is restricted.14
💼 PCI DSS v4.0 → 💼 1.4.1 NSCs are implemented between trusted and untrusted networks.9
💼 PCI DSS v4.0 → 💼 1.4.2 Inbound traffic from untrusted networks to trusted networks is restricted.7
💼 PCI DSS v4.0 → 💼 1.4.4 System components that store cardholder data are not directly accessible from untrusted networks.3
💼 PCI DSS v4.0 → 💼 7.3.1 An access control system(s) is in place that restricts access based on a user's need to know and covers all system components.5
💼 SOC 2 → 💼 CC6.1-6 Manages Points of Access56
💼 SOC 2 → 💼 CC6.6-1 Restricts Access1515
💼 UK Cyber Essentials → 💼 1.2 Prevent access to the administrative interface from the internet3336
💼 UK Cyber Essentials → 💼 2.1.5 Ensure users are authenticated before allowing them access to organizational data or services33