STIGhubSTIGhub
STIGsRMF ControlsCompare

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

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 4 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to MongoDB Enterprise Advanced 7.x Security Technical Implementation Guide

V-265949

CAT II (Medium)

MongoDB must maintain the confidentiality and integrity of information during reception.

Rule ID

SV-265949r1028633_rule

STIG

MongoDB Enterprise Advanced 7.x Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-002422

Discussion

Information can be either unintentionally or maliciously disclosed or modified during reception, including, for example, during aggregation, at protocol transformation points, and during packing/unpacking. These unauthorized disclosures or modifications compromise the confidentiality or integrity of the information. This requirement applies only to those applications that are either distributed or can allow access to data nonlocally. Use of this requirement will be limited to situations where the data owner has a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process. When receiving data, MongoDB, associated applications, and infrastructure must leverage protection mechanisms.

Check Content

If the data owner does not have a strict requirement for ensuring data integrity and confidentiality is maintained at every step of the data transfer and handling process, this is not a finding. 

If such a requirement is present, inspect the MongoDB configuration file (default location: /etc/mongod.conf) for the following entries:

net:
  tls:
    mode: requireTLS
    certificateKeyFile: <PEM File>
    CAFile: <PEM File>
    allowInvalidCertificates: false
    allowConnectionsWithoutCertificates: false
    FIPSMode: true

If net.tls.mode is not set to "requireTLS", this is a finding.

Fix Text

Stop the MongoDB instance if it is running. 

Obtain a certificate from a valid DOD certificate authority to be used for encrypted data reception. 

Modify the MongoDB configuration file to include the following TLS configuration options:

net:
  tls:
    mode: requireTLS
    certificateKeyFile: <PEM File>
    CAFile: <PEM File>
    allowInvalidCertificates: false
    allowConnectionsWithoutCertificates: false
    FIPSMode: true

Set "net.tls.mode" to the "requireTLS".
<PEM File> is the fullpathnames to the certificates used for the option.

Start/stop (restart) all mongod or mongos instances using the MongoDB configuration file (default location: /etc/mongod.conf).