AWS Well-Architected Security Pillar
Data Protection

AWS Well-Architected Security Pillar SEC07-BP04: Define scalable data lifecycle management

Define data lifecycle management that scales, covering how data is handled at ingestion, how sensitivity is reduced through masking or tokenisation, retention periods, provenance tracking and destruction.

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

What else in your programme already covers this

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

ISO 27701:2019 · 5 controls

  • 6.11.3 Test data
  • 6.8.2 Equipment
  • 7.4.5 PII de-identification and deletion at the end of processing
  • 7.4.7 Retention
  • 8.4.2 Return, transfer or disposal of PII

NIST SP 800-161 Rev 1 · 5 controls

SOC 2 · 5 controls

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-C1.2 C1.2 Disposing of confidential information
  • SOC2-CC6.5 CC6.5 Protecting data on assets until disposal
  • SOC2-P4.2 P4.2 Retaining personal information
  • SOC2-P4.3 P4.3 Securely disposing of personal information

CIS Controls v8 · 4 controls

  • CIS-3.1 Establish and Maintain a Data Management Process
  • CIS-3.4 Enforce Data Retention
  • CIS-3.5 Securely Dispose of Data
  • CIS-3.8 Document Data Flows

ISO 27002:2022 · 4 controls

  • 5.12 Classification of information
  • 8.10 Information deletion
  • 8.11 Data masking
  • 8.33 Test information

C5 (Germany) · 3 controls

  • C5-AM-04 Decommissioning of Hardware
  • C5-PI-02 Contractual agreements for the provision of data
  • C5-PI-03 Secure deletion of data

ISO 27001:2022 · 3 controls

  • 5.33 Protection of records
  • 8.10 Information deletion
  • 8.11 Data masking
  • 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
  • AM-3 Ensure security of asset lifecycle management
  • ASBv3-LT-6 Configure log storage retention

FedRAMP High · 2 controls

  • MP-6 Media Sanitization
  • SI-12 Information Management and Retention

FedRAMP Moderate · 2 controls

  • MP-6 Media Sanitization
  • SI-12 Information Management and Retention
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.DS-10 The confidentiality, integrity, and availability of data-in-use are protected

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

ISO/IEC 42001:2023 · 1 control

  • A.7.2 Data for development and enhancement of AI system

PCI DSS 4.0 · 1 control

  • 3.2.1 3.2.1 Data retention and disposal minimise stored account data

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 SEC07-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 52 it maps to, and the evidence behind each claim, over MCP and REST.