Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

MongoDB Enterprise Advanced

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	MongoDB is a scalable, open source NoSQL database written in C++. MongoDB is available in a free Community Edition and an Enterprise Advanced Edition. Please note this technology page might not be accessible within the VA firewall.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.5
Decision Date:	05/06/2024 at 17:36:24 UTC
Aliases:	MongoDB Enterprise Advanced
Introduced By:	TRM Request
Vendor Name:	MongoDB Inc.

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2.4.x	03/31/2013	03/31/2016	03/31/2016
2.6.x	04/30/2014	10/30/2016	10/30/2016
3.0.x	03/31/2015	02/28/2018	02/28/2018
3.2.x	12/31/2015	09/30/2018	09/30/2018
3.4.x (Com Ed)
3.4.x	11/01/2016	01/31/2020	01/31/2020
3.6.x	11/01/2017	04/30/2021	04/30/2021
4.0.x	08/06/2018	04/30/2022	04/30/2022
4.2.x	08/01/2019	04/30/2023
4.4.x	07/01/2020	02/28/2024
5.0.x	07/13/2021	10/30/2024
6.0.x	09/28/2022	07/31/2025
7.0.x	09/05/2023

Current Decision Matrix (05/02/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2021

CY2022

CY2023

Future>

Release

2.4.x

Unapproved

2.6.x

Unapproved

3.0.x

Unapproved

3.2.x

Unapproved

3.4.x (Com Ed)

Unapproved

3.4.x

Unapproved

3.6.x

Divest
[2, 3, 13, 14, 15]

Unapproved

4.0.x

Approved w/Constraints
[2, 3, 13, 14, 15]

Approved w/Constraints
[2, 14, 15, 16, 17]

Approved w/Constraints
[16, 18, 19, 20, 21]

Divest
[16, 18, 19, 20, 21, 22]

Divest
[16, 18, 19, 21, 22, 23]

4.2.x

Approved w/Constraints
[2, 3, 13, 14, 15]

Approved w/Constraints
[2, 14, 15, 16, 17]

Approved w/Constraints
[16, 18, 19, 20, 21]

Divest
[16, 18, 19, 20, 21, 22]

Divest
[16, 18, 19, 21, 22, 23]

4.4.x

Approved w/Constraints
[2, 3, 13, 14, 15]

Approved w/Constraints
[2, 14, 15, 16, 17]

Approved w/Constraints
[16, 18, 19, 20, 21]

Approved w/Constraints
[16, 18, 19, 20, 21, 22]

Approved w/Constraints
[16, 18, 19, 21, 22, 23]

5.0.x

Unapproved

Approved w/Constraints
[16, 18, 19, 20, 21, 22]

Approved w/Constraints
[16, 18, 19, 21, 22, 23]

6.0.x

Unapproved

Approved w/Constraints
[16, 18, 19, 20, 21, 22]

Approved w/Constraints
[16, 18, 19, 21, 22, 23]

7.0.x

Unapproved

Decision Constraints


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

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.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
No components have been identified for this entry.


Information Management Technologies Data Management	Non-relational Database

- The information contained on this page is accurate as of the Decision Date (05/06/2024 at 17:36:24 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/02/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/02/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES