V-252136

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. It is, therefore, 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 Content

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 660, this is a finding.

Note that the audit destination cannot be modified at runtime.