MD4X-00-002800 - MongoDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to prevent potential misuse and compromise of the system.

Organizational users include organizational employees or individuals the organization deems to have equivalent status of employees (e.g., contractors). Organizational users (and any processes acting on behalf of users) must be uniquely identified and authenticated for all accesses, except the following:

(i) Accesses explicitly identified and documented by the organization. Organizations document specific user actions that can be performed on the information system without identification or authentication; and
(ii) Accesses that occur through authorized use of group authenticators without individual authentication. Organizations may require unique identification of individuals using shared accounts, for detailed accountability of individual activity.

Solution

For any user not a member of an appropriate organization and has access to a database in the system, run the following command:

use database
db.dropUser(%username%, {w: 'majority', wtimeout: 5000})

If the %MongoDB configuration file% (default location: /etc/mongod.conf) does not contain

security:
authorization: enabled

Edit the %MongoDB configuration file%, add these parameters, stop/start (restart) any mongod or mongos process using this %MongoDB configuration file%.

See Also

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

Item Details

References: CAT|II, CCI|CCI-000764, Rule-ID|SV-252157r813853_rule, STIG-ID|MD4X-00-002800, Vuln-ID|V-252157

Plugin: Unix

Control ID: 92110cb118811b05e18881f7fc437390751bfd9c690a346996cc3b20c185705c