<Past |
Future> |
10.19.x |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.20.x |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.0.x |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Divest [1, 3, 4, 6, 7, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
11.x |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
Approved w/Constraints [1, 3, 4, 6, 7, 8, 9] |
| | [1] | This technology can utilize Universal Serial Bus (USB) forwarding and proper security precautions must be taken when used.
Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [3] | 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. | | [4] | 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. | | [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 VA OIT Product Engineering team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [6] | This product includes a Bluetooth capability. If that capability is leveraged, the implementer must conform to the Bluetooth Standard. 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. | | [7] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [8] | 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. | | [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, 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 11.4.1.8 is the most current version, released 04/11/2023. |