MON-19: Monitoring For Information Disclosure
Mechanisms exist to monitor for evidence of unauthorized exfiltration or disclosure of non-public information.
Renumbered: Formerly MON-11 in SCF 2025.4.
Control Question: Does the organization monitor for evidence of unauthorized exfiltration or disclosure of non-public information?
General (12)
| Framework | Mapping Values |
|---|---|
| ISO 27002 2022 | 5.7 |
| ISO 27018 2025 | 5.7 |
| NIST 800-53 R4 | AU-13 |
| NIST 800-53 R5.2 | AU-13 |
| NIST 800-82 R3 | AU-13 |
| NIST 800-160 Vol2 R1 | AU-13 |
| NIST 800-161 R1 | AU-13 |
| NIST 800-161 R1 Flow Down | AU-13 |
| NIST 800-161 R1 Level 2 | AU-13 |
| NIST 800-161 R1 Level 3 | AU-13 |
| NIST 800-171 R3 (source) | 03.01.22.b |
| NIST 800-171A R3 (source) | A.03.01.22.b[01] |
US (1)
| Framework | Mapping Values |
|---|---|
| USA Federal FFIEC ITEH 2016 | III.B |
EMEA (3)
| Framework | Mapping Values |
|---|---|
| EMEA Spain CCN-STIC 825 | op.mon.3 |
| EMEA EU DORA RTS 2024 | Article 23.5(b) Article 34.1(i) |
| EMEA LUX CCSF 20/750 2020 | 3.4.5-39 |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC Malaysia RMiT 2025 | A5-B5(b) A10-B14(c)(i) |
| APAC New Zealand HISF MLHSP 2023 | HHSP63 HML69 |
| APAC New Zealand HISF Suppliers 2023 | HSUP55 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 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
SCR-CMM Level 1 criteria definitions are not available for this control: ▪ A reasonable person would conclude this control requires a structured process. ▪ At this level of maturity, the "ad hoc" nature of performing a capability informally would indicate the intent of the control is not met due to a lack of consistency and formality.
Level 2 — Planned & Tracked
Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity. ▪ Standardized Operating Procedures (SOP) associated with MON 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 MON domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD). ▪ Continuous monitoring-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines). ▪ Continuous monitoring may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
Level 3 — Well Defined
Continuous Monitoring (MON) 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 MON domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function. ▪ Cybersecurity personnel use a structured process via Standardized Operating Procedures (SOP) to review and analyze logs. ▪ A Security Operations Center (SOC) team, or similar function, is appropriately staffed and supported to implement and maintain MON domain capabilities. ▪ Technology is leveraged to enhance the efficiency and accuracy of continuous monitoring operations (e.g., Security Incident Event Manager (SIEM)). ▪ 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 MON 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). ▪ Secure Baseline Configurations (SBC) enforce security event logging to contain sufficient information to establish necessary details of activity and allow for forensics analysis. ▪ An implemented and operational capability exists to monitor for evidence of unauthorized exfiltration or disclosure of non-public information.
Level 4 — Quantitatively Controlled
Utilize SCR-CMM Level 3 criteria definitions: ▪ There are no defined Level 4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to operationalize this control. ▪ While it may be possible to develop “metrics-driven” capabilities for this control, the criteria would be organization-specific to define.
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
- MON-19_A01 open-source information and/or information sites to be monitored for evidence of unauthorized disclosure of organizational information is/are defined.
- MON-19_A02 the frequency with which open-source information and/or information sites are monitored for evidence of unauthorized disclosure of organizational information is defined.
- MON-19_A03 personnel or roles to be notified if an information disclosure is discovered is/are defined.
- MON-19_A04 additional actions to be taken if an information disclosure is discovered are defined.
- MON-19_A05 personnel or roles are notified if an information disclosure is discovered.
- MON-19_A06 additional actions are taken if an information disclosure is discovered.
Evidence Requirements
- E-DCH-16 Data Loss Prevention (DLP) Configuration
-
Documented evidence of Data Loss Prevention (DLP) and exfiltration prevention configurations.
Data Protection
Technology Recommendations
Micro/Small
- Content filtering
- Keyword alerting (e.g., Google Alerts)
- Review of social media outlets
- HaveIBeenPwned monitoring (https://haveibeenpwned.com)
Small
- Content filtering
- Keyword alerting (e.g., Google Alerts)
- Review of social media outlets
- HaveIBeenPwned monitoring (https://haveibeenpwned.com)
- Dark web monitoring (e.g., SpyCloud, HaveIBeenPwned Pro)
Medium
- Content filtering
- Keyword alerting (e.g., Google Alerts)
- Dark web monitoring (e.g., SpyCloud, Recorded Future, Digital Shadows)
- Data Loss Prevention (DLP) solution
Large
- Data Loss Prevention (DLP) solution (e.g., Microsoft Purview DLP, Forcepoint DLP)
- Dark web monitoring platform (e.g., Recorded Future, Digital Shadows, SpyCloud)
- Brand and digital footprint monitoring
Enterprise
- Enterprise DLP solution (e.g., Symantec DLP, Forcepoint DLP, Microsoft Purview DLP)
- Dedicated threat intelligence platform with dark web monitoring
- Digital risk protection (DRP) service (e.g., ZeroFox, Recorded Future)
- Automated exfiltration detection via SIEM/UEBA