| Checked | Name | Title |
|---|
| ☐ | SV-96557r1_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-96559r1_rule | MongoDB must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-96561r1_rule | MongoDB must provide audit record generation for DoD-defined auditable events within all DBMS/database components. |
| ☐ | SV-96563r1_rule | The audit information produced by MongoDB must be protected from unauthorized read access. |
| ☐ | SV-96565r1_rule | MongoDB must protect its audit features from unauthorized access. |
| ☐ | SV-96567r1_rule | MongoDB software installation account must be restricted to authorized users. |
| ☐ | SV-96569r1_rule | Database software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications. |
| ☐ | SV-96571r1_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-96573r1_rule | Unused database components, DBMS software, and database objects must be removed. |
| ☐ | SV-96575r1_rule | Unused database components that are integrated in MongoDB and cannot be uninstalled must be disabled. |
| ☐ | SV-96577r1_rule | MongoDB must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-96579r1_rule | If DBMS authentication, using passwords, is employed, MongoDB must enforce the DoD standards for password complexity and lifetime. |
| ☐ | SV-96581r1_rule | If passwords are used for authentication, MongoDB must store only hashed, salted representations of passwords. |
| ☐ | SV-96583r1_rule | If passwords are used for authentication, MongoDB must transmit only encrypted representations of passwords. |
| ☐ | SV-96585r2_rule | MongoDB must enforce authorized access to all PKI private keys stored/utilized by MongoDB. |
| ☐ | SV-96587r1_rule | MongoDB must map the PKI-authenticated identity to an associated user account. |
| ☐ | SV-96589r1_rule | MongoDB must use NIST FIPS 140-2-validated cryptographic modules for cryptographic operations. |
| ☐ | SV-96591r1_rule | MongoDB must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). |
| ☐ | SV-96593r1_rule | MongoDB must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values. |
| ☐ | SV-96595r1_rule | MongoDB must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |
| ☐ | SV-96597r1_rule | MongoDB must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-96599r1_rule | Database contents must be protected from unauthorized and unintended information transfer by enforcement of a data-transfer policy. |
| ☐ | SV-96601r1_rule | MongoDB must prevent unauthorized and unintended information transfer via shared system resources. |
| ☐ | SV-96603r1_rule | MongoDB must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-96605r1_rule | MongoDB and associated applications must reserve the use of dynamic code execution for situations that require it. |
| ☐ | SV-96607r1_rule | MongoDB must provide non-privileged users with error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. |
| ☐ | SV-96609r1_rule | MongoDB must reveal detailed error messages only to the ISSO, ISSM, SA, and DBA. |
| ☐ | SV-96611r1_rule | MongoDB must associate organization-defined types of security labels having organization-defined security label values with information in storage. |
| ☐ | SV-96613r1_rule | MongoDB must enforce discretionary access control policies, as defined by the data owner, over defined subjects and objects. |
| ☐ | SV-96615r1_rule | MongoDB must provide the means for individuals in authorized roles to change the auditing to be performed on all application components, based on all selectable event criteria within organization-defined time thresholds. |
| ☐ | SV-96617r1_rule | MongoDB must utilize centralized management of the content captured in audit records generated by all components of MongoDB. |
| ☐ | SV-96619r1_rule | MongoDB must allocate audit record storage capacity in accordance with site audit record storage requirements. |
| ☐ | SV-96621r1_rule | MongoDB must provide a warning to appropriate support staff when allocated audit record storage volume reaches 75% of maximum audit record storage capacity. |
| ☐ | SV-96623r1_rule | MongoDB must prohibit user installation of logic modules (stored procedures, functions, triggers, views, etc.) without explicit privileged status. |
| ☐ | SV-96625r1_rule | MongoDB must enforce access restrictions associated with changes to the configuration of MongoDB or database(s). |
| ☐ | SV-96627r1_rule | MongoDB must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. |
| ☐ | SV-96629r1_rule | MongoDB must prohibit the use of cached authenticators after an organization-defined time period. |
| ☐ | SV-96631r1_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-96633r1_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-96635r1_rule | MongoDB must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-96637r1_rule | MongoDB must maintain the confidentiality and integrity of information during reception. |
| ☐ | SV-96639r1_rule | When invalid inputs are received, MongoDB must behave in a predictable and documented manner that reflects organizational and system objectives. |
| ☐ | SV-96641r1_rule | MongoDB must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
| ☐ | SV-96643r1_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. |
STIGQter: STIG Summary: