<Past |
Future> |
2.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.4.x (Com Ed) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.0.x |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
6.0.x |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
7.0.x |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
| | [1] | Configuration and deployment standards for MongoDB on Red Hat Enterprise Linux Server images must be followed and adhered to unless an appropriate waiver is granted. As of this writing, VA has not approved MongoDB for use on Windows Server. Detailed baseline information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx | | [2] | Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations. | | [3] | Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities. | | [4] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [5] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [6] | Configuration and deployment standards for MongoDB on Red Hat Enterprise Linux Server images must be followed and adhered to unless an appropriate waiver is granted. As of this writing, VA has not approved MongoDB for use on Windows Server. Detailed baseline information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Version 3.0 is the only version with a baseline listed on the Baseline Configuration Management site. Newer versions (3.2 and 3.4) must not be approved until a baseline is updated and/or created for them. | | [7] | Configuration and deployment standards for MongoDB on Red Hat Enterprise Linux Server images must be followed and adhered to unless an appropriate waiver is granted. As of this writing, VA has not approved MongoDB for use on Windows Server. Detailed baseline information can be found at the following location: https://vaww.sde.portal.va.gov/svcs/sma/BCM/SitePages/Home.aspx
Version 3.0 is the only version with a baseline listed on the Baseline Configuration Management site. Newer versions (3.2 and 3.4) must not be approved until a baseline is updated and/or created for them. | | [8] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [9] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [10] | Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information. | | [11] | Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.
MongoDB Enterprise Advanced is the only Approved with Constraints edition at this time. | | [12] | Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.
MongoDB Enterprise Advanced is the only Approved with Constraints edition at this time.
Per the Initial Product Review, users must abide by the following constraints:
- System owners and developers must ensure FIPS mode is enabled. This is accomplished by performing a thorough end-to-end encryption test to ensure VA sensitive data are secured and protected at rest and in transit. In addition to employing FIPS encryption on database management systems (DBMS), the following access enforcement and physical controls must also be implemented as mandated by VA Chief Information Security Officer (CISO). This involved restricting, monitoring and auditing logical access to the information systems, hard drives, access logs and DBMS
- Ensure that the HTTP status interface, the REST API, and the JSON API are all disabled during testing and prior to deployment in production environment. In the event the HTTP status interface is required to be enabled, system owners should only allow trusted clients to access the port.
- Ensure that MongoDB programs bind to the private or internal network interface and the programs should only be accessible on trusted networks. In addition, only allow traffic from trusted sources to reach mongod and mongos instances and that both instances can only connect to trusted outputs.
- Deploy MongoDB in a secure enclave within the VA internal network and configure firewall to limit incoming traffic on a specific port to specific systems.
- Employ virtual private networks (VPN) to provide a secure tunnel for all connections associated with MongoDB and to ensure access control for all clients connecting to MongoDB instances.
- Disable all server-side execution of JavaScript, by passing the --noscripting option on the command line. It is worth noting that MongoDB enables input validation by default through the wireObjectCheck setting to make sure all documents stored by the mongod instance are valid BSON.
- Hardening of the MongoDB deployment will be required before it can move to the VA production environment. After hardening, the application should be tested within a VA-owned lab environment to ensure that it complies with the organization’s functional and security requirements. System owners and developers should leverage available security guidance and best practices such as the MongoDB Security Guide and DISA STIG (See attached DISA documentation). In addition, the MongoDB Security Tutorials contain valuable instructions for utilizing the MongoDB security features which includes enabling access control and authentication mechanisms supported by MongoDB. Additionally, managing users and configuring auditing of database system should also be considered.
| | [13] | Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.
MongoDB Enterprise Advanced is the only Approved with Constraints edition at this time.
Per the Initial Product Review, users must abide by the following constraints:
- System owners and developers must ensure FIPS mode is enabled. This is accomplished by performing a thorough end-to-end encryption test to ensure VA sensitive data are secured and protected at rest and in transit. In addition to employing FIPS encryption on database management systems (DBMS), the following access enforcement and physical controls must also be implemented as mandated by VA Chief Information Security Officer (CISO). This involved restricting, monitoring and auditing logical access to the information systems, hard drives, access logs and DBMS
- Ensure that the HTTP status interface, the REST API, and the JSON API are all disabled during testing and prior to deployment in production environment. In the event the HTTP status interface is required to be enabled, system owners should only allow trusted clients to access the port.
- Ensure that MongoDB programs bind to the private or internal network interface and the programs should only be accessible on trusted networks. In addition, only allow traffic from trusted sources to reach mongod and mongos instances and that both instances can only connect to trusted outputs.
- Deploy MongoDB in a secure enclave within the VA internal network and configure firewall to limit incoming traffic on a specific port to specific systems.
- Employ virtual private networks (VPN) to provide a secure tunnel for all connections associated with MongoDB and to ensure access control for all clients connecting to MongoDB instances.
- Disable all server-side execution of JavaScript, by passing the --noscripting option on the command line. It is worth noting that MongoDB enables input validation by default through the wireObjectCheck setting to make sure all documents stored by the mongod instance are valid BSON.
- Hardening of the MongoDB deployment will be required before it can move to the VA production environment. After hardening, the application should be tested within a VA-owned lab environment to ensure that it complies with the organization’s functional and security requirements. System owners and developers should leverage available security guidance and best practices such as the MongoDB Security Guide and DISA STIG (See attached DISA documentation). In addition, the MongoDB Security Tutorials contain valuable instructions for utilizing the MongoDB security features which includes enabling access control and authentication mechanisms supported by MongoDB. Additionally, managing users and configuring auditing of database system should also be considered.
| | [14] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [15] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [16] | Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.
| | [17] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities. | | [18] | Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities. | | [19] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). | | [20] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [21] | Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations. | | [22] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. | | [23] | Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500. | | [24] | Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes. | | [25] | Configuration baseline and deployment standards for this technology that are maintained by Infrastructure Operations in ITOPS must be followed and adhered to unless an appropriate waiver is granted. See the reference section for more information.
Users must not utilize Vormetric Data Security Platform, as it is at the time of writing, unapproved in the TRM. |
|
Note: |
At the time of writing, version 7.0.1 is the most current version, released 09/05/2023.
A baseline configuration of this technology was developed by the BCM team. At the time of writing, the latest baselined version is 7.x. |