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

Version

V2R3

Benchmark ID

MongoDB_3-x_STIG

Total Checks

44

Tags

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

V-221158HIGHMongoDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals.V-221159HIGHMongoDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies.V-221160MEDIUMMongoDB must provide audit record generation for DoD-defined auditable events within all DBMS/database components.V-221161MEDIUMThe audit information produced by MongoDB must be protected from unauthorized read access.V-221162MEDIUMMongoDB must protect its audit features from unauthorized access.V-221163HIGHMongoDB software installation account must be restricted to authorized users.V-221164MEDIUMDatabase software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.V-221165MEDIUMThe 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-221166MEDIUMUnused database components, DBMS software, and database objects must be removed.V-221167MEDIUMUnused database components that are integrated in MongoDB and cannot be uninstalled must be disabled.V-221168MEDIUMMongoDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).V-221169HIGHIf DBMS authentication using passwords is employed, MongoDB must enforce the DoD standards for password complexity and lifetime.V-221170HIGHIf passwords are used for authentication, MongoDB must store only hashed, salted representations of passwords.V-221171HIGHIf passwords are used for authentication, MongoDB must transmit only encrypted representations of passwords.V-221172HIGHMongoDB must enforce authorized access to all PKI private keys stored/utilized by MongoDB.V-221173MEDIUMMongoDB must map the PKI-authenticated identity to an associated user account.V-221174HIGHMongoDB must use NIST FIPS 140-2-validated cryptographic modules for cryptographic operations.V-221175MEDIUMMongoDB must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).V-221176MEDIUMMongoDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.V-221177MEDIUMMongoDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.V-221178HIGHMongoDB must protect the confidentiality and integrity of all information at rest.V-221179MEDIUMDatabase contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy.V-221180MEDIUMMongoDB must prevent unauthorized and unintended information transfer via shared system resources.V-221181MEDIUMMongoDB must check the validity of all data inputs except those specifically identified by the organization.V-221182MEDIUMMongoDB and associated applications must reserve the use of dynamic code execution for situations that require it.V-221183MEDIUMMongoDB 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-221184MEDIUMMongoDB must reveal detailed error messages only to the ISSO, ISSM, SA, and DBA.V-221185MEDIUMMongoDB must associate organization-defined types of security labels having organization-defined security label values with information in storage.V-221186MEDIUMMongoDB must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects.V-221188MEDIUMMongoDB must utilize centralized management of the content captured in audit records generated by all components of MongoDB.V-221189MEDIUMMongoDB must allocate audit record storage capacity in accordance with site audit record storage requirements.V-221190MEDIUMMongoDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity.V-221191MEDIUMMongoDB must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status.V-221192MEDIUMMongoDB must enforce access restrictions associated with changes to the configuration of MongoDB or database(s).V-221193MEDIUMMongoDB must require users to reauthenticate when organization-defined circumstances or situations require reauthentication.V-221194MEDIUMMongoDB must prohibit the use of cached authenticators after an organization-defined time period.V-221195MEDIUMMongoDB 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-221196MEDIUMMongoDB 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-221197MEDIUMMongoDB must maintain the confidentiality and integrity of information during preparation for transmission.V-221198MEDIUMMongoDB must maintain the confidentiality and integrity of information during reception.V-221199MEDIUMWhen invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives.V-221200HIGHMongoDB must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.V-221201MEDIUMMongoDB 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-265875HIGHMongoDB products must be a version supported by the vendor.