MON-01.2: Automated Tools for Real-Time Analysis
Mechanisms exist to utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support near real-time analysis and incident escalation.
Control Question: Does the organization utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support near real-time analysis and incident escalation?
General (27)
| Framework | Mapping Values |
|---|---|
| AICPA TSC 2017:2022 (used for SOC 2) (source) | CC7.2 CC7.2-POF1 CC7.2-POF3 |
| COBIT 2019 | DSS06.05 |
| CSA CCM 4 | LOG-03 |
| CSA IoT SCF 2 | MON-03 OPA-04 |
| GovRAMP Moderate | SI-04(02) |
| GovRAMP High | SI-04(02) |
| ISO 27002 2022 | 8.16 |
| NIST AI 600-1 | MG-3.2-006 |
| NIST 800-53 R4 | SI-4(2) |
| NIST 800-53 R4 (moderate) | SI-4(2) |
| NIST 800-53 R4 (high) | SI-4(2) |
| NIST 800-53 R5 (source) | SI-4(2) SC-48 |
| NIST 800-53B R5 (moderate) (source) | SI-4(2) |
| NIST 800-53B R5 (high) (source) | SI-4(2) |
| NIST 800-53 R5 (NOC) (source) | SC-48 |
| NIST 800-82 R3 MODERATE OT Overlay | SI-4(2) |
| NIST 800-82 R3 HIGH OT Overlay | SI-4(2) |
| NIST 800-207 | NIST Tenet 5 NIST Tenet 7 |
| OWASP Top 10 2021 | A01:2021 A07:2021 A09:2021 |
| PCI DSS 4.0.1 (source) | 10.4 10.4.1 10.4.1.1 |
| PCI DSS 4.0.1 SAQ A-EP (source) | 10.4.1 10.4.1.1 |
| PCI DSS 4.0.1 SAQ C (source) | 10.4.1 10.4.1.1 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 10.4.1 10.4.1.1 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 10.4.1 10.4.1.1 |
| SCF CORE Mergers, Acquisitions & Divestitures (MA&D) | MON-01.2 |
| SCF CORE ESP Level 2 Critical Infrastructure | MON-01.2 |
| SCF CORE ESP Level 3 Advanced Threats | MON-01.2 |
US (17)
| Framework | Mapping Values |
|---|---|
| US CJIS Security Policy 5.9.3 (source) | 5.4.1 SI-4(2) |
| US CMS MARS-E 2.0 | SI-4(2) |
| US DoD Zero Trust Execution Roadmap | 2.7.2 2.7.3 5.2.2 7.2 7.2.1 |
| US DoD Zero Trust Reference Architecture 2.0 | 6.2 |
| US DHS CISA TIC 3.0 | 3.UNI.CLMAN |
| US DHS ZTCF | APP-02 SEC-01 |
| US FedRAMP R4 | SI-4(2) |
| US FedRAMP R4 (moderate) | SI-4(2) |
| US FedRAMP R4 (high) | SI-4(2) |
| US FedRAMP R5 (source) | SI-4(2) |
| US FedRAMP R5 (moderate) (source) | SI-4(2) |
| US FedRAMP R5 (high) (source) | SI-4(2) |
| US IRS 1075 | SI-4(2) |
| US SSA EIESR 8.0 | 5.6 |
| US - CA CCPA 2025 | 7123(c)(8)(A) |
| US - NY DFS 23 NYCRR500 2023 Amd 2 | 500.14(b)(2) |
| US - TX TX-RAMP Level 2 | SI-4(2) |
EMEA (9)
| Framework | Mapping Values |
|---|---|
| EMEA EU EBA GL/2019/04 | 3.4.5(39) 3.4.5(40) |
| EMEA EU NIS2 Annex | 3.2.2 |
| EMEA Germany C5 2020 | OPS-13 |
| EMEA Israel CDMO 1.0 | 11.11 12.31 |
| EMEA Saudi Arabia CSCC-1 2019 | 2-11-1-3 2-11-1-4 |
| EMEA Saudi Arabia IoT CGIoT-1 2024 | 2-11-1 |
| EMEA Saudi Arabia ECC-1 2018 | 2-12-3-3 5-1-3-3 |
| EMEA Saudi Arabia SAMA CSF 1.0 | 3.3.14 |
| EMEA UK DEFSTAN 05-138 | 3102 |
APAC (2)
| Framework | Mapping Values |
|---|---|
| APAC Japan ISMAP | 12.4.5.P |
| APAC New Zealand HISF 2022 | HMS19 |
Americas (2)
| Framework | Mapping Values |
|---|---|
| Americas Canada CSAG | 3.4 |
| Americas Canada OSFI B-13 | 3.3.1 |
Capability Maturity Model
Level 0 — Not Performed
There is no evidence of a capability to utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support near real-time analysis and incident escalation.
Level 1 — Performed Informally
C|P-CMM1 is N/A, since a structured process is required to utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support near real-time analysis and incident escalation.
Level 2 — Planned & Tracked
Continuous Monitoring (MON) efforts are requirements-driven and governed at a local/regional level, but are not consistent across the organization. CMM Level 2 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Identify cybersecurity and data protection controls that are appropriate to address applicable statutory, regulatory and contractual requirements for situational awareness management. o Configure alerts for critical or sensitive data that is stored, transmitted and processed on assets. o Use a structured process to review and analyze logs.
- Situational awareness management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
- Secure baseline configurations generate logs that contain sufficient information to establish necessary details of activity and allow for forensics analysis.
- IT/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 systems.
Level 3 — Well Defined
Continuous Monitoring (MON) efforts are standardized across the organization and centrally managed, where technically feasible, to ensure consistency. CMM Level 3 control maturity would reasonably expect all, or at least most, the following criteria to exist: o Governs asset management that ensures compliance with requirements for asset management. o Leverages a Configuration Management Database (CMDB), or similar tool, as the authoritative source of IT assets. o Centrally collects logs and is protected according to the manufacturer’s security guidelines to protect the integrity of the event logs with cryptographic mechanisms. o Monitors the organization for Indicators of Compromise (IoC) and provides 24x7x365 near real-time alerting capability. o Is configured to alert incident response personnel of detected suspicious events such that incident responders can look to terminate suspicious events.
- An IT Asset Management (ITAM) function, or similar function:
- A Security Incident Event Manager (SIEM), or similar automated tool:
- Both inbound and outbound network traffic is monitored for unauthorized activities to identify prohibited activities and assist incident handlers with identifying potentially compromised systems.
- A Security Operations Center (SOC), or similar function, enables cybersecurity operations covering preparation, detection and analysis, containment, eradication and recovery.
Level 4 — Quantitatively Controlled
See C|P-CMM3. There are no defined C|P-CMM4 criteria, since it is reasonable to assume a quantitatively-controlled process is not necessary to utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support near real-time analysis and incident escalation.
Level 5 — Continuously Improving
See C|P-CMM4. There are no defined C|P-CMM5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to utilize a Security Incident Event Manager (SIEM), or similar automated tool, to support near real-time analysis and incident escalation.
Assessment Objectives
- MON-01.2_A01 automated tools and mechanisms are employed to support a near real-time analysis of events.
Evidence Requirements
- E-MON-01 Event Log Review & Analysis
-
Documented evidence of security event log review and analysis (e.g., system monitoring records).
Event Log Monitoring - 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
Technology Recommendations
Micro/Small
- Managed Security Services Provider (MSSP)
Small
- Managed Security Services Provider (MSSP)
Medium
- Security Incident Event Management (SIEM)
- Security Orchestration, Automation & Response (SOAR)
- Extended Detection and Response (XDR)
- Managed Security Services Provider (MSSP)
Large
- Security Incident Event Management (SIEM)
- Security Orchestration, Automation & Response (SOAR)
- Extended Detection and Response (XDR)
- Managed Security Services Provider (MSSP)
Enterprise
- Security Incident Event Management (SIEM)
- Security Orchestration, Automation & Response (SOAR)
- Extended Detection and Response (XDR)
- Managed Security Services Provider (MSSP)