AutoCAD

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Autodesk AutoCAD is computer-aided design (CAD) software for two dimensional (2D) and three dimensional (3D) drafting. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.1
Decision Date:	01/23/2024 at 01:30:39 UTC
Introduced By:	SCCM
Vendor Name:	Autodesk, Inc.

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
2012 (18.2)	03/22/2011
2013 (19.0)	03/27/2012
2014 (19.1)	03/26/2013
2015	06/05/2014
2016	03/23/2015
2017	03/21/2016
2018	03/21/2017
2019	03/22/2018
2020	03/17/2019
2021	03/25/2020
2022	03/05/2021
2023	03/28/2022
2024.x	03/28/2023

Current Decision Matrix (01/22/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time 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. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2017

CY2018

CY2019

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2012 (18.2)

Unapproved

2013 (19.0)

Unapproved

2014 (19.1)

Divest
[2, 3, 4, 5, 6]

Unapproved

2015

Divest
[2, 3, 4, 5, 6]

Unapproved

2016

Divest
[2, 3, 4, 5, 6]

Divest
[3, 4, 5, 6, 7]

Divest
[3, 5, 6, 8, 9]

Divest
[3, 5, 6, 9, 10]

Unapproved

2017

Approved w/Constraints
[2, 3, 4, 5, 6]

Approved w/Constraints
[3, 4, 5, 6, 7]

Approved w/Constraints
[3, 5, 6, 8, 9]

Approved w/Constraints
[3, 5, 6, 9, 10]

Divest
[3, 5, 6, 9, 10]

Unapproved

2018

Unapproved

Approved w/Constraints
[3, 4, 5, 6, 7]

Approved w/Constraints
[3, 5, 6, 8, 9]

Approved w/Constraints
[3, 5, 6, 9, 10]

Divest
[3, 5, 6, 9, 10]

Approved w/Constraints
[3, 5, 6, 9, 10]

2019

Unapproved

Approved w/Constraints
[3, 5, 6, 9, 10]

Divest
[3, 5, 6, 9, 10]

Approved w/Constraints
[3, 5, 6, 9, 10]

2020

Unapproved

Approved w/Constraints
[3, 5, 6, 9, 10]

2021

Unapproved

2022

Unapproved

2023

Unapproved

2024.x

Unapproved

Decision Constraints


[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]	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.

[3]	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.

[4]	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.

[5]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[6]	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.

[7]	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).

[8]	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).

[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]	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).

Note:

At the time of writing, version 2024.1.2 is the most current version, released 11/15/2023.

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 24.1.162.0 (2022) and version 2024 will begin testing.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Other	Autodesk AutoCAD Code Execution Vulnerability Security Hotfix Readme.	Vendor	Guide to fix common vulnerability exposures (CVE) vulnerabilities.
Vendor Provided*	System Requirements for AutoCAD 2023 and Specialized Toolsets.		This link provides information about system requirements for AutoCAD 2023 on the Windows and MacOS operating systems. Toolsets include: AutoCAD Map, AutoCAD Electrical, AutoCAD Architecture, AutoCAD MEP, AutoCAD Plant 3D, AutoCAD Mechanical and AutoCAD Raster Design.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
ACAD Private	ACAD Private is a Medium Scale Integration (MSI) installation package which is a required part of an AutoCAD installation. The MSI package installs required files for AutoCAD; without this MSI package AutoCAD can`t run.
Architecture Toolset	The Architecture Toolset gives users the ability to access the AutoCAD library, automatically generate floor plans and quickly place walls, doors, and windows.
AutoCad Web	This link provides information about AutoCAD Web . This component technology is included in an AutoCAD or AutoCAD LT subscription. It allows the user access to CAD designs via the web or mobile app.
Autodesk Single Sign-on Component (SSO)	This link describes the Single Sign-On (SSO) component that can be bundled with AutoCAD. Single Sign-On lets users access Autodesk products and services using the same email and password used by their organization.
Map 3D Toolset	This component enables direct access to spatial data using Feature Data Objects (FDO) technology, directly edit geospatial data, and manage infrastructure systems with Enterprise Industry Models.
MEP Toolset	This component gives uses access to AutoCAD`s library of mechanical, electrical, and plumbing (MEP) objects, the ability to optimize workflow, and automatically update drawings and sheets when changes occur.
Plant 3D Toolset	The Plant 3D Toolset allows users to collaborate in a secure cloud environment, speed up and automate piping and instrumentation diagrams, and automatically create piping isometric drawings directly from the three dimensional model.
Raster Design Toolset	The Raster Design Toolset allows users to access tools to enhance image editing, edit RemObjects, and simplify workflow using vectorization tools.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Productivity Software	Graphics Design Software

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

DirectX
Microsoft .NET - (required for some configurations)
Microsoft .NET Framework - (required for some configurations)

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology may improve productivity for specific staff whose responsibilities include two dimensional (2D) and three dimensional (3D) modeling and design.
This technology has a comprehensive set of documentation.
This technology uses 3rd party software to meet FIPS 140-2 compliance.

Adoption Risks

The technology requires the purchase of licenses from vendor, which could potentially lead to vendor lock-in.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
There are other approved solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (01/22/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (01/22/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES