STIGhubSTIGhub
STIGsRMF ControlsCompare
STIGhub— A free STIG search and compliance tool·STIGs updated 3 days ago
Powered by Pylon·Privacy·Terms·© 2026 Beacon Cloud Solutions, Inc.
← Back to MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide

V-279346

CAT II (Medium)

MongoDB must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.

Rule ID

SV-279346r1179449_rule

STIG

MongoDB Enterprise Advanced 8.x Security Technical Implementation Guide

Version

V1R1

CCIs

CCI-000382

Discussion

To prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical ports/protocols/services on information systems. Applications are capable of providing a wide variety of functions and services. Some of the functions and services provided by default may not be necessary to support essential organizational operations. Additionally, it is sometimes convenient to provide multiple services from a single component (e.g., email and web services); however, doing so increases risk over limiting the services provided by any one component. To support the requirements and principles of least functionality, the application must support the organizational requirements providing only essential capabilities and limiting the use of ports, protocols, and/or services to only those required, authorized, and approved to conduct official business or to address authorized quality of life issues. Database Management Systems using ports, protocols, and services deemed unsafe are open to attack through those ports, protocols, and services. This can allow unauthorized access to the database and through the database to other components of the information system.

Check Content

Check the MongoDB configuration file (default location /etc/mongod.conf) to verify the following entry:

net:
  port: 27017

If the port listed is not authorized, this is a finding.

Verify only TLS 1.2+ is being used. If the following entry is not in the configuration file, this is a finding.

net:
  tls:
    mode: requireTLS
    disabledProtocols: TLS1_0,TLS1_1

Verify the binding of IP addresses does not include "0.0.0.0" or ":0":

net:
  bindIp: 127.0.0.1,<specific-ip-addresses>

If the bindIp contains "0.0.0.0" or "::0", this is a finding.

Fix Text

Check the MongoDB configuration file (default location /etc/mongod.conf):

Ensure the following section exists and set the port in the to an allowed port:

net:
  port: 27017

Ensure that TLS 1.2+ is being used by adding the following entry into the configuration file.

net:
  tls:
    mode: requireTLS
    disabledProtocols: TLS1_0,TLS1_1

Ensure the following section exists in the configuration file and that it does not contain wildcard binding (occurrences of "0.0.0.0" or "::0" or equivalents).

net:
  bindIp: 127.0.0.1,<specific-ip-addresses>