STIGViewer Support

MongoDB must, for password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-279349MD8X-00-003600SV-279349r1179508_ruleCCI-004062high
Description
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 authorizing official (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 the DBMS.
STIGDate
MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide2026-02-20

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

IAC-10Authenticator Management
0.50
IAC-10.1Password-Based Authentication
0.50
IAC-10.4Automated Support For Password Strength
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (58) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(10)Shared and Group Account Credential Change
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-3(4)Discretionary Access Control
1.00

+48 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (4) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.5.10
1.00
3.5.7
1.00
3.5.8
1.00
3.5.9
1.00
CCI1 mapping

Details

Check Text (C-279349r1179508_chk)

MongoDB supports the Salted Challenge Response Authentication Mechanism (SCRAM) as the default authentication mechanism for MongoDB. Run the following script for database in the MongoDB system: /// Connect to admin database db = db.getSiblingDB('admin'); // Get all users without SCRAM-SHA-256 const allUsers = db.system.users.find().toArray(); const usersToUpgrade = allUsers.filter(user => !user.credentials || !user.credentials["SCRAM-SHA-256"] ); print(`Found ${usersToUpgrade.length} users without SCRAM-SHA-256 authentication`); if (usersToUpgrade.length === 0) { print("All users already using SCRAM-SHA-256. No action needed."); quit(); } // Display users that need upgrading print("\nUsers needing upgrade to SCRAM-SHA-256:"); usersToUpgrade.forEach(user => { print(`- User: ${user.user}, Database: ${user.db}`); }); If any user found in a database using password authentication does not have "Using SCRAM-SHA-256: YES", this is a finding.

Fix Text (F-83807r1179451_fix)

For each user that does not have SCRAM-SHA-256, run the following command: use admin db.runCommand({'updateUser':'<their username>',pwd: passwordPrompt() , mechanisms:['SCRAM-SHA-256']})