STIGhubSTIGhub
STIGsRMF ControlsCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • RMF Controls
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to MongoDB Enterprise Advanced 4.x Security Technical Implementation Guide

V-252159

CAT I (High)

If passwords are used for authentication, MongoDB must store only hashed, salted representations of passwords.

Rule ID

SV-252159r981949_rule

STIG

MongoDB Enterprise Advanced 4.x Security Technical Implementation Guide

Version

V1R4

CCIs

CCI-000196

Discussion

The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be used only when it is not possible to employ a PKI certificate, and requires AO approval. In such cases, database passwords stored in clear text, using reversible encryption, or using unsalted hashes would be vulnerable to unauthorized disclosure. Database passwords must always be in the form of one-way, salted hashes when stored internally or externally to MongoDB.

Check Content

MongoDB supports several authentication mechanisms, some of which store credentials on the MongoDB server. 

If these mechanisms are in use, MongoDBs authSchemaVersion in the admin.system.version collection must be set to 5.

1. Validate that authenticationMechansisms is defined in config file (default location /etc/mongod.conf).

The MongoDB Configuration file should contain the similar to the following entry:

setParameter:
  authenticationMechanisms: SCRAM-SHA-256 

If the config file does not contain an authenticationMechanisms entry, this is a finding.

2. Validate authSchemaVersion is set to 5.

  Using the shell, run the following command:

 db.getSiblingDB("admin").system.version.find({ "_id" : "authSchema"}, {_id: 0})

  It should return:
    { "currentVersion" : 5 }

If currentVersion is less than 5, this is a finding.

Fix Text

1. If authenticationMechanisms is not defined in the %MongoDB configuration file% (default location: /etc/mongod.conf), define one of more authenticationMechanisms, from the subset below:

SCRAM-SHA-1
SCRAM-SHA-256
MONGODB-X509
GSSAPI
PLAIN

which the MongoDB server process must accept.

Example:

setParameter:
  authenticationMechanisms: SCRAM-SHA-1,SCRAM-SHA-256

2. If authSchemaVersion is less than 5.

Run the following command:

 db.adminCommand({authSchemaUpgrade: 1})

In the unlikely event that an error is encountered, safely rerun the authSchemaUpgrade command.