STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide

V-279333

CAT I (High)

MongoDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.

Rule ID

SV-279333r1179443_rule

STIG

MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000213

Discussion

Authentication with a DOD-approved PKI certificate does not necessarily imply authorization to access the DBMS. To mitigate the risk of unauthorized access to sensitive information by entities that have been issued certificates by DOD-approved PKIs, all DOD systems, including databases, must be properly configured to implement access control policies. Successful authentication must not automatically give an entity access to an asset or security boundary. Authorization procedures and controls must be implemented to ensure each authenticated entity also has a validated and current authorization. Authorization is the process of determining whether an entity, once authenticated, is permitted to access a specific asset. Information systems use access control policies and enforcement mechanisms to implement this requirement. Access control policies include identity-based policies, role-based policies, and attribute-based policies. Access enforcement mechanisms include access control lists, access control matrices, and cryptography. These policies and mechanisms must be employed by the application to control access between users (or processes acting on behalf of users) and objects (e.g., devices, files, records, processes, programs, and domains) in the information system. This requirement is applicable to access control enforcement applications, a category that includes database management systems. If the DBMS does not follow applicable policy when approving access, it may be in conflict with networks or other applications in the information system. This may result in users either gaining or being denied access inappropriately and in conflict with applicable policy.

Check Content

The MongoDB administrator must ensure that additional application access control is enforced.

Review the system documentation to determine the required levels of protection for MongoDB server securables by type of login. 

Review the permissions actually in place on the server.

Run the command to view roles and privileges in a particular <database> :

use <database>
db.getRoles(
    {
      rolesInfo: 1,
      showPrivileges: true,
      showBuiltinRoles: true
    }
)

If the permissions do not match the documented requirements, this is a finding.

Fix Text

Use the following statements to add and remove permissions on MongoDB server securables, bringing them in line with the documented requirements:

createRole(), 
updateRole(), 
dropRole(), 
grantRolesToUser()

MongoDB commands for role management can be found here:
https://www.mongodb.com/docs/v8.0/reference/method/js-role-management/