<Past |
Future> |
3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.5 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.7 |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.8.x |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.9.x |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.10.x |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.11.x |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.12.x |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.13.x |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.14.x |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.15.x |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Divest [8, 9, 12, 13, 14] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
5.16.x |
Approved w/Constraints [8, 9, 12, 13, 14] |
Approved w/Constraints [8, 9, 12, 13, 14] |
Approved w/Constraints [8, 9, 12, 13, 14] |
Approved w/Constraints [8, 9, 12, 13, 15] |
Divest [12, 13, 15, 16, 17] |
Divest [12, 13, 15, 16, 17] |
Divest [12, 13, 15, 16, 17] |
Divest [12, 13, 15, 16, 17] |
Divest [12, 13, 15, 16, 17] |
Divest [12, 13, 15, 16, 17] |
Unapproved |
Unapproved |
6.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved 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] |
Approved 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] |
| | [1] | 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). | | [2] | 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. | | [3] | 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). | | [4] | Users must ensure that VMware vSphere is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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] | 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] | Users must ensure that VMware vSphere, Firefox, and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)
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 not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize OpenStack and Open Secure Socket Layer (OpenSSL), as they are at the time of writing, unapproved in the TRM.
Users must not utilize Hyper-V Server, as it is at the time of writing, prohibited in the TRM. | | [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 VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [10] | 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] | 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. | | [12] | 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. | | [13] | 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. | | [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] | 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. | | [16] | Users must ensure that VMware vSphere, Firefox, and Google Chrome are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)
The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is unapproved for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)
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 not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.
Users must not utilize OpenStack, Hyper-v Server and Open Secure Socket Layer (OpenSSL), as they are at the time of writing, unapproved in the TRM. | | [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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
Note: |
At the time of writing, version 6.5.00 is the most current version, released 12/12/2023. |