OpenControls Logo

STIG Viewer

STIGViewer Support

MongoDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-265925MD7X-00-004900SV-265925r1043181_ruleCCI-001188medium
Description
One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2 or 140-3 approved random number generator. However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking. Therefore, other techniques are acceptable, provided they are demonstrated to be effective.
STIGDate
MongoDB Enterprise Advanced 7.x Security Technical Implementation Guide2026-05-23

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

NET-09.2Unique System-Generated Session Identifiers
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (23) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-2(4)Automated Audit Actions
1.00
AC-3Access Enforcement
1.00
AC-4Information Flow Enforcement
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-12Audit Record Generation
1.00
AU-3Content of Audit Records
1.00
CM-5(1)Automated Access Enforcement and Audit Records
1.00
CM-7Least Functionality
1.00
IA-2(8)Access to Accounts — Replay Resistant
1.00

+13 more (top 10 by confidence shown)

CCI1 mapping
CCI-001188
1.00

Details

Check Text (C-265925r1043181_chk)

Check the MongoDB configuration file (default location: /etc/mongod.conf). The following option must be present ( "net.tls.mode") and set to "requireTLS": net: tls: mode: requireTLS If this is not found in the MongoDB configuration file, this is a finding.

Fix Text (F-69747r1028560_fix)

Edit the MongoDB configuration file to ensure the "net.tls.mode" option is included and set to the value "requireTLS" as shown below: net: tls: mode: requireTLS Restart the MongoDB service from the OS $ sudo systemctl restart mongod Further documentation is here: https://www.mongodb.com/docs/v7.0/tutorial/configure-ssl/