<Past |
Future> |
1.6.x (Win) |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.11.x (Win) |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.12.x (Win) |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.16.x (Win) |
Approved w/Constraints [1, 3, 5, 7, 8] |
Approved w/Constraints [1, 3, 5, 7, 8] |
Approved w/Constraints [1, 3, 5, 7, 8] |
Approved w/Constraints [1, 3, 5, 7, 8, 9] |
Approved w/Constraints [1, 3, 5, 8, 9, 10] |
Approved w/Constraints [1, 3, 5, 8, 9, 10] |
Approved w/Constraints [1, 3, 5, 8, 9, 10] |
Approved w/Constraints [1, 3, 5, 8, 9, 10] |
Divest [1, 3, 9, 11, 12] |
Divest [1, 3, 9, 11, 12] |
Divest [1, 3, 9, 11, 13] |
Divest [1, 3, 9, 11, 13] |
1.33.x (Win) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 9, 11, 12] |
Approved w/Constraints [1, 3, 9, 11, 12] |
Approved w/Constraints [1, 3, 9, 11, 13] |
Approved w/Constraints [1, 3, 9, 11, 13] |
1.6.x (Mac) |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.7.x (Mac) |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.13.x (Mac) |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.26.x (Mac) |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.28.x (Max) |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.29.x (Mac) |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8] |
Divest [1, 3, 5, 7, 8, 9] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.31.x (Mac) |
Approved w/Constraints [1, 3, 5, 7, 8] |
Approved w/Constraints [1, 3, 5, 7, 8] |
Approved w/Constraints [1, 3, 5, 7, 8] |
Approved w/Constraints [1, 3, 5, 7, 8, 9] |
Approved w/Constraints [1, 3, 5, 8, 9, 10] |
Approved w/Constraints [1, 3, 5, 8, 9, 10] |
Approved w/Constraints [1, 3, 5, 8, 9, 10] |
Approved w/Constraints [1, 3, 5, 8, 9, 10] |
Divest [1, 3, 9, 11, 12] |
Divest [1, 3, 9, 11, 12] |
Divest [1, 3, 9, 11, 13] |
Divest [1, 3, 9, 11, 13] |
1.49.x (Mac) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 3, 9, 11, 12] |
Approved w/Constraints [1, 3, 9, 11, 12] |
Approved w/Constraints [1, 3, 9, 11, 13] |
Approved w/Constraints [1, 3, 9, 11, 13] |
| | [1] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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] | Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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). | | [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 potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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). | | [7] | 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). | | [8] | 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 ISO can advise on the ESCCB review process. | | [9] | 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. | | [10] | 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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [12] | 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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | [13] | 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 Project Special Forces (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|
Note: |
At the time of writing, 1.33.4 is the most current Windows version released. 1.49.0 is the most current Mac version. |