<Past |
Future> |
7.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.1.x |
Divest [1, 3, 7, 8] |
Divest [1, 3, 7, 8] |
Divest [1, 3, 7, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
8.2.x |
Divest [1, 3, 7, 8] |
Divest [1, 3, 7, 8] |
Divest [1, 3, 7, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.0.x |
Divest [1, 3, 7, 8] |
Divest [1, 3, 7, 8] |
Divest [1, 3, 7, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.1.x |
Divest [1, 3, 7, 8] |
Divest [1, 3, 7, 8] |
Divest [1, 3, 7, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
9.2.x |
Approved w/Constraints [1, 3, 7, 8] |
Approved w/Constraints [1, 3, 7, 8] |
Approved w/Constraints [1, 3, 7, 9] |
Approved w/Constraints [1, 3, 7, 9] |
Divest [1, 3, 9, 10, 11] |
Divest [1, 3, 10, 11, 12] |
Divest [1, 3, 10, 11, 12] |
Divest [1, 3, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.0.x |
Approved w/Constraints [1, 3, 7, 8] |
Approved w/Constraints [1, 3, 7, 8] |
Approved w/Constraints [1, 3, 7, 9] |
Approved w/Constraints [1, 3, 7, 9] |
Divest [1, 3, 9, 10, 11] |
Divest [1, 3, 10, 11, 12] |
Divest [1, 3, 10, 11, 12] |
Divest [1, 3, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [1, 3, 9, 10, 11] |
Divest [1, 3, 10, 11, 12] |
Divest [1, 3, 10, 11, 12] |
Divest [1, 3, 10, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 9, 10, 11] |
Approved w/Constraints [1, 3, 10, 11, 12] |
Approved w/Constraints [1, 3, 10, 11, 12] |
Approved w/Constraints [1, 3, 10, 11, 12] |
Divest [12, 13, 14, 15, 16] |
Divest [12, 13, 14, 15, 16] |
Divest [12, 13, 14, 15, 16] |
Divest [12, 13, 15, 16, 17] |
11.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 9, 10, 11] |
Approved w/Constraints [1, 3, 10, 11, 12] |
Approved w/Constraints [1, 3, 10, 11, 12] |
Approved w/Constraints [1, 3, 10, 11, 12] |
Divest [12, 13, 14, 15, 16] |
Divest [12, 13, 14, 15, 16] |
Divest [12, 13, 14, 15, 16] |
Divest [12, 13, 15, 16, 17] |
11.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Divest [12, 13, 14, 15, 16] |
Divest [12, 13, 15, 16, 17] |
11.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 14, 15, 16] |
Divest [12, 13, 14, 15, 16] |
Divest [12, 13, 15, 16, 17] |
12.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [12, 13, 14, 15, 16] |
Approved w/Constraints [12, 13, 15, 16, 17] |
| | [1] | 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. | | [2] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [3] | 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. | | [4] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that Microsoft Internet Explorer (IE) and VMware vSphere are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest version of a TRM approved Java Environment.
Users must ensure that Microsoft Internet Explorer (IE) and VMware vSphere are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [8] | 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). | | [9] | 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). | | [10] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that Java Runtime Environment (JRE) - Oracle, and VMware vSphere are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users should divest use of Microsoft Internet Explorer (IE) with this technology, it is in a divested state at the time, and is not required to use the technology.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. | | [11] | 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. | | [12] | 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). | | [13] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
Users must ensure that Oracle, and VMware vSphere are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users should divest use of Microsoft Internet Explorer (IE) with this technology, it is in End-of-Life status at the time, and is not required to use the technology.
This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [15] | 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. | | [16] | 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. | | [17] | 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 12.2.0 is the most current version, updated 07/23/2023. |