AWS Well-Architected Security Pillar
Data Protection

AWS Well-Architected Security Pillar SEC08-BP04: Enforce access control

Layer IAM, resource policies, KMS grants, S3 Access Points and VPC endpoint policies to enforce least privilege access to data and prevent exfiltration.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 53 controls across 21 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CMMC 2.0 · 7 controls

C5 (Germany) · 4 controls

  • C5-IDM-07 Access to cloud customer data
  • C5-OPS-12 Logging and Monitoring - Access, Storage and Deletion
  • C5-OPS-24 Separation of Datasets in the Cloud Infrastructure
  • C5-PSS-09 Authorisation Mechanisms

NIST SP 800-171 Rev 3 · 4 controls

PCI DSS 4.0 · 4 controls

  • 10.3.1 10.3.1 Audit log read access limited to job need
  • 3.6.1.3 3.6.1.3 Cleartext key component access limited to minimum custodians
  • 7.2.6 7.2.6 Query access to stored cardholder data restricted
  • 7.3.1 7.3.1 Need-to-know access control system covers all components
  • ASBv3-DP-8 Ensure security of key and certificate repository
  • DP-2 Monitor anomalies and threats targeting sensitive data
  • NS-2 Secure cloud services with network controls

NIST SP 800-161 Rev 1 · 3 controls

  • AUCDR-IS-3 Securely manage information assets over their lifecycle
  • AUCDR-PS-12 Privacy Safeguard 12 - Security of CDR data and destruction or de-identification of redundant CDR data

CIS Controls v8 · 2 controls

  • CIS-3.13 Deploy a Data Loss Prevention Solution
  • CIS-3.3 Configure Data Access Control Lists

FedRAMP High · 2 controls

  • AC-3 Access Enforcement
  • AC-6 Least Privilege

FedRAMP Moderate · 2 controls

  • AC-3 Access Enforcement
  • AC-6 Least Privilege

HIPAA Security Rule · 2 controls

ISO 27001:2022 · 2 controls

  • 8.12 Data leakage prevention
  • 8.3 Information access restriction

ISO 27002:2022 · 2 controls

  • 8.12 Data leakage prevention
  • 8.3 Information access restriction
  • NIST-CSF-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 duties
  • NIST-CSF-PR.DS-01 The confidentiality, integrity, and availability of data-at-rest are protected

NIST SP 800-53 Rev 5 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.7 CC6.7 Restricting and protecting information in transmission, movement and removal
  • E8-BACKUP-ML1 Regular Backups (ML1)
  • ANSSI-HYG-09 Assign the Correct Rights on Sensitive Resources
  • ASD37-27 Outbound data loss prevention (Very Good)

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Data Protection

You are reading one control. How much of AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC08-BP04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 53 it maps to, and the evidence behind each claim, over MCP and REST.