STIGUI
V-265909CAT II — Medium severitySV-265909r1028719_rule

MongoDB must protect its audit features from unauthorized access.

Rule version MD7X-00-002300 · STIG v1 · 2026-05-23

Discussion

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data.

Depending upon the log format and application, system and application log tools may provide the only means to manipulate and manage application and system log data. Therefore, it is imperative that access to audit tools be controlled and protected from unauthorized access.

Applications providing tools to interface with audit data will leverage user permissions and roles identifying the user accessing the tools and the corresponding rights the user enjoys in order make access decisions regarding the access to audit tools.

Audit tools include, but are not limited to, OS-provided audit tools, vendor-provided audit tools, and open source audit tools needed to successfully view and manipulate audit information system activity and records.

If an attacker were to gain access to audit tools, they could analyze audit logs for system weaknesses or weaknesses in the auditing itself. An attacker could also manipulate logs to hide evidence of malicious activity.

Satisfies: SRG-APP-000121-DB-000202, SRG-APP-000122-DB-000203, SRG-APP-000123-DB-000204

Check

To ensure audit configurations are protected from unauthorized modification, the default installation of MongoDB restricts permission on the configuration file.

Verify User ownership, Group ownership, and permissions on the "<MongoDB configuration file>":

(default name and location is /etc/mongod.conf)

(The name and location for the MongoDB configuration file will vary according to local circumstances.)

Using the default name and location the command would be:

$ stat /etc/mongod.conf

If the User owner is not "mongod", this is a finding.

If the Group owner is not "mongod", this is a finding.

If the filename is more permissive than "600", this is a finding.

Note that the audit destination cannot be modified at runtime.

Fix

Run these commands:

"chown mongod <MongoDB configuration file>" "chgrp mongod <MongoDB configuration file>" "chmod 600 <MongoDB configuration file>"

(The name and location for the MongoDB configuration file will vary according to local circumstances. The default name and location is /etc/mongod.conf.)

Using the default name and location the commands would be:

$ chown mongod /etc/mongod.conf  
$ chgrp  mongod /etc/mongod.conf  
$ chmod 660 /etc/mongod.conf

Identifiers

Group ID
V-265909
Group title
SRG-APP-000121-DB-000202
Rule ID
SV-265909r1028719_rule
Check ID
C-69827r1028511_chk
Fix ID
F-69731r1028512_fix