<Past |
Future> |
6.0 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.4 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.6 |
Divest [1, 2, 3, 4] |
Divest [1, 2, 3, 4] |
Divest [1, 2, 3] |
Divest [1, 2, 3] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
6.8 |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Divest [1, 2, 3] |
Divest [1, 2, 3] |
Divest [1, 2, 3] |
Divest [1, 2, 3] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.0 |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3, 4] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Divest [1, 2, 3] |
Divest [1, 2, 3] |
Divest [1, 2, 3] |
Divest [3, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.2 |
Unapproved |
Unapproved |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Divest [1, 2, 3] |
Divest [3, 5, 6] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
7.4 |
Unapproved |
Unapproved |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Divest [3, 5, 6] |
Divest [3, 5, 6] |
Divest [3, 5, 6] |
Divest [3, 6, 7, 8] |
Divest [3, 4, 6, 9] |
7.6 |
Unapproved |
Unapproved |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Divest [3, 5, 6] |
Divest [3, 5, 6] |
Divest [3, 5, 6] |
Divest [3, 6, 7, 8] |
Divest [3, 4, 6, 9] |
7.8 |
Unapproved |
Unapproved |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Divest [3, 6, 7, 8] |
Divest [3, 4, 6, 9] |
8.8 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 2, 3] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Approved w/Constraints [3, 5, 6] |
Divest [3, 6, 7, 8] |
Divest [3, 4, 6, 9] |
9.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [3, 6, 7, 8] |
Approved w/Constraints [3, 4, 6, 9] |
19.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
20.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
22.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
24.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | New installations or major expansions of this technology that will transmit data over the Wide Area Network (WAN) must complete a Systems Engineering Design Review (SEDR) (contact VA e-mail: VA IT ESE SEDR SEG) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [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] | 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] | 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. | | [5] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: OIT ITOPS SD Engagement Requests) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [6] | 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. | | [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 (contact VA e-mail: Office of Information Technology (OIT) Information Technology Operations (ITOPS) Strategy Design (SD) Engagement Requests) prior to implementation to ensure proper compliance to VA network design and usage requirements. | | [8] | 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). | | [9] | New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements. |
|
Note: |
At the time of writing, version 24.03.4.0 is the most current version, released 04/16/2024. |