Skip to main content

MON-01.12: Automated Alerts

MON 5 — Medium Detect

Mechanisms exist to automatically alert incident response personnel to inappropriate or anomalous activities that have potential security incident implications.

Control Question: Does the organization automatically alert incident response personnel to inappropriate or anomalous activities that have potential security incident implications?

General (14)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) CC7.2-POF2
CSA CCM 4 LOG-03
CSA IoT SCF 2 MON-03
NIST 800-53 R4 SI-4(12)
NIST 800-53 R5 (source) SI-4(12)
NIST 800-53B R5 (high) (source) SI-4(12)
NIST 800-82 R3 HIGH OT Overlay SI-4(12)
NIST 800-171 R3 (source) 03.03.04.a 03.03.05.b
NIST 800-171A R3 (source) A.03.03.05.b
NIST CSF 2.0 (source) DE.AE DE.AE-06
SCF CORE Mergers, Acquisitions & Divestitures (MA&D) MON-01.12
SCF CORE ESP Level 1 Foundational MON-01.12
SCF CORE ESP Level 2 Critical Infrastructure MON-01.12
SCF CORE ESP Level 3 Advanced Threats MON-01.12
US (4)
Framework Mapping Values
US CISA CPG 2022 2.T
US DHS ZTCF APP-02 SEC-01
US FedRAMP R5 (source) SI-4(12)
US FedRAMP R5 (high) (source) SI-4(12)
EMEA (1)
Framework Mapping Values
EMEA Saudi Arabia ECC-1 2018 2-12-3-1
APAC (2)
Framework Mapping Values
APAC New Zealand HISF 2022 HHSP69 HML68 HSUP60
APAC New Zealand HISF Suppliers 2023 HSUP60
Americas (1)
Framework Mapping Values
Americas Canada ITSP-10-171 03.03.04.A 03.03.05.B

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to automatically alert incident response personnel to inappropriate or anomalous activities that have potential security incident implications.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to automatically alert incident response personnel to inappropriate or anomalous activities that have potential security incident implications.

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.
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 automatically alert incident response personnel to inappropriate or anomalous activities that have potential security incident implications.

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 automatically alert incident response personnel to inappropriate or anomalous activities that have potential security incident implications.

Assessment Objectives

  1. MON-01.12_A01 personnel or roles to be alerted when indications of inappropriate or unusual activity with cybersecurity / data privacy implications occur is/are defined.
  2. MON-01.12_A02 automated mechanisms used to alert personnel or roles are defined.
  3. MON-01.12_A03 activities that trigger alerts to personnel or are defined.
  4. MON-01.12_A04 personnel or roles is/are alerted using automated mechanisms when activities that trigger alerts indicate inappropriate or unusual activities with cybersecurity / data privacy implications.
  5. MON-01.12_A05 findings are reported to organizational personnel or roles.

Evidence Requirements

E-MON-06 Automated Event Escalation & Reporting

Documented evidence of a capability for selected events to alert applicable personnel, or roles, based on the type of event. This can be demonstrated by the configuration of a Security Incident Event Manager (SIEM), or similar technology, that helps automate event log analysis and reporting.

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.