Rotate your device back to portrait to use STIG Vault.
The MongoDB Enterprise Advanced 4.x Security Technical Implementation Guide (V1 R4) has 52 STIG checks. New to STIG checklists? Read What is a STIG checklist?, CKL vs CKLB, and STIG vs SCAP benchmark.
Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Rule Text
Discussion Text
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.
Mongo can limit the total number of connections.
Verify that the MongoDB configuration file (default location: /etc/mongod.conf) contains the following:
net:
maxIncomingConnections: %int%
If this parameter is not present, or the OS is not utilized to limit connections, this is a finding.
MongoDB can limit the total number of connections served by mongod process by setting the following in the MongoDB configuration file (default location: /etc/mongod.conf)
net:
maxIncomingConnections: %int%
See the following documentation:
https://docs.mongodb.com/v4.4/reference/configuration-options/
Products outside of MongoDB can be used to monitor database sessions and limit the maximum number of connections that can be made.
Alternatively most UNIX-like operating systems, including Linux and macOS, provide ways to limit and control the usage of system resources such as threads, files, and network connections on a per-process and per-user basis.
These ulimits prevent single users from using too many system resources.
The following is the MongoDB documentation regarding these user limits: https://docs.mongodb.com/v4.4/reference/ulimit/