Skip to main content

DCH-27: Media & Data Retention

DCH 8 — High Protect

Mechanisms exist to retain media and data in accordance with applicable statutory, regulatory and contractual obligations.

Renumbered: Formerly DCH-18 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, DCH-27 was Data Rights Management (DRM). That control is now DCH-39.

Control Question: Does the organization retain media and data in accordance with applicable statutory, regulatory and contractual obligations?

General (52)
Framework Mapping Values
AICPA Privacy Management Framework (PMF) U4.2-POF1 U4.2-POF2
AICPA TSC 2017:2022 (used for SOC 2) (source) C1.1-POF3 PI1.5
CIS CSC 8.1 3.1 3.4
CIS CSC 8.1 IG1 3.1 3.4
CIS CSC 8.1 IG2 3.1 3.4
CIS CSC 8.1 IG3 3.1 3.4
COBIT 2019 APO14.09
CSA CCM 4.1.0 DSP-16
GovRAMP MP-07 SI-12
GovRAMP Low SI-12
GovRAMP Low+ SI-12
GovRAMP Moderate SI-12
GovRAMP High MP-07 SI-12
IEC 62443-2-1 2024 DATA 1.4
ISO 27002 2022 5.33 8.10
ISO 27017 2015 18.1.3
ISO 27018 2025 5.33 8.10
MITRE ATT&CK 16 T1003 T1003.003 T1020.001 T1040 T1070 T1070.001 T1070.002 T1070.008 T1114 T1114.001 T1114.002 T1114.003 T1119 T1213.004 T1530 T1548 T1548.004 T1550.001 T1552 T1552.004 T1557 T1557.002 T1557.004 T1558 T1558.002 T1558.003 T1558.004 T1558.005 T1565 T1565.001 T1565.002 T1602 T1602.001 T1602.002
MPA Content Security Program 5.3.1 PS-1.3 PS-3.0 TS-1.0
NAIC Insurance Data Security Model Law (MDL-668) 4.B(4)
NIST AI 600-1 GV-1.5-003
NIST 800-53 R4 MP-7 SI-12
NIST 800-53 R5.2 MP-07 SI-12
NIST 800-53B R5 (low) (source) MP-07 SI-12
NIST 800-53B R5 (moderate) (source) MP-07 SI-12
NIST 800-53B R5 (high) (source) MP-07 SI-12
NIST 800-53B R5 (privacy) (source) SI-12
NIST SP 800-66 R2 164.316(b)
NIST 800-82 R3 MP-07 SI-12
NIST 800-82 R3 LOW OT Overlay MP-07 SI-12
NIST 800-82 R3 MODERATE OT Overlay MP-07 SI-12
NIST 800-82 R3 HIGH OT Overlay MP-07 SI-12
NIST 800-161 R1 SI-12
NIST 800-161 R1 C-SCRM Baseline SI-12
NIST 800-161 R1 Level 3 SI-12
NIST 800-171 R3 (source) 03.01.20.c.02 03.10.07.b 03.14.08
NIST 800-171A R3 (source) A.03.01.20.c.02 A.03.10.07.b A.03.14.08[01] A.03.14.08[02] A.03.14.08[03] A.03.14.08[04]
NIST 800-172 R3 03.04.06E 03.10.01E
NIST 800-172A R3 DS-A.03.04.06E A.03.10.01E.ODP[01]
NIST Privacy Framework 1.0 CT.DM-P3 CT.DM-P4
PCI DSS 4.0.1 (source) 3.2 3.2.1 9.4.6 9.4.7 10.5 10.5.1 11.4.1
PCI DSS 4.0.1 SAQ A (source) 3.2.1 9.4.6
PCI DSS 4.0.1 SAQ A-EP (source) 3.2.1 9.4.6 10.5.1 11.4.1
PCI DSS 4.0.1 SAQ B (source) 9.4.6
PCI DSS 4.0.1 SAQ B-IP (source) 9.4.6
PCI DSS 4.0.1 SAQ C (source) 9.4.6 10.5.1
PCI DSS 4.0.1 SAQ C-VT (source) 9.4.6
PCI DSS 4.0.1 SAQ D Merchant (source) 3.2.1 9.4.6 9.4.7 10.5.1 11.4.1
PCI DSS 4.0.1 SAQ D Service Provider (source) 3.2.1 9.4.6 9.4.7 10.5.1 11.4.1
PCI DSS 4.0.1 SAQ P2PE (source) 3.2.1 9.4.6
SCF DPMP 2026 5.4
SWIFT CSF 2025 6.4
US (27)
EMEA (7)
Framework Mapping Values
EMEA Germany C5 2026 OPS-11.01B OPS-11.01B.3 OPS-19.01B.10
EMEA EU AI Act Article 16(d) Article 18.1 Article 18.1(a) Article 18.1(b) Article 18.1(c) Article 18.1(d) Article 18.1(e) Article 18.3
EMEA EU Cyber Resiliency Act 2024 Article 13(13) Article 19(6) Article 23(2)
EMEA EU NIS2 Annex 2024 1.1.1(h) 4.2.2(f)
EMEA LUX CCSF 22/806 2022 53
EMEA Saudi Arabia CSCC-1 2019 2-6-1-4 2-11-2
EMEA Saudi Arabia SACS-002 2022 VII.A.TPC-19
APAC (6)
Framework Mapping Values
APAC Australia ISM June 2026 ISM-1510
APAC India DPDPA 2023 8(7)(a) 8(8)
APAC India RBI PPI 2025 6.3 10.1.d 10.3.b
APAC India SEBI CSCRF 2024 PR.AA.S13
APAC Japan ISMAP 4.4.7.4 4.6.3.4 12.3.1.15 12.3.1.19.P 13.2.1.7 18.1.3 18.1.3.1 18.1.3.2 18.1.3.3 18.1.3.4 18.1.3.5 18.1.3.6 18.1.3.7 18.1.3.8 18.1.3.9 18.1.3.10 18.1.3.11 18.1.3.12 18.1.3.13.PB
APAC Malaysia RMiT 2025 A10-A5(c)
Americas (2)
Framework Mapping Values
Americas Bermuda BMACCC 2020 5.5
Americas Canada ITSP-10-171 2025 03.01.20.C.02 03.10.07.B 03.14.08

