Detections
Analytics
MD8X-00-012100 - MongoDB must off-load audit data to a separate log management facility; this shall be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems.
Information
Information stored in one location is vulnerable to accidental or incidental deletion or alteration.Off-loading is a common process in information systems with limited audit storage capacity.
The Database management system (DBMS) may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with off-loading the records to the centralized system.
Solution
To specify auditLog, or a centralized system log (recommended), configure these in the mongod.conf configuration file:auditLog:
destination: syslog
Refer to documentation for additional configuration:
https://www.mongodb.com/docs/v8.0/core/auditing/
When deploying a Log Forwarding Tool, use a monitor for the audit log file and push records to a centralized log management system (e.g., Elasticsearch, Splunk, or a custom solution).
Allocate sufficient space to the storage volume hosting the file identified in the MongoDB configuration "auditLog.path" to support audit file peak demand.
See Also
https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MDB_Enterprise_Advanced_8-x_V1R1_STIG.zip
Item Details
Category: AUDIT AND ACCOUNTABILITY
References: 800-53|AU-4(1), CAT|II, CCI|CCI-001851, Rule-ID|SV-279394r1179490_rule, STIG-ID|MD8X-00-012100, Vuln-ID|V-279394
Plugin: Unix
Control ID: 3be98e0fb17ee29374eb23d48a38347386af556178fb6f393126a95da0d96fec