MON-32: Database Logging
Mechanisms exist to ensure databases produce audit records that contain sufficient information to monitor database activities.
Renumbered: Formerly MON-03.7 in SCF 2025.4.
Control Question: Does the organization ensure databases produce audit records that contain sufficient information to monitor database activities?
General (4)
| Framework | Mapping Values |
|---|---|
| NIST 800-171A (source) | 3.3.2[a] |
| PCI DSS 4.0.1 (source) | 7.2.6 |
| PCI DSS 4.0.1 SAQ D Merchant (source) | 7.2.6 |
| PCI DSS 4.0.1 SAQ D Service Provider (source) | 7.2.6 |
US (1)
| Framework | Mapping Values |
|---|---|
| USA Federal FFIEC ITEH 2016 | II.C.18 |
EMEA (1)
| Framework | Mapping Values |
|---|---|
| EMEA Saudi Arabia CSCC-1 2019 | 2-2-1-8 |
APAC (3)
| Framework | Mapping Values |
|---|---|
| APAC Australia ISM June 2026 | ISM-1537 |
| APAC New Zealand NZISM 3.9 | 16.6.7.C.01 16.6.9.C.01 16.6.10.C.01 16.6.10.C.02 |
| APAC Singapore CCOP CII 2026 | 5.13.4 6.1.1(a) |
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.
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 ensure databases produce audit records that contain sufficient information to monitor database activities.
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-32_A01 the content of database audit records needed to support the ability to uniquely trace account actions is defined.
- MON-32_A02 database audit records contain information that establishes the identity of any individuals, subjects or objects/entities associated with the event.
Evidence Requirements
- E-MON-09 Event Logs
-
Documented evidence of event logs being generated by Technology Assets, Applications and/or Services (TAAS).
Event Log Monitoring
Technology Recommendations
Micro/Small
- Secure Baseline Configurations (SBC)
Small
- Secure Baseline Configurations (SBC)
Medium
- Secure Baseline Configurations (SBC)
Large
- Secure Baseline Configurations (SBC)
Enterprise
- Secure Baseline Configurations (SBC)