<Past |
Future> |
2010 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2012 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2013 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2015 |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
2017 |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
Divest [2, 7, 8, 10, 11, 12] |
2019 |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
2022 |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
Approved w/Constraints [2, 7, 8, 10, 11, 12] |
| | [1] | 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. | | [2] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [3] | 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. | | [4] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users much ensure that Microsoft .NET Framework 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 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. | | [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] | 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. | | [9] | 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. | | [10] | 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. | | [11] | 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. | | [12] | 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. |
|