MON-12.2: Event Log & Security-Relevant Telemetry Access by Subset of Privileged Users
Mechanisms exist to restrict access to the management of event logs and security-relevant telemetry to privileged users with a specific business need.
Renumbered: Formerly MON-08.2 in SCF 2025.4.
Control Question: Does the organization restrict access to the management of event logs to privileged users with a specific business need?
General (24)
| Framework | Mapping Values |
|---|---|
| CSA CCM 4.1.0 | LOG-04 |
| CSA IoT SCF 2 | MON-04 MON-05 |
| GovRAMP | AU-09(04) |
| GovRAMP Moderate | AU-09(04) |
| GovRAMP High | AU-09(04) |
| IEC 62443-3-3 2013 | SR 6.1 |
| IEC 62443-4-2 2019 | CR 6.1 |
| NIST 800-53 R4 | AU-9(4) |
| NIST 800-53 R5.2 | AU-09(04) |
| NIST 800-53B R5 (moderate) (source) | AU-09(04) |
| NIST 800-53B R5 (high) (source) | AU-09(04) |
| NIST 800-82 R3 | AU-09(04) |
| NIST 800-82 R3 MODERATE OT Overlay | AU-09(04) |
| NIST 800-82 R3 HIGH OT Overlay | AU-09(04) |
| NIST 800-171 R2 (source) | 3.3.9 |
| NIST 800-171 R3 (source) | 03.03.08.a 03.03.08.b |
| NIST 800-171A (source) | 3.3.9[a] 3.3.9[b] |
| NIST 800-171A R3 (source) | A.03.03.08.a[01] A.03.03.08.b |
| OWASP Top 10 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 |
US (8)
| Framework | Mapping Values |
|---|---|
| USA Federal CMS MARS-E 2.0 | AU-9(4) |
| USA Federal CISA CPG 2022 | 2.U |
| USA Federal CMMC 2.0 Level 2 | AUL2.-3.3.9 |
| USA Federal CJIS Security Policy 6.0 | AU-9(4) |
| USA Federal FedRAMP R5 (moderate) | AU-09(04) |
| USA Federal FedRAMP R5 (high) | AU-09(04) |
| USA Federal IRS 1075 2021 | AU-9(CE-4) |
| USA Federal 33 CFR Part 101 Subpart F | 101.650(c)(1) |
APAC (2)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-1985 |
| APAC New Zealand NZISM 3.9 | 16.4.41.C.03 |
Americas (1)
| Framework | Mapping Values |
|---|---|
| Americas Canada ITSP-10-171 2025 | 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 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 restrict access to the management of event logs to privileged users with a specific business need.
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
- MON-12.2_A01 a subset of privileged users or roles authorized to access management of event logging functionality is defined.
- MON-12.2_A02 access to management of audit logging functionality is authorized to only a subset of privileged users or roles.
- MON-12.2_A03 access to the management of security-relevant telemetry is restricted to privileged users with a specific business need.
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)