| Checked | Name | Title |
|---|
| ☐ | SV-279331r1179501_rule | MongoDB must limit the total number of concurrent connections to the database. |
| ☐ | SV-279332r1179502_rule | MongoDB must integrate with an organization-level authentication/access mechanism providing account management and automation for all users, groups, roles, and any other principals. |
| ☐ | SV-279333r1179443_rule | MongoDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-279334r1179504_rule | MongoDB must provide audit record generation for DOD-defined auditable events within all DBMS/database components. |
| ☐ | SV-279336r1179505_rule | The audit information produced by MongoDB must be protected from unauthorized access, modification, and deletion. |
| ☐ | SV-279337r1179178_rule | MongoDB must protect its audit features from unauthorized access, modification, and removal. |
| ☐ | SV-279338r1179445_rule | MongoDB must limit privileges to change software modules, to include stored procedures, functions and triggers, and links to software external to MongoDB. |
| ☐ | SV-279339r1179184_rule | MongoDB software installation account must be restricted to authorized users. |
| ☐ | SV-279340r1179187_rule | MongoDB database software, including configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications. |
| ☐ | SV-279341r1179506_rule | MongoDB database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to MongoDB, etc.) must be owned by database/DBMS principals authorized for ownership. |
| ☐ | SV-279342r1179447_rule | The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to MongoDB, etc.) must be restricted to authorized users. |
| ☐ | SV-279344r1179199_rule | Unused database components, MongoDB software, and database objects must be removed. |
| ☐ | SV-279346r1179449_rule | 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. |
| ☐ | SV-279347r1179208_rule | MongoDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-279349r1179508_rule | MongoDB must, for password-based authentication, store passwords using an approved salted key derivation function, preferably using a keyed hash. |
| ☐ | SV-279350r1179454_rule | If passwords are used for authentication, MongoDB must transmit only encrypted representations of passwords. |
| ☐ | SV-279351r1179509_rule | MongoDB must enforce authorized access to all PKI private keys stored/used by the DBMS. |
| ☐ | SV-279352r1179459_rule | MongoDB must map the PKI-authenticated identity to an associated user account. |
| ☐ | SV-279353r1179226_rule | MongoDB must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
| ☐ | SV-279354r1179510_rule | MongoDB must use NIST FIPS 140-2/140-3 validated cryptographic modules for cryptographic operations. |
| ☐ | SV-279355r1179463_rule | MongoDB must separate user functionality (including user interface services) from database management functionality. |
| ☐ | SV-279358r1179465_rule | MongoDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. |
| ☐ | SV-279361r1179250_rule | MongoDB must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-279363r1179256_rule | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-279364r1179259_rule | Access to database files must be limited to relevant processes and to authorized, administrative users. |
| ☐ | SV-279365r1179467_rule | MongoDB must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-279366r1179512_rule | MongoDB and associated applications must reserve the use of dynamic code execution for situations that require it. |
| ☐ | SV-279367r1179513_rule | MongoDB must provide nonprivileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. |
| ☐ | SV-279368r1179271_rule | MongoDB must reveal detailed error messages only to the information system security officer (ISSO), information system security manager (ISSM), system administrator (SA) and database administrator (DBA). |
| ☐ | SV-279371r1179515_rule | MongoDB must associate organization-defined types of security labels having organization-defined security label values with information in storage. |
| ☐ | SV-279372r1179475_rule | MongoDB must enforce Discretionary Access Control (DAC) policies, as defined by the data owner, over defined subjects and objects. |
| ☐ | SV-279373r1179516_rule | MongoDB must prevent nonprivileged users from executing privileged functions, to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
| ☐ | SV-279375r1179292_rule | MongoDB must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-279376r1179479_rule | MongoDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75 percent of maximum audit record storage capacity. |
| ☐ | SV-279380r1179481_rule | MongoDB must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. |
| ☐ | SV-279381r1179310_rule | MongoDB must enforce access restrictions associated with changes to the configuration of MongoDB or database(s). |
| ☐ | SV-279382r1179313_rule | MongoDB must disable network functions, ports, protocols, and services deemed by the organization to be nonsecure, in accord with the Ports, Protocols, and Services Management (PPSM) guidance. |
| ☐ | SV-279383r1179483_rule | MongoDB must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. |
| ☐ | SV-279385r1179518_rule | MongoDB must use NSA-approved cryptography to protect classified information in accordance with the data owner's requirements. |
| ☐ | SV-279386r1179520_rule | MongoDB must only accept end entity certificates issued by DOD PKI or DOD-approved PKI Certification Authorities (CAs) for the establishment of all encrypted sessions. |
| ☐ | SV-279387r1179328_rule | MongoDB must implement cryptographic mechanisms to prevent unauthorized modification of organization-defined information at rest (to include, at a minimum, PII and classified information) on organization-defined information system components. |
| ☐ | SV-279389r1179334_rule | MongoDB must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-279390r1179486_rule | When invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives. |
| ☐ | SV-279391r1179488_rule | When updates are applied to MongoDB software, any software components that have been replaced or made unnecessary must be removed. |
| ☐ | SV-279392r1179521_rule | Security-relevant software updates to MongoDB must be installed within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). |
| ☐ | SV-279393r1179522_rule | MongoDB must be a version supported by the vendor. |
| ☐ | SV-279394r1179490_rule | MongoDB must off-load audit data to a separate log management facility; this shall be continuous and in near real time for systems with a network connection to the storage facility and weekly or more often for stand-alone systems. |
| ☐ | SV-279395r1179492_rule | MongoDB must be configured in accordance with the security configuration settings based on DOD security configuration and implementation guidance, including STIGs, NSA configuration guides, CTOs, DTMs, and IAVMs. |
| ☐ | SV-279398r1179494_rule | MongoDB must prevent the installation of organization-defined software and firmware components without verification that the component has been digitally signed using a certificate recognized and approved by the organization. |
| ☐ | SV-279399r1179524_rule | MongoDB must require users to be individually authenticated before granting access to the shared accounts or resources. |
| ☐ | SV-279409r1179526_rule | MongoDB must, for public key-based authentication, implement a local cache of revocation data to support path discovery and validation. |
| ☐ | SV-279411r1179400_rule | MongoDB must include only approved trust anchors in trust stores or certificate stores managed by the organization. |
| ☐ | SV-279412r1179403_rule | MongoDB must provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store. |
| ☐ | SV-281700r1179499_rule | MongoDB must terminate a user session after organization-defined conditions or trigger events requiring session disconnect via a scheduled script. |
| ☐ | SV-282943r1179530_rule | MongoDB must be configured to restrict the use of administrator access to authorized IP addresses. |
STIGQter: STIG Summary: