MongoDB must separate user functionality (including user interface services) from database management functionality.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-265924	SRG-APP-000211-DB-000122	MD7X-00-004600	SV-265924r1028722_rule	2024-09-27	1

Description
Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods, as appropriate. An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different domain and with additional access controls. If administrative functionality or information regarding DBMS management is presented on an interface available for users, information on DBMS settings may be inadvertently made available to the user.

Description

Information system management functionality includes functions necessary to administer databases, network components, workstations, or servers and typically requires privileged user access. The separation of user functionality from information system management functionality is either physical or logical and is accomplished by using different computers, different central processing units, different instances of the operating system, different network addresses, combinations of these methods, or other methods, as appropriate. An example of this type of separation is observed in web administrative interfaces that use separate authentication methods for users of any other information system resources. This may include isolating the administrative interface on a different domain and with additional access controls. If administrative functionality or information regarding DBMS management is presented on an interface available for users, information on DBMS settings may be inadvertently made available to the user.

ℹ️ Check
MongoDB grants access to data and commands through role-based authorization and provides built-in roles that provide the different levels of access commonly needed in a database system. Additionally, user-defined roles can be created. Check a user's role to ensure correct privileges for the function: Run the following command to get a list of all the databases in the system: > show dbs For each database in the system, identify the user's roles for the database: > use <database> > db.getUsers() The server will return a document with the all users in the data and their associated roles. View a role's privileges: For each database, identify the privileges granted by a role: > use <database> > db.getRole( "<role name>", { showPrivileges: true } ) The server will return a document with the "privileges" and "inheritedPrivileges" arrays. The "privileges returned document lists the privileges directly specified by the role and excludes those privileges inherited from other roles. The "inheritedPrivileges" returned document lists all privileges granted by this role, both directly specified and inherited. If the role does not inherit from other roles, the two fields are the same. If a user has a role with inappropriate privileges, this is a finding.

ℹ️ Check

MongoDB grants access to data and commands through role-based authorization and provides built-in roles that provide the different levels of access commonly needed in a database system. Additionally, user-defined roles can be created. Check a user's role to ensure correct privileges for the function: Run the following command to get a list of all the databases in the system: > show dbs For each database in the system, identify the user's roles for the database: > use <database> > db.getUsers() The server will return a document with the all users in the data and their associated roles. View a role's privileges: For each database, identify the privileges granted by a role: > use <database> > db.getRole( "<role name>", { showPrivileges: true } ) The server will return a document with the "privileges" and "inheritedPrivileges" arrays. The "privileges returned document lists the privileges directly specified by the role and excludes those privileges inherited from other roles. The "inheritedPrivileges" returned document lists all privileges granted by this role, both directly specified and inherited. If the role does not inherit from other roles, the two fields are the same. If a user has a role with inappropriate privileges, this is a finding.

✔️ Fix
Administrators using MongoDB should document the appropriate privileges for various roles appropriate to the application. For each database, identify the user's roles for the database. > use <database> > 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 following: > db.revokeRolesFromUser( "<username>", [ <roles> ], { <writeConcern> } ) To grant a role to a user use the following: > db.grantRolesToUser( "<username>", [ <roles> ], { <writeConcern> } )

✔️ Fix

Administrators using MongoDB should document the appropriate privileges for various roles appropriate to the application. For each database, identify the user's roles for the database. > use <database> > 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 following: > db.revokeRolesFromUser( "<username>", [ <roles> ], { <writeConcern> } ) To grant a role to a user use the following: > db.grantRolesToUser( "<username>", [ <roles> ], { <writeConcern> } )