Skip to main content

MON-05.1: Real-Time Alerts of Event Logging Failure

MON 6 — Medium Detect

Mechanisms exist to provide 24x7x365 near real-time alerting capability when an event log processing failure occurs.

Control Question: Does the organization provide 24x7x365 near real-time alerting capability when an event log processing failure occurs?

General (8)
Framework Mapping Values
CSA CCM 4 LOG-13
GovRAMP High AU-05(02)
NIST AI 600-1 MG-3.2-006
NIST 800-53 R4 AU-5(2) SI-4(12)
NIST 800-53 R4 (high) AU-5(2)
NIST 800-53 R5 (source) AU-5(2) SI-4(12)
NIST 800-53B R5 (high) (source) AU-5(2) SI-4(12)
NIST 800-82 R3 HIGH OT Overlay AU-5(2) SI-4(12)
US (5)
Framework Mapping Values
US FedRAMP R4 AU-5(2)
US FedRAMP R4 (high) AU-5(2)
US FedRAMP R5 (source) AU-5(2) SI-4(12)
US FedRAMP R5 (high) (source) AU-5(2) SI-4(12)
US IRS 1075 SI-4(12)
EMEA (2)
Framework Mapping Values
EMEA Germany C5 2020 OPS-17
EMEA Israel CDMO 1.0 21.9

Capability Maturity Model

Level 0 — Not Performed

There is no evidence of a capability to provide 24x7x365 near real-time alerting capability when an event log processing failure occurs.

Level 1 — Performed Informally

C|P-CMM1 is N/A, since a structured process is required to provide 24x7x365 near real-time alerting capability when an event log processing failure occurs.

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 provide 24x7x365 near real-time alerting capability when an event log processing failure occurs.

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 provide 24x7x365 near real-time alerting capability when an event log processing failure occurs.

Assessment Objectives

  1. MON-05.1_A01 real-time period requiring alerts when event log failure events occur is defined.
  2. MON-05.1_A02 personnel, roles, and/or locations to be alerted in real time when event log failure events occur is/are defined.
  3. MON-05.1_A03 event logging failure events requiring real-time alerts are defined.
  4. MON-05.1_A04 an alert is provided within organization-defined real-time period to organization-defined personnel, roles, and/or locations when organization-defined event logging failure events requiring real-time alerts occur.

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.