Skip to main content
CUI

STIG Rule - V-279399

V-279399

SV-279399r1179524_rule

CAT II

MongoDB must require users to be individually authenticated before granting access to the shared accounts or resources.

From: MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide (V1R1)

Description

<VulnDiscussion>Individual authentication prior to shared group authentication mitigates the risk of using group accounts or authenticators.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>

Check Procedure

Check the MongoDB configuration file (default location /etc/mongod.conf) for a section named "security". If this section does not contain the subkey of "authorization" with a value of "enabled" as shown below, this is a finding. security: authorization: enabled

Fix Text

Enable authorization for MongoDB Enterprise. Read the directions in the MongoDB documentation here: https://www.mongodb.com/docs/v8.0/tutorial/configure-scram-client-authentication/ Create the user administrator. Edit the MongoDB database configuration file (default location /etc/mongod.conf) to contain the following setting in the security section: security: authorization: enabled Stop/start (restart) the mongod or mongos instance using this configuration. Log on to MongoDB as an authorized user created by the user administrator and run the following command to verify the output is "true": db.getSiblingDB("admin").runCommand({getCmdLineOpts: 1}).parsed.security.authorization The output of this command must be "true".

CCI Reference

CCI-004045
Created
2026-04-07 20:08:22
Last Updated
2026-04-07 20:08:22
CUI