Details
Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack.
The content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records.
MongoDB 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
Install a centralized syslog collecting tool and configured it as instructed in its documentation.
To enable auditing and print audit events to the syslog in JSON format, specify the syslog for the –auditDestination setting:
mongod –dbpath data/db –auditDestination syslog
Alternatively, these options can also be specified in the configuration file:
storage:
dbPath: data/db
auditLog:
destination: syslog
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Audit and Accountability.This control applies to the following type of system Unix.
References
- 800-53|AU-3(2)
- CAT|II
- CCI|CCI-001844
- Rule-ID|SV-96617r1_rule
- STIG-ID|MD3X-00-000600
- Vuln-ID|V-81903