<Past |
Future> |
0.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
0.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.9.x |
DIVEST [12, 13, 14, 15] |
DIVEST [12, 13, 14, 15] |
DIVEST [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.10.x |
DIVEST [12, 13, 14, 15] |
DIVEST [12, 13, 14, 15] |
DIVEST [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.11.x |
DIVEST [12, 13, 14, 15] |
DIVEST [12, 13, 14, 15] |
DIVEST [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.12.x |
DIVEST [12, 13, 14, 15] |
DIVEST [12, 13, 14, 15] |
DIVEST [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.13.x |
Approved w/Constraints [12, 13, 14, 15] |
Approved w/Constraints [12, 13, 14, 15] |
DIVEST [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.14.x |
Approved w/Constraints [12, 13, 14, 15] |
Approved w/Constraints [12, 13, 14, 15] |
DIVEST [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.15.x |
Approved w/Constraints [12, 13, 14, 15] |
Approved w/Constraints [12, 13, 14, 15] |
Approved w/Constraints [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST) [12, 13, 15, 16, 17] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.16.x |
Approved w/Constraints [12, 13, 14, 15] |
Approved w/Constraints [12, 13, 14, 15] |
Approved w/Constraints [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST) [12, 13, 15, 16, 17] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.17.x |
Unapproved |
Unapproved |
Approved w/Constraints [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST) [12, 13, 15, 16, 17] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.18.x |
Unapproved |
Unapproved |
Approved w/Constraints [12, 13, 15, 16, 17] |
Approved w/Constraints [12, 13, 15, 16, 17] |
Authorized w/ Constraints [12, 13, 15, 16, 17] |
Approved w/Constraints [12, 13, 15, 16, 17] |
Approved w/Constraints [12, 13, 15, 16, 17] |
Approved w/Constraints [12, 13, 15, 16, 17] |
Authorized w/ Constraints [12, 13, 15, 16, 17] |
Authorized w/ Constraints [12, 13, 15, 16, 17] |
Authorized w/ Constraints [12, 13, 15, 16, 17] |
Authorized w/ Constraints [12, 13, 15, 16, 17] |
1.19.x |
Unapproved |
Unapproved |
Approved w/Constraints [12, 13, 15, 16, 17] |
Approved w/Constraints [12, 13, 15, 16, 17] |
Authorized w/ Constraints (DIVEST) [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.20.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [12, 13, 15, 16, 17] |
Authorized w/ Constraints [12, 13, 15, 16, 17] |
Approved w/Constraints [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
DIVEST [12, 13, 15, 16, 17] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| | [1] | 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. | | [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 authorized and the user should take the proper steps to decline those installations. | | [3] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data.
- Administrators must ensure they are using the version 1.6.x or higher. Current version is 1.8.3
- Caution must be exercised in implementing any open source software in the VA network environment and should include a formal risk assessment.
- Administrators need to ensure Consul is deployed in Secure Configuration Mode.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
- Consul Kubernetes integration should not be used without a Kubernetes baseline configuration. Specific hardening guidance regarding the secure implementation of Consul should be documented. Please reference the TRM for the approval status and the Baseline Configuration Management website for more information.
| | [4] | 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. | | [5] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [6] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [7] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [8] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data.
- Administrators must ensure they are using the version 1.6.x or higher. Current version is 1.8.3
- Caution must be exercised in implementing any open source software in the VA network environment and should include a formal risk assessment.
- Administrators need to ensure Consul is deployed in Secure Configuration Mode.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
- Consul Kubernetes integration should not be used without a Kubernetes baseline configuration. Specific hardening guidance regarding the secure implementation of Consul should be documented. Please reference the TRM for the approval status and the Baseline Configuration Management website for more information.
Users must ensure that Google Chrome, Firefox, and Microsoft Internet Explorer (IE) are implemented with VA-authorized baselines.
Users must Divest the use of Internet Explorer with this technology. Other authorized internet browsers are available. See Category Tab for details.
Users must not utilize Kubernetes as it is, at the time of writing, unapproved in the TRM.
| | [9] | This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product. | | [10] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [11] | Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data.
- Caution must be exercised in implementing any open source software in the VA network environment and should include a formal risk assessment.
- Administrators need to ensure Consul is deployed in Secure Configuration Mode.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
- Consul Kubernetes integration should not be used without a Kubernetes baseline configuration. Specific hardening guidance regarding the secure implementation of Consul should be documented. Please reference the TRM for the approval status and the Baseline Configuration Management website for more information.
This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations.
Users must utilize authorized internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. | | [12] | 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 authorized and the user should take the proper steps to decline those installations. | | [13] | 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. | | [14] | Users must ensure that Kubernetes, Firefox, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations.
Per the Initial Product Review, users must abide by the following constraints:
- Ensure use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data.
- Caution must be exercised in implementing any open source software in the VA network environment and should include a formal risk assessment.
- Administrators need to ensure Consul is deployed in Secure Configuration Mode.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
- Consul Kubernetes integration should not be used without a Kubernetes baseline configuration. Specific hardening guidance regarding the secure implementation of Consul should be documented. Please reference the TRM for the approval status and the Baseline Configuration Management website for more information.
| | [15] | Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [16] | Users must ensure that Kubernetes, Firefox, and Google Chrome are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations.
Per the Initial Product Review, users must abide by the following constraints:
- Consul will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information.
- The use of open-source products, lacking any vendor support, hosting potentially critical VA production systems may pose severe security risks to the VA. Relying on vendor support may result in slow response times and non-timely patches. Users should check with their supervisor, ISSO or local OIT representative for permission to download and use this software.
- Administrators need to ensure Consul is deployed in Secure Configuration Mode.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Business Integration and Outcomes Service (BIOS) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC.
- Consul Kubernetes integration should not be used without a Kubernetes baseline configuration. Specific hardening guidance regarding the secure implementation of Consul should be documented. Please reference the TRM for the approval status and the Baseline Configuration Management website for more information.
- Ensure that the latest stable version of Consul is used. Additionally, Consul must be added to the list of applications for continuous monitoring for published vulnerabilities, updates, and patches. ISSO’s and administrators must monitor the National Vulnerability Database for any new security vulnerabilities.
| | [17] | 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. |
|
Note: |
At the time of writing, version 1.20.1 is the most current version, released 10/29/2024. |