<Past |
Future> |
10.2.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.2.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.3 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.3.1 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.4.x |
Approved w/Constraints [4, 7, 8, 9, 10, 11] |
Approved w/Constraints [4, 7, 8, 9, 10, 11] |
Divest [4, 7, 8, 9, 11] |
Divest [4, 7, 8, 9, 11] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.5.x |
Approved w/Constraints [4, 7, 8, 9, 10, 11] |
Approved w/Constraints [4, 7, 8, 9, 10, 11] |
Divest [4, 7, 8, 9, 11] |
Divest [4, 7, 8, 9, 11] |
Divest [4, 8, 9, 11, 12] |
Divest [4, 8, 9, 11, 12] |
Divest [4, 8, 9, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.6.x |
Approved w/Constraints [4, 7, 8, 9, 10, 11] |
Approved w/Constraints [4, 7, 8, 9, 10, 11] |
Approved w/Constraints [4, 7, 8, 9, 11] |
Approved w/Constraints [4, 7, 8, 9, 11] |
Divest [4, 8, 9, 11, 12] |
Divest [4, 8, 9, 11, 12] |
Divest [4, 8, 9, 11, 12] |
Divest [4, 8, 9, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.7.x |
Unapproved |
Approved w/Constraints [4, 7, 8, 9, 10, 11] |
Approved w/Constraints [4, 7, 8, 9, 11] |
Approved w/Constraints [4, 7, 8, 9, 11] |
Divest [4, 8, 9, 11, 12] |
Divest [4, 8, 9, 11, 12] |
Divest [4, 8, 9, 11, 12] |
Divest [4, 8, 9, 11, 12] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
10.8.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [4, 8, 9, 11, 12] |
Approved w/Constraints [4, 8, 9, 11, 12] |
Approved w/Constraints [4, 8, 9, 11, 12] |
Approved w/Constraints [4, 8, 9, 11, 12] |
Approved w/Constraints [4, 8, 12, 13, 14] |
Approved w/Constraints [4, 8, 12, 13, 14] |
Approved w/Constraints [4, 8, 12, 13, 14] |
Approved w/Constraints [4, 8, 13, 14, 15] |
| | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | [2] | Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. | | [3] | 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.
| | [4] | 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. | | [5] | 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. | | [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] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [8] | 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. | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [10] | 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. | | [11] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place. | | [12] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Citrix XenDesktop, Microsoft .NET Framework, and VMware vSphere are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | [14] | This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. 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 and ensure privacy of information compliance protections are in place. | | [15] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
Users must ensure that Citrix Virtual Apps and Desktops, Microsoft .NET Framework, and VMware vSphere are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) |
|
Note: |
At the time of writing, version 10.8.2 is the latest version of this technology.
The vendor of this technology, Esri, has announced they have no plans to release future major or minor versions, and users should convert to ArcGIS Pro by Q2 2026. |