<Past |
Future> |
10.0.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
10.1.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
10.2.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
10.3.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
10.4.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
10.5.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
10.6.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
10.7.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
10.8.x |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Prohibited |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
10.9.x |
Approved w/Constraints [4, 11, 14, 15, 16] |
Approved w/Constraints [4, 11, 14, 15, 17] |
Approved w/Constraints [4, 11, 14, 15, 17] |
DIVEST [4, 14, 15, 17, 18] |
DIVEST [14, 17, 18, 19, 20] |
Approved w/Constraints [14, 17, 18, 19, 20] |
Approved w/Constraints [14, 17, 18, 19, 20] |
Approved w/Constraints [14, 17, 18, 19, 20] |
Approved w/Constraints [14, 19, 20, 21, 22, 23, 24] |
Approved w/Constraints [14, 19, 20, 22, 23, 24, 25] |
Approved w/Constraints [14, 19, 20, 22, 23, 24, 25] |
Authorized w/ Constraints [14, 19, 20, 22, 23, 24, 26, 27] |
11.0.x |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 14, 15, 17, 18] |
Approved w/Constraints [14, 17, 18, 19, 20] |
Approved w/Constraints [14, 17, 18, 19, 20] |
Approved w/Constraints [14, 17, 18, 19, 20] |
DIVEST [14, 17, 18, 19, 20] |
DIVEST [14, 19, 20, 21, 22, 23, 24] |
DIVEST [14, 19, 20, 22, 23, 24, 25] |
DIVEST [14, 19, 20, 22, 23, 24, 25] |
Authorized w/ Constraints (DIVEST) [14, 19, 20, 22, 23, 24, 26, 27] |
11.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [14, 17, 18, 19, 20] |
Approved w/Constraints [14, 17, 18, 19, 20] |
Approved w/Constraints [14, 17, 18, 19, 20] |
DIVEST [14, 19, 20, 21, 22, 23, 24] |
DIVEST [14, 19, 20, 22, 23, 24, 25] |
DIVEST [14, 19, 20, 22, 23, 24, 25] |
Authorized w/ Constraints (DIVEST) [14, 19, 20, 22, 23, 24, 26, 27] |
11.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [14, 19, 20, 21, 22, 23, 24] |
DIVEST [14, 19, 20, 22, 23, 24, 25] |
DIVEST [14, 19, 20, 22, 23, 24, 25] |
Authorized w/ Constraints (DIVEST) [14, 19, 20, 22, 23, 24, 26, 27] |
11.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [14, 19, 20, 22, 23, 24, 25] |
Approved w/Constraints [14, 19, 20, 22, 23, 24, 25] |
Authorized w/ Constraints (DIVEST) [14, 19, 20, 22, 23, 24, 26, 27] |
11.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints [14, 19, 20, 22, 23, 24, 26, 27] |
Note: |
At the time of writing, version 11.4.0 is the most current version, released 11/07/2024. |
| | [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. | | [11] | Users must ensure that Microsoft .NET Framework and Microsoft Internet Explorer (IE) are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’). | | [14] | 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. | | [15] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an authorized VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | [16] | 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). | | [17] | 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). | | [18] | Microsoft Internet Explorer, a dependency of this technology, is in End-of-Life status and must no longer be used. | | [19] | 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. | | [20] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an authorized VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. 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 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517
and VA Directive 6513. The local ISSO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place. | | [21] | Users must ensure that Microsoft Edge is implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [22] | 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. | | [23] | 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). | | [24] | 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. | | [25] | Users must ensure that Microsoft Edge is implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize Hyper-V Server (Stand-alone Edition), as it is at the time of writing, unapproved in the TRM. | | [26] | Users must ensure that Microsoft Edge is implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize Hyper-V Server (Stand-alone Edition), as it, at the time of writing, requires a POA&M. | | [27] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. |
|