Capability Maturity Model

Level 0 — Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 — Performed Informally

Data Classification & Handling (DCH) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include: ▪ Policies, standards & procedures associated with DCH domain capabilities provide limited coverage due to the depth and breadth of the existing documentation. ▪ Data management-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices. ▪ Data protection controls are primarily administrative in nature (e.g., policies & standards) to classify, protect and dispose of systems and data, including storage media. ▪ A manual data retention process exists. ▪ Media is securely stored until it is destroyed or sanitized using approved equipment, techniques and procedures.

Level 2 — Planned & Tracked

Data Classification & Handling (DCH) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with DCH domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with DCH domain capabilities are documented and maintained by process owners. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with DCH domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Data classification and handling-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Data classification and handling management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel. ▪ A formalized data classification scheme exists to identify categories of data, based on protection requirements from applicable laws, regulations and/or contractual obligations. ▪ The data retention process is manual and IT and/or cybersecurity personnel work with business stakeholders and process owners to manage the process. ▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to dispose of, destroy, erase, and/or anonymize sensitive/regulated data.

Level 3 — Well Defined

Data Classification & Handling (DCH) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Policies and standards associated with DCH domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Standardized Operating Procedures (SOP) associated with DCH domain capabilities are well-documented and kept current by process owners. ▪ A Governance, Risk & Compliance (GRC) team, or similar function, is appropriately staffed and supported to implement and maintain DCH domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of data classification and handling operations (e.g., GRC platform). ▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with DCH domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls). ▪ An implemented and operational capability exists to retain media and data in accordance with applicable statutory, regulatory and contractual obligations.

Level 4 — Quantitatively Controlled

Data Classification & Handling (DCH) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist: ▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational. ▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs). ▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs). ▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties. ▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review). ▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes. ▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 — Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions: ▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control. ▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies. ▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.

Assessment Objectives

  1. DCH-27_A01 the frequency with which to conduct reviews of persistent organizational storage locations is defined.
  2. DCH-27_A02 persistent organizational storage locations are identified.
  3. DCH-27_A03 reviews of persistent organizational storage locations are conducted per an organization-defined frequency to identify sensitive / regulated data that is no longer needed.
  4. DCH-27_A04 sensitive / regulated data that is no longer needed is removed.
  5. DCH-27_A05 sensitive / regulated data within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.
  6. DCH-27_A06 sensitive / regulated data within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.
  7. DCH-27_A07 sensitive / regulated data output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.
  8. DCH-27_A08 sensitive / regulated data output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.
  9. DCH-27_A09 CUI within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.
  10. DCH-27_A10 CUI within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.
  11. DCH-27_A11 CUI output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.
  12. DCH-27_A12 CUI output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.

Evidence Requirements

E-AST-11 Data Retention Program

Documented evidence of a formal data retention program that governs the retention and destruction of data types.

Asset Management

Technology Recommendations

Micro/Small

  • Data retention program
  • Data classification program

Small

  • Data retention program
  • Data classification program

Medium

  • Data retention program
  • Data classification program

Large

  • Data retention program
  • Data classification program
  • Data governance program

Enterprise

  • Data retention program
  • Data classification program
  • Data governance program

The Secure Controls Framework (SCF) is maintained by SCF Council. Use of SCF content is subject to the SCF Terms & Conditions.

Manage this control in SCF Connect

Track implementation status, collect evidence, and map controls to your compliance frameworks automatically.