MongoDB
TMA-MONGODB-5.3
Ensure that logging captures as much information as possible
LowLevel 2Automatedmongodb
Description
The SystemLog.quiet option stops logging of information such as: - connection events - authentication events - replication sync activities - evidence of some potentially impactful commands being run (eg: drop, dropIndexes, validate) This information should be logged whenever possible. This check is only for Enterprise editions. Checks the YAML config file /etc/mongod.conf (SKIP when it does not exist). Passes when systemLog.quiet is absent or false.
How it is checked
Audit method: File pattern
- File
/etc/mongod.conf- Pattern
(?m)^[ \t]*quiet:[ \t]*['\x22]?true\b
How it is fixed
Fix method: Guidance or infrastructure patch
Set systemLog.quiet: false (or remove the quiet setting) in /etc/mongod.conf and restart mongod.
Properties
- Operating systems
- Any
- Tags
- mongodblogging
- Reference
- CIS MongoDB 8 Benchmark v2.0.0 - 5.3 Ensure that logging captures as much information as possible
Check this host
Run this on a machine you are allowed to audit. The scan is read-only.
shell
tmaegis scan --target mongodb --level 2