Skip to main content

DCH-24: Publicly Accessible Content

DCH 10 — Critical Protect

Mechanisms exist to control publicly-accessible content.

Renumbered: Formerly DCH-15 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, DCH-24 was Information Location. That control is now DCH-29.

Control Question: Does the organization control publicly-accessible content?

General (24)
US (13)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 AC-22 AC-22.a AC-22.b AC-22.c AC-22.d
USA Federal CMMC 2.0 Level 1 AC.L1-B.1.IV
USA Federal CMMC 2.0 Level 1 AOs AC.L1-B.1.IV[a] AC.L1-B.1.IV[b] AC.L1-B.1.IV[c] AC.L1-B.1.IV[d] AC.L1-B.1.IV[e]
USA Federal CMMC 2.0 Level 2 ACL2.-3.1.22
USA Federal FAR 52.204-21 52.204-21(b)(1)(iv)
USA Federal CJIS Security Policy 6.0 AC-22
USA Federal FedRAMP R5 (low) AC-22
USA Federal FedRAMP R5 (moderate) AC-22
USA Federal FedRAMP R5 (high) AC-22
USA Federal FedRAMP R5 (LI-SaaS) AC-22
USA Federal IRS 1075 2021 AC-22
USA Texas DIR SCSC 2.2 2025 AC-22
USA Texas TX-RAMP Level 2 AC-22
EMEA (4)
APAC (1)
Framework Mapping Values
APAC Australia CCM 2026 GOV-10
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.01.22.A 03.01.22.B

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.

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.

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 control publicly-accessible content.

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-24_A01 individuals authorized to post or process information on publicly accessible systems are identified.
  2. DCH-24_A02 procedures to ensure sensitive / regulated data is not posted or processed on publicly accessible systems are identified.
  3. DCH-24_A03 the proposed content of information is reviewed prior to posting onto the publicly accessible system to ensure that non-public information is not included.
  4. DCH-24_A04 the content on publicly accessible systems is reviewed per an organization-defined frequency for sensitive / regulated data.
  5. DCH-24_A05 mechanisms are in place to remove and address improper posting of sensitive / regulated data.
  6. DCH-24_A06 the frequency at which to review the content on the publicly accessible system for non-public information is defined.
  7. DCH-24_A07 authorized individuals are trained to ensure that publicly accessible information does not contain non-public information.
  8. DCH-24_A08 authorized individuals are trained to ensure that publicly accessible information does not contain CUI.
  9. DCH-24_A09 CUI is removed from publicly accessible systems, if discovered.
  10. DCH-24_A10 content on publicly accessible systems is reviewed to ensure that it does not include CUI.
  11. DCH-24_A11 the content on publicly accessible systems is reviewed for CUI.
  12. DCH-24_A12 a review process is in place prior to posting of any content to publicly accessible systems.
  13. DCH-24_A13 content on publicly accessible systems is reviewed to ensure that it does not include sensitive/regulated data.

Evidence Requirements

E-DCH-11 Authorized Users To Post Publicly Accessible Content

Documented evidence of list of users authorized to post publicly accessible content on organizational systems.

Data Protection
E-DCH-12 Publicly Accessible Information Reviews

Documented evidence of reviews for publicly accessible sensitive / regulated data.

Data Protection

Technology Recommendations

Micro/Small

  • Data classification policy (public/internal/confidential)

Small

  • Data classification policy
  • Data handling procedures

Medium

  • Data classification program
  • DLP tools
  • Data handling standards

Large

  • Enterprise DLP solution (e.g., Microsoft Purview, Symantec DLP)
  • Data classification tool

Enterprise

  • Enterprise data governance platform (e.g., Collibra)
  • DLP with automated classification
  • Data lifecycle management

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.