Skip to main content

MON-12: Protection of Event Logs & Security-Relevant Telemetry

MON 10 — Critical Detect

Mechanisms exist to protect event logs, security-relevant telemetry and audit tools from unauthorized access, modification and deletion.

Renumbered: Formerly MON-08 in SCF 2025.4.

Code reused: In SCF 2025.4 and earlier, MON-12 was Session Audit. That control is now MON-18.1.

Control Question: Does the organization protect event logs and audit tools from unauthorized access, modification and deletion?

General (35)
Framework Mapping Values
AICPA TSC 2017:2022 (used for SOC 2) (source) PI1.4 PI1.5
CSA CCM 4.1.0 LOG-02 LOG-10
CSA IoT SCF 2 MON-04 MON-05
GovRAMP AU-09
GovRAMP Low AU-09
GovRAMP Low+ AU-09
GovRAMP Moderate AU-09
GovRAMP High AU-09
IEC 62443-2-1 2024 EVENT 1.6
IEC 62443-3-3 2013 SR 3.9 SR 6.1 RE 1
IEC 62443-4-2 2019 CR 3.9 CR 6.1 CR 6.1(1)
ISO 27002 2022 8.15
ISO 27017 2015 12.4.2
ISO 27018 2025 8.15
MPA Content Security Program 5.3.1 TS-1.5
NIST 800-53 R4 AU-9
NIST 800-53 R5.2 AU-09
NIST 800-53B R5 (low) (source) AU-09
NIST 800-53B R5 (moderate) (source) AU-09
NIST 800-53B R5 (high) (source) AU-09
NIST 800-82 R3 AU-09
NIST 800-82 R3 LOW OT Overlay AU-09
NIST 800-82 R3 MODERATE OT Overlay AU-09
NIST 800-82 R3 HIGH OT Overlay AU-09
NIST 800-171 R2 (source) 3.3.8
NIST 800-171 R3 (source) 03.03.03.b 03.03.06.b 03.03.08.a 03.03.08.b
NIST 800-171A (source) 3.3.8[a] 3.3.8[b] 3.3.8[c] 3.3.8[d] 3.3.8[e] 3.3.8[f]
NIST 800-171A R3 (source) A.03.03.03.b A.03.03.06.b[01] A.03.03.06.b[02] A.03.03.08.a[01] A.03.03.08.a[02] A.03.03.08.b
OWASP Top 10 2025 A01:2025 A09:2025
PCI DSS 4.0.1 (source) 10.3 10.3.1 10.3.2
PCI DSS 4.0.1 SAQ A-EP (source) 10.3.1 10.3.2
PCI DSS 4.0.1 SAQ C (source) 10.3.1 10.3.2
PCI DSS 4.0.1 SAQ D Merchant (source) 10.3.1 10.3.2
PCI DSS 4.0.1 SAQ D Service Provider (source) 10.3.1 10.3.2
SWIFT CSF 2025 6.4
US (16)
EMEA (12)
Framework Mapping Values
EMEA Germany C5 2026 OPS-11.01B.4 OPS-12.01B OPS-12.01B.1 OPS-14.01B OPS-14.03B OPS-15.02AC OPS-15.02AC.1 OPS-17.01AC OPS-19.01B.9 SIM-03.06B PSS-04.04B
EMEA Spain CCN-STIC 825 op.exp.8
EMEA EU DORA RTS 2024 Article 12.2(a) Article 12.2(d) Article 23.3
EMEA UK CAF 4.0 C1.b
EMEA UK DEFSTAN 05-138 2024 3103
EMEA UK DEFSTAN 05-138 - L2 2024 3103
EMEA UK DEFSTAN 05-138 - L3 2024 3103
EMEA LUX CCSF 20/750 2020 3.4.2-31.d
EMEA Saudi Arabia CSCC-1 2019 2-3-1-8 2-11-1-5 2-11-2
EMEA Saudi Arabia ECC-1 2018 2-14-3-3
EMEA Saudi Arabia OTCC-1 2022 2-3-1-10
EMEA Saudi Arabia SAMA CSF 1.0 2017 3.3.14.4.h
APAC (9)
Framework Mapping Values
APAC Australia CCM 2026 DET-01
APAC Australia Essential 8 2024 ISM-1815
APAC Australia ISM June 2026 ISM-1815 ISM-1985
APAC India RBI Digital Payments 2021 70.a
APAC India SEBI CSCRF 2024 PR.AA.S9
APAC Japan ISMAP 12.4.2 12.4.2.1 12.4.2.2 12.4.2.3 12.4.3.2
APAC New Zealand NZISM 3.9 16.6.12.C.01 16.6.13.C.01 16.6.13.C.02 16.6.13.C.03 16.6.13.C.04
APAC Singapore CCOP CII 2026 6.1.4(b)
APAC Singapore MAS TRM 2021 12.2.2
Americas (2)
Framework Mapping Values
Americas Bermuda BMACCC 2020 6.21-BP3
Americas Canada ITSP-10-171 2025 03.03.03.B 03.03.06.B 03.03.08.A 03.03.08.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. ▪ IT and/or cybersecurity personnel retain security event logs for a time period consistent with records retention requirements to provide support for after-the-fact investigations of security incidents and to meet statutory, regulatory and/or contractual retention requirements. ▪ IT and/or cybersecurity personnel restrict access to the management of event logs for privileged users to protect event logs and audit tools from unauthorized access, modification and deletion.

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 protect event logs and audit tools from unauthorized access, modification and deletion.

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-12_A01 audit records are retained for a time period consistent with the records retention policy.
  2. MON-12_A02 the original content of audit records is preserved.
  3. MON-12_A03 the original time ordering of audit records is preserved.
  4. MON-12_A04 audit information is protected from unauthorized access, modification, and deletion.
  5. MON-12_A05 access to management of audit logging functionality is authorized to only a subset of privileged users or roles.
  6. MON-12_A06 personnel or roles to be alerted upon detection of unauthorized access, modification or deletion of event logs, security-relevant telemetry or audit tools is/are defined.
  7. MON-12_A07 organization-defined personnel or roles are alerted upon detection of unauthorized access, modification or deletion of event logs, security-relevant telemetry or audit tools.
  8. MON-12_A08 security-relevant telemetry is protected from unauthorized access, modification and deletion.

Evidence Requirements

E-MON-12 Event Log Protection & Time Synchronization

Documented evidence of event log protection (access restriction, cryptographic protection, separate backup) and synchronization with an authoritative time source.

Event Log Monitoring

Technology Recommendations

Micro/Small

  • Secure Baseline Configurations (SBC)
  • Role Based Access Control (RBAC)

Small

  • Secure Baseline Configurations (SBC)
  • Role Based Access Control (RBAC)

Medium

  • Secure Baseline Configurations (SBC)
  • Role Based Access Control (RBAC)

Large

  • Secure Baseline Configurations (SBC)
  • Role Based Access Control (RBAC)

Enterprise

  • Secure Baseline Configurations (SBC)
  • Role Based Access Control (RBAC)

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.