STIGQter: STIG Summary: MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 26 Jan 2026:

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.

DISA Rule

SV-279394r1179490_rule

Vulnerability Number

V-279394

Group Title

SRG-APP-000515-DB-000318

Rule Version

MD8X-00-012100

Severity

CAT II

CCI(s)

• CCI-001851 - Transfer audit logs per organization-defined frequency to a different system, system component, or media than the system or system component conducting the logging.

Weight

10

Fix Recommendation

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.

Check Contents

MongoDB relies on the underlying operating system to allocate storage capacity for audit logs and as such, does not enforce arbitrary file size limits on audit logs.

System administrators should confirm that the recommended centralized system logging has been enabled (e.g., syslog on Linux systems) in the /etc/mongod.conf configuration file.

For example, on a Linux-based system using syslog, which is mirrored to an off-server centralized location, confirm that the MongoDB configuration file (default location: /etc/mongod.conf) contains a properly configured auditLog such as follows:

auditLog:
destination: syslog

If the auditLog entry is missing, or the destination does not reflect the intended application location, this is a finding.

Investigate whether there have been any incidents where MongoDB ran out of audit log space since the last time the space was allocated or other corrective measures were taken.

Vulnerability Number

V-279394

Documentable

False

Rule Version

MD8X-00-012100

Severity Override Guidance

MongoDB relies on the underlying operating system to allocate storage capacity for audit logs and as such, does not enforce arbitrary file size limits on audit logs.

System administrators should confirm that the recommended centralized system logging has been enabled (e.g., syslog on Linux systems) in the /etc/mongod.conf configuration file.

For example, on a Linux-based system using syslog, which is mirrored to an off-server centralized location, confirm that the MongoDB configuration file (default location: /etc/mongod.conf) contains a properly configured auditLog such as follows:

auditLog:
destination: syslog

If the auditLog entry is missing, or the destination does not reflect the intended application location, this is a finding.

Investigate whether there have been any incidents where MongoDB ran out of audit log space since the last time the space was allocated or other corrective measures were taken.

Check Content Reference

M

Target Key

5728