<Past |
Future> |
1.8.x |
Approved w/Constraints [1, 2, 3, 4, 5] |
Divest [1, 2, 3, 4, 5] |
Divest [1, 2, 3, 5, 6] |
Divest [1, 2, 3, 5, 6] |
Divest [1, 3, 5, 6, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.9.x |
Approved w/Constraints [1, 2, 3, 4, 5] |
Approved w/Constraints [1, 2, 3, 4, 5] |
Approved w/Constraints [1, 2, 3, 5, 6] |
Approved w/Constraints [1, 2, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6, 7] |
Divest [1, 3, 5, 6, 7] |
Divest [1, 3, 5, 6, 7] |
Divest [1, 3, 5, 6, 7] |
Divest [1, 3, 5, 6, 7] |
Unapproved |
Unapproved |
Unapproved |
1.14.x |
Approved w/Constraints [1, 2, 3, 4, 5] |
Approved w/Constraints [1, 2, 3, 4, 5] |
Approved w/Constraints [1, 2, 3, 5, 6] |
Approved w/Constraints [1, 2, 3, 5, 6] |
Approved w/Constraints [1, 3, 5, 6, 7] |
Approved w/Constraints [1, 3, 5, 6, 7] |
Divest [1, 3, 5, 6, 7] |
Divest [1, 3, 5, 6, 7] |
Divest [1, 3, 5, 6, 7] |
Divest [1, 3, 5, 6, 7] |
Unapproved |
Unapproved |
1.18.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 5, 6, 7] |
Approved w/Constraints [1, 3, 5, 6, 7] |
Approved w/Constraints [1, 3, 5, 6, 7] |
Approved w/Constraints [1, 3, 5, 6, 7] |
Approved w/Constraints [1, 3, 5, 6, 7] |
Approved w/Constraints [1, 3, 5, 6, 7] |
Divest [1, 3, 7] |
2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 7] |
| | [1] | 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. | | [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] | 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. | | [5] | Users must ensure that Microsoft .NET Framework Technology is implemented with VA-approved baselines. | | [6] | 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. | | [7] | 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. |
|
Note: |
At the time of writing, version 2.4.1 is the most current version, released 10/25/2022. |