Skip to main content

MON-08: Correlate Monitoring Information

MON 9 — Critical Detect

Automated mechanisms exist to correlate both technical and non-technical information from across the enterprise by a Security Incident Event Manager (SIEM) or similar automated tool, to enhance organization-wide situational awareness.

Renumbered: Formerly MON-02.1 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, MON-08 was Protection of Event Logs. That control is now MON-12.

Control Question: Does the organization use automated mechanisms to correlate both technical and non-technical information from across the enterprise by a Security Incident Event Manager (SIEM) or similar automated tool, to enhance organization-wide situational awareness?

General (35)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC7.2 CC7.3
CIS CSC 8.1 3.14 8.12 13.6
CIS CSC 8.1 IG2 13.6
CIS CSC 8.1 IG3 3.14 8.12 13.6
CR CMM 2026 CR2.2.1
GovRAMP AU-06(03) SI-04(16)
GovRAMP Moderate AU-06(03) SI-04(16)
GovRAMP High AU-06(03) SI-04(16)
ISO 27002 2022 8.15
ISO 27017 2015 12.4.1
ISO 27018 2025 8.15
NIST 800-53 R4 AU-6(3) IR-4(4) SI-4(16)
NIST 800-53 R5.2 AU-06(03) AU-06(09) IR-04(04) SI-04(16)
NIST 800-53B R5 (moderate) (source) AU-06(03)
NIST 800-53B R5 (high) (source) AU-06(03) IR-04(04)
NIST 800-82 R3 AU-06(03) AU-06(09) IR-04(04) SI-04(16)
NIST 800-82 R3 MODERATE OT Overlay AU-06(03)
NIST 800-82 R3 HIGH OT Overlay AU-06(03) IR-04(04)
NIST 800-160 Vol2 R1 AU-06(03) AU-06(09) IR-04(04) SI-04(16)
NIST 800-161 R1 AU-6(9)
NIST 800-161 R1 Level 3 AU-6(9)
NIST 800-171 R2 (source) 3.3.5 3.14.7
NIST 800-171 R3 (source) 03.03.05.a 03.03.05.c
NIST 800-171A (source) 3.3.5[a] 3.3.5[b] 3.14.7[a] 3.14.7[b]
NIST 800-171A R3 (source) A.03.03.05.a A.03.03.05.c[02]
NIST 800-207 NIST Tenet 5 NIST Tenet 7
NIST CSF 2.0 (source) DE.AE-03 DE.AE-06
OWASP Top 10 2025 A09:2025
PCI DSS 4.0.1 (source) 10.4.1.1 12.10.5
PCI DSS 4.0.1 SAQ A-EP (source) 10.4.1.1
PCI DSS 4.0.1 SAQ C (source) 10.4.1.1
PCI DSS 4.0.1 SAQ D Merchant (source) 10.4.1.1 12.10.5
PCI DSS 4.0.1 SAQ D Service Provider (source) 10.4.1.1 12.10.5
SCF DPMP 2026 7.13
TISAX ISA 6.0.3 5.2.4
US (11)
Framework Mapping Values
USA Federal CMS MARS-E 2.0 AU-6(3)
USA Federal CISA CPG 2022 2.T
USA Federal DHS CISA TIC 3.0 3.UNI.SAWAR 3.UNL.CMREP
USA Federal C2M2 2.1 SITUATION-1e SITUATION-3e RESPONSE-1d
USA Federal CMMC 2.0 Level 2 AUL2.-3.3.5 SIL2.-3.14.7
USA Federal DoD Zero Trust Execution Roadmap v1.1 3.5.1 3.5.2 4.4.3 4.4.4 4.4.5 4.4.6 7.2.2
USA Federal CJIS Security Policy 6.0 AU-6(3)
USA Federal FFIEC ITEH 2016 II.C.22
USA Federal FedRAMP R5 (moderate) AU-06(03) SI-04(16)
USA Federal FedRAMP R5 (high) AU-06(03) IR-04(04) SI-04(16)
USA Federal IRS 1075 2021 AU-6(CE-3) AU-6(CE-9)
EMEA (5)
Framework Mapping Values
EMEA Germany C5 2026 OPS-13.02B.1 OPS-13.02B.2 OPS-25.04B SIM-03.05B
EMEA Spain CCN-STIC 825 op.exp.8
EMEA EU EBA GL/2019/04 3.4.5.38(a) 3.4.5.38(b) 3.4.5.38(c) 3.4.5.39 3.4.5.40
EMEA Saudi Arabia CSCC-1 2019 2-11-1-3 2-11-1-4
EMEA Saudi Arabia SACS-002 2022 VII.B.TPC-81
APAC (7)
Americas (2)
Framework Mapping Values
Americas Canada ITSP-10-171 2025 03.03.05.A 03.03.05.C
Americas Canada OSFI B-13 2022 3.3.1

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. ▪ A log aggregator, or similar automated tool, provides an event log report generation capability to aid in detecting and assessing anomalous activities on business-critical TAASD. ▪ IT and/or cybersecurity personnel configure alerts for critical or sensitive data that is stored, transmitted and processed on assets. ▪ Logs of vulnerability scanning activities and associated administrator accounts are reviewed to ensure that those activities are limited to the timeframes of legitimate scans.

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 automatically correlate both technical and non-technical information from across the enterprise by a Security Incident Event Manager (SIEM) or similar automated tool, to enhance organization-wide situational awareness.

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

  1. MON-08_A01 authorized use of the system is defined.
  2. MON-08_A02 unauthorized use of the system is identified.
  3. MON-08_A03 incident information and individual incident responses are correlated to achieve an organization-wide perspective on incident awareness and response.
  4. MON-08_A04 audit records across different repositories are correlated to gain organization-wide situational awareness.
  5. MON-08_A05 audit record review, analysis and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious or unusual activity are defined.
  6. MON-08_A06 defined audit record review, analysis and reporting processes are correlated.

Evidence Requirements

E-MON-05 Centralized Event Log Collection

Documented evidence of security-relevant activities being logged and included as part of the centralized event log collection and review/analysis process.

Event Log Monitoring
E-MON-07 Situational Awareness

Documented evidence of the organization leveraging knowledge of event log generation to gain situational awareness of cross-domain activities (e.g., technology issues, security events, policy violations, service provider activities, remote workforce activities, physical security events, etc.).

Event Log Monitoring

Technology Recommendations

Micro/Small

  • Managed Security Services Provider (MSSP)

Small

  • Security Incident Event Manager (SIEM)
  • Managed Security Services Provider (MSSP)

Medium

  • Security Incident Event Manager (SIEM)
  • Managed Security Services Provider (MSSP)

Large

  • Security Incident Event Manager (SIEM)
  • Managed Security Services Provider (MSSP)

Enterprise

  • Security Incident Event Manager (SIEM)
  • Managed Security Services Provider (MSSP)

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.