<Past |
Future> |
13.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
14.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
15.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
16.x |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
19.x |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
20.x |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
21.x |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
22.x |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 11, 12] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
Approved w/Constraints [6, 10, 12, 13] |
| | [1] | Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, FIPS 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption in not used, additional mitigating controls must be documented in an approved System Security Plan (SSP). In addition, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)), unless the specific uses and instances of the technology are approved by the Enterprise Security Change Control Board (ESCCB). All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. In cases where the technology is used for external connections, a full ESCCB review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. | | [2] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | [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. | | [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] | 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. | | [7] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Microsoft .NET Framework and Acrobat Reader are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [9] | 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. | | [10] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Adobe Acrobat Reader Document Cloud (DC) is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [11] | 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. | | [12] | 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. | | [13] | 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. |
|
Note: |
At the time of writing, version 22.0.3 is the most current version, released 08/09/2022.
Versions 16.x and later will remain approved until the vendor no longer supports these versions to ensure that user service is not disrupted per Update Request # 64372. |