Details

Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system.

When dealing with access restrictions pertaining to change control, it should be noted that any changes to the hardware, software, and/or firmware components of the information system can potentially have significant effects on the overall security of the system.

Accordingly, only qualified and authorized individuals should be allowed to obtain access to system components for the purposes of initiating changes, including upgrades and modifications.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

Prereq: To view a user’s roles, must have the ‘viewUser’ privilege.
https://docs.mongodb.com/v3.4/reference/privilege-actions/

Connect to MongoDB.

For each database, identify the user’s roles for the database.

use
db.getUser(‘[username]’)

The server will return a document with the user’s roles.

To revoke a user’s role from a database use the db.revokeRolesFromUser() method.
https://docs.mongodb.com/v3.4/reference/method/db.revokeRolesFromUser/

To grant a role to a user use the db.grantRolesToUser() method. https://docs.mongodb.com/v3.4/reference/method/db.grantRolesToUser/

Supportive Information

The following resource is also helpful.

• https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MDB_Enterprise_Advanced_3-x_V1R2_STIG.zip

This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system MongoDB.

References

• 800-53|CM-5(1)
• CAT|II
• CCI|CCI-001813
• Rule-ID|SV-96625r1_rule
• STIG-ID|MD3X-00-000670
• Vuln-ID|V-81911

Source

• Tenable.com/audits