STIGhubSTIGhub
STIGsSearchCompareAbout

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
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

MongoDB Enterprise Advanced 4.x Security Technical Implementation Guide

Version

V1R4

Benchmark ID

MongoDB_Enterprise_Advanced_4-x_STIG

Total Checks

52

Tags

database
CAT I: 11CAT II: 41CAT III: 0

This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: disa.stig_spt@mail.mil.

Export CKLExport CSVExport JSON

Checks (52)

V-252134MEDIUMMongoDB must provide audit record generation for DoD-defined auditable events within all DBMS/database components.V-252135MEDIUMThe audit information produced by MongoDB must be protected from unauthorized access.V-252136MEDIUMMongoDB must protect its audit features from unauthorized access.V-252137MEDIUMUnused database components that are integrated in MongoDB and cannot be uninstalled must be disabled.V-252138MEDIUMUnused database components that are integrated in MongoDB and cannot be uninstalled must be disabled.V-252139HIGHIf passwords are used for authentication, MongoDB must transmit only encrypted representations of passwords.V-252140MEDIUMMongoDB must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).V-252141MEDIUMMongoDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.V-252142MEDIUMMongoDB must prevent unauthorized and unintended information transfer via shared system resources.V-252143MEDIUMMongoDB and associated applications must reserve the use of dynamic code execution for situations that require it.V-252144MEDIUMMongoDB must associate organization-defined types of security labels having organization-defined security label values with information in storage and transmission.V-252145MEDIUMMongoDB must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.V-252146HIGHMongoDB must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.V-252147MEDIUMMongoDB must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components.V-252148MEDIUMMongoDB must limit the total number of concurrent connections to the database.V-252149HIGHMongoDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.V-252150HIGHMongoDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.V-252151MEDIUMMongoDB must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to MongoDB.V-252152HIGHMongoDB software installation account must be restricted to authorized users.V-252153MEDIUMDatabase software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.V-252154MEDIUMDatabase objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to MongoDB, etc.) must be owned by database/DBMS principals authorized for ownership.V-252155MEDIUMThe role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to MongoDB, etc.) must be restricted to authorized users.V-252156MEDIUMUnused database components that are integrated in MongoDB and cannot be uninstalled must be disabled.V-252157MEDIUMMongoDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).V-252158HIGHIf passwords are used for authentication, MongoDB must implement LDAP or Kerberos for authentication to enforce the DoD standards for password complexity and lifetime.V-252159HIGHIf passwords are used for authentication, MongoDB must store only hashed, salted representations of passwords.V-252160HIGHMongoDB must enforce authorized access to all PKI private keys stored/utilized by MongoDB.V-252161MEDIUMMongoDB must map the PKI-authenticated identity to an associated user account.V-252162HIGHMongoDB must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.V-252163MEDIUMMongoDB must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).V-252164MEDIUMMongoDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.V-252165HIGHMongoDB must protect the confidentiality and integrity of all information at rest.V-252166MEDIUMDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.V-252167MEDIUMMongoDB must check the validity of all data inputs except those specifically identified by the organization.V-252168MEDIUMMongoDB must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.V-252169MEDIUMMongoDB must reveal detailed error messages only to the ISSO, ISSM, SA, and DBA.V-252170MEDIUMMongoDB must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.V-252171MEDIUMMongoDB must utilize centralized management of the content captured in audit records generated by all components of MongoDB.V-252172MEDIUMMongoDB must allocate audit record storage capacity in accordance with site audit record storage requirements.V-252173MEDIUMMongoDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity.V-252174MEDIUMMongoDB must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.V-252175MEDIUMMongoDB must enforce access restrictions associated with changes to the configuration of MongoDB or database(s).V-252176MEDIUMMongoDB must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.V-252177MEDIUMMongoDB must prohibit the use of cached authenticators after an organization-defined time period.V-252178MEDIUMMongoDB must only accept end entity certificates issued by DoD PKI or DoD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions.V-252179MEDIUMMongoDB must maintain the confidentiality and integrity of information during preparation for transmission.V-252180MEDIUMMongoDB must maintain the confidentiality and integrity of information during reception.V-252181MEDIUMWhen invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives.V-252182MEDIUMWhen updates are applied to MongoDB software, any software components that have been replaced or made unnecessary must be removed.V-252183MEDIUMSecurity-relevant software updates to MongoDB must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).V-252184HIGHMongoDB products must be a version supported by the vendor.V-252185MEDIUMMongoDB must be configured in accordance with the security configuration settings based on DoD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs.