STIGQter: STIG Summary: MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide Version: 1 Release: 1 Benchmark Date: 26 Jan 2026:

MongoDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.

DISA Rule

SV-279332r1179502_rule

Vulnerability Number

V-279332

Group Title

SRG-APP-000023-DB-000001

Rule Version

MD8X-00-000200

Severity

CAT I

CCI(s)

CCI-000015 - Support the management of system accounts using (organization-defined automated mechanisms).

Weight

Fix Recommendation

Edit the MongoDB configuration file (default location /etc/mongod.conf) to include the following:

security:
authorization: "enabled"

This will enable SCRAM-SHA-256 authentication (default).

Instruction on configuring the default authentication is provided here:
https://www.mongodb.com/docs/v8.0/tutorial/enable-authentication/

The high-level steps described by the above will require the following:

1. Start MongoDB without access control.
2. Connect to the instance.
3. Create the user administrator.
4. Restart the MongoDB instance with access control.
5. Connect and authenticate as the user administrator.
6. Create additional users as needed for the deployment.

For OIDC, edit the MongoDB configuration file (default location /etc/mongod.conf) to include the following:

setParameter:
authenticationMechanisms: "MONGODB-OIDC"
oidcIdentityProviders: [ {
issuer: "<Issuer URL from IdP>",
audience: "<>",
matchPattern: "<>",
JWKSPollSecs: "<>"
} ]

Configuration information for OIDC for MongoDB can be found here: https://www.mongodb.com/docs/manual/core/oidc/workforce/configure-oidc/#std-label-configure-oidc.

Configuration information for OAuth 2.0 for MongoDB can be found here: https://www.mongodb.com/docs/manual/core/oidc/workload/configure-mongodb-workload/#std-label-configure-mongodb-workload.

Check Contents

Verify that the MongoDB configuration file (default location /etc/mongod.conf) contains the following:

security:
authorization: "enabled"

If using OIDC for human users:

Verify the MongoDB configuration file (default location: /etc/mongod.conf) contains the following:

setParameter:
authenticationMechanisms: "MONGODB-OIDC"
oidcIdentityProviders: [ {
issuer: "<Issuer URL from IdP>",
audience: "<>",
matchPattern: "<>",
JWKSPollSecs: "<>"
} ]

If this parameter is not present, this is a finding.

Refer to Security OIDC/OAuth 2.0 configuration documentation for additional details:
https://www.mongodb.com/docs/manual/core/oidc/security-oidc/

Vulnerability Number

V-279332

Documentable

False

Rule Version

MD8X-00-000200

Severity Override Guidance

Check Content Reference

Target Key

5728