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 7.x Security Technical Implementation Guide

Version

V1R1

Benchmark ID

MongoDB_Enterprise_Advanced_7-x_STIG

Total Checks

50

Tags

database
CAT I: 11CAT II: 39CAT 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 (50)

V-265905HIGHMongoDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.V-265906HIGHMongoDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.V-265907MEDIUMMongoDB must provide audit record generation for DOD-defined auditable events within all DBMS/database components.V-265908MEDIUMThe audit information produced by MongoDB must be protected from unauthorized access.V-265909MEDIUMMongoDB must protect its audit features from unauthorized access.V-265910MEDIUMMongoDB must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to MongoDB.V-265911HIGHMongoDB software installation account must be restricted to authorized users.V-265912MEDIUMDatabase software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.V-265913MEDIUMDatabase 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-265914MEDIUMThe role(s)/group(s) used to modify database structure (including but not 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-265915MEDIUMUnused database components that are integrated in MongoDB and cannot be uninstalled must be disabled.V-265916MEDIUMMongoDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).V-265917HIGHIf passwords are used for authentication, MongoDB must store only hashed, salted representations of passwords.V-265918HIGHIf passwords are used for authentication, MongoDB must transmit only encrypted representations of passwords.V-265919HIGHMongoDB must enforce authorized access to all PKI private keys stored/used by MongoDB.V-265920MEDIUMMongoDB must map the PKI-authenticated identity to an associated user account.V-265921HIGHMongoDB must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.V-265922HIGHMongoDB must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.V-265923MEDIUMMongoDB must uniquely identify and authenticate nonorganizational users (or processes acting on behalf of nonorganizational users).V-265924MEDIUMMongoDB must separate user functionality (including user interface services) from database management functionality.V-265925MEDIUMMongoDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.V-265926HIGHMongoDB must protect the confidentiality and integrity of all information at rest.V-265927MEDIUMDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.V-265928MEDIUMMongoDB must prevent unauthorized and unintended information transfer via shared system resources.V-265929MEDIUMMongoDB must check the validity of all data inputs except those specifically identified by the organization.V-265930MEDIUMMongoDB and associated applications must reserve the use of dynamic code execution for situations that require it.V-265931MEDIUMMongoDB must provide nonprivileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries.V-265932MEDIUMMongoDB must reveal detailed error messages only to the information system security officer (ISSO), information system security manager (ISSM), system administrator (SA), and database administrator (DBA).V-265933MEDIUMThe DBMS must automatically terminate a user session after organization-defined conditions or trigger events requiring session disconnect.V-265934MEDIUMMongoDB must associate organization-defined types of security labels having organization-defined security label values with information in storage.V-265935MEDIUMMongoDB must enforce discretionary access control (DAC) policies, as defined by the data owner, over defined subjects and objects.V-265936MEDIUMMongoDB must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures.V-265938MEDIUMMongoDB must allocate audit record storage capacity in accordance with site audit record storage requirements.V-265939MEDIUMMongoDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity.V-265940MEDIUMMongoDB must provide an immediate real-time alert to appropriate support staff of all audit log failures.V-265941MEDIUMMongoDB must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.V-265942MEDIUMMongoDB must enforce access restrictions associated with changes to the configuration of MongoDB or database(s).V-265943MEDIUMThe DBMS must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance.V-265945HIGHMongoDB must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements.V-265946MEDIUMMongoDB 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-265947MEDIUMMongoDB 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-265948MEDIUMMongoDB must maintain the confidentiality and integrity of information during preparation for transmission.V-265949MEDIUMMongoDB must maintain the confidentiality and integrity of information during reception.V-265950MEDIUMWhen invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives.V-265951MEDIUMWhen updates are applied to MongoDB software, any software components that have been replaced or made unnecessary must be removed.V-265952HIGHMongoDB products must be a supported version.V-265953MEDIUMMongoDB must off-load audit data to a separate log management facility; this must be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for standalone systems.V-265954MEDIUMMongoDB 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.V-265972MEDIUMSecurity-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-265973MEDIUMMongoDB must limit the total number of concurrent connections to the database.