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

V-221176

CAT II (Medium)

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

Rule ID

SV-221176r961119_rule

STIG

MongoDB Enterprise Advanced 3.x Security Technical Implementation Guide

Version

V2R3

CCIs

CCI-001188

Discussion

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 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.

Check Content

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

The following should be set:

net:
ssl:
mode: requireSSL

If this is not found in the MongoDB configuration file, this is a finding.

Fix Text

Follow the documentation guide at https://docs.mongodb.com/v3.4/tutorial/configure-ssl/.

Stop/start (restart) and mongod or mongos using the MongoDB configuration file.