V-279337

Discussion

Protecting audit data also includes identifying and protecting the tools used to view and manipulate log data. Therefore, protecting audit tools is necessary to prevent unauthorized operation on audit data. 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 to make access decisions regarding the deletion of audit tools. Audit tools include, but are not limited to, vendor-provided and open source audit tools needed to successfully view and manipulate audit information system activity and records. Audit tools include custom queries and report generators. Satisfies: SRG-APP-000123-DB-000204, SRG-APP-000121-DB-000202, SRG-APP-000122-DB-000203

Check Content

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

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

Note: 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.