MongoDB
TMA-MONGODB-5.1
Ensure that system activity is audited
Description
Track access and changes to database configurations and data. MongoDB Enterprise includes a system auditing facility that can record system events (e.g. user operations, connection events) on a MongoDB instance. These audit records permit forensic analysis and allow administrators to verify proper controls. Checks the YAML config file /etc/mongod.conf (SKIP when it does not exist). Auditing requires MongoDB Enterprise or Percona Server for MongoDB.
How it is checked
Audit method: File pattern
- File
/etc/mongod.conf- Pattern
(?m)^auditLog:[ \t]*\n(?:[ \t]*(?:#[^\n]*)?\n|[ \t]+[^\n]*\n)*?[ \t]+destination:[ \t]*['\x22]?(?:file|syslog|console)\b
How it is fixed
Fix method: Guidance or infrastructure patch
Add 'auditLog: {destination: file, format: JSON, path: /var/log/mongodb/auditLog.json}' (or destination: syslog) to /etc/mongod.conf and restart mongod.
Properties
- Operating systems
- Any
- Tags
- mongodbloggingaudit
- Reference
- CIS MongoDB 8 Benchmark v2.0.0 - 5.1 Ensure that system activity is audited
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
tmaegis scan --target mongodb