OpenControls Logo

STIG Viewer

STIGViewer Support

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

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-279332MD8X-00-000200SV-279332r1179502_ruleCCI-000015high
Description
Enterprise environments make account management for applications and databases challenging and complex. A manual process for account management functions adds the risk of a potential oversight or other error. Managing accounts for the same person in multiple places is inefficient and prone to problems with consistency and synchronization. A comprehensive application account management process that includes automation helps to ensure that accounts designated as requiring attention are consistently and promptly addressed. Examples include, but are not limited to, using automation to take action on multiple accounts designated as inactive, suspended, or terminated, or by disabling accounts located in noncentralized account stores, such as multiple servers. Account management functions can also include assignment of group or role membership; identifying account type; specifying user access authorizations (i.e., privileges); account removal, update, or termination; and administrative alerts. The use of automated mechanisms can include, for example, using email or text messaging to notify account managers when users are terminated or transferred; using the information system to monitor account usage; and using automated telephone notification to report atypical system account usage. The DBMS must be configured to automatically use organization-level account management functions, and these functions must immediately enforce the organization's current account policy. Automation may comprise differing technologies, which when placed together, contain an overall mechanism supporting an organization's automated account management requirements.
STIGDate
MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide2026-02-20

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) 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-15.1Automated System Account Management (Directory Services)
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (72) 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-12Session Termination
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-17(9)Disconnect or Disable Access
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

+62 more (top 10 by confidence shown)

CCI1 mapping
CCI-000015
1.00

Details

Check Text (C-279332r1179502_chk)

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/

Fix Text (F-83790r1179440_fix)

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.