<Past |
Future> |
2013 (19.0) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2014 (19.1) |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2015 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2016 |
Divest [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2017 |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2018 |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Divest [5, 7, 8, 11, 12] |
Divest [5, 7, 8, 11, 12] |
Divest [5, 7, 8, 11, 12] |
Divest [5, 7, 8, 11, 12] |
2019 |
Unapproved |
Unapproved |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Divest [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [5, 7, 8, 11, 12] |
Divest [5, 7, 8, 11, 12] |
Divest [5, 7, 8, 11, 12] |
Divest [5, 7, 8, 11, 12] |
2019.1.2 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [6, 7, 8, 10] |
Approved w/Constraints [5, 7, 8, 11, 12] |
Approved w/Constraints [5, 7, 8, 11, 12] |
Approved w/Constraints [5, 7, 8, 11, 12] |
Approved w/Constraints [5, 7, 8, 11, 12] |
2020 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [5, 7, 8, 11, 12] |
Approved w/Constraints [5, 7, 8, 11, 12] |
Approved w/Constraints [5, 7, 8, 11, 12] |
Approved w/Constraints [5, 7, 8, 11, 12] |
2022 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2023 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2024 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
2025 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Product must remain properly patched in order to mitigate known and future security vulnerabilities. Product features includes cloud connectors to a personal online AutoCAD account. These and other external Peer-to-Peer repositories are not approved for use in the organization at this time. | | [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] | Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | [4] | This software has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning. If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [5] | 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. | | [6] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | [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. | | [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] | 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). | | [10] | 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). | | [11] | 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 Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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). |
|
Note: |
At the time of writing, version 2025 is the most current version, released 03/28/2024.
A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 2022. |