From MongoDB Enterprise Advanced 3.x Security Technical Implementation Guide
Part of SRG-APP-000380-DB-000360
Associated with: CCI-001813
Failure to provide logical access restrictions associated with changes to configuration may have significant effects on the overall security of the system.
Review the security configuration of the MongoDB database(s). If unauthorized users can start the mongod or mongos processes or edit the MongoDB configuration file (default location: /etc/mongod.conf), this is a finding. If MongoDB does not enforce access restrictions associated with changes to the configuration of the database(s), this is a finding. To assist in conducting reviews of permissions, the following MongoDB commands describe permissions of databases and users: Permissions of concern in this respect include the following, and possibly others: - any user with a role of userAdminAnyDatabase role or userAdmin role - any database or with a user have a role or privilege with "C" (create) or "w" (update) privileges that are not necessary MongoDB commands to view roles in a particular database: db.getRoles( { rolesInfo: 1, showPrivileges:true, showBuiltinRoles: true })
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
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer