Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.11

Adobe Animate Creative Cloud (CC)
Adobe Animate Creative Cloud (CC) Technology

Vendor Release Information

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

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version Release Date Vendor End of Life Date Vendor Desupport Date
CS4 (10) 09/23/2008
CS5 (11) 04/12/2010
CS5.5 (11.5) 05/02/2011
CS6 (12) 05/07/2012
CC (13) 07/26/2013
CC (14) 06/18/2014
CC (14.1) 10/06/2014
CC (15.1) 02/08/2016
CC (2017.x.x) 11/02/2016
CC 2018 (18.0.x) 10/18/2017
CC 2019 (19.x) 10/17/2018
CC 2020 (20.x) 11/01/2019
CC 2021 (21.x) 01/01/2021
CC 2022 (22.x) 10/01/2021
CC 2023 (23.x) 10/01/2022
CC 2024 (24.x) 10/10/2023

Current Decision Matrix (11/29/2023)

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 VAIT 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.
Legend:
White Authorized: The technology/standard has been authorized for use.
Yellow Authorized 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 Authorized w/ Constraints (POA&M): 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 Authorized w/ Constraints (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 unauthorized may be found on the Decision tab for the specific entry.
Black Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue Authorized w/ Constraints (PLANNING/EVALUATION): 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 authorized 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 authorized 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.
Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

<Past CY2018 CY2019 CY2020 Future>
Release Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
CS4 (10) Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
CS5 (11) Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
CS5.5 (11.5) DIVEST
[4, 5, 9]
DIVEST
[4, 5, 9]
DIVEST
[4, 5, 9]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
Unapproved Unapproved
CS6 (12) Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
Unapproved Unapproved
CC (13) Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
CC (14) DIVEST
[4, 5, 9]
DIVEST
[4, 5, 9]
DIVEST
[4, 5, 9]
Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
CC (14.1) DIVEST
[4, 5, 9]
DIVEST
[4, 5, 9]
DIVEST
[4, 5, 9]
Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
CC (15.1) Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[4, 5, 9]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 9, 10]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
Unapproved Unapproved
CC (2017.x.x) Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
CC 2018 (18.0.x) Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[4, 5, 9]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
CC 2019 (19.x) Unapproved Unapproved Unapproved Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
Approved w/Constraints
[5, 9, 10]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
DIVEST
[5, 10, 11]
CC 2020 (20.x) Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Approved w/Constraints
[5, 10, 11]
Approved w/Constraints
[5, 10, 11]
Approved w/Constraints
[5, 10, 11]
Approved w/Constraints
[5, 10, 11]
CC 2021 (21.x) Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
CC 2022 (22.x) Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
CC 2023 (23.x) Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
CC 2024 (24.x) Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved Unapproved
 

Decision Constraints

[1]Cloud versions of this product are not permitted without a waiver from the Architecture and Engineering Review Board (AERB) and expressed authorization. Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines.

[2]Editing and publication of official materials and graphics utilizing this software should be restricted to those who have an official need to publish information on behalf of the Department of Veterans Affairs. Additionally, no synchronization or storage of VA data is permitted outside the Department via the Creative Cloud synchronization and storage options.

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

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

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

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

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

[11]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 24.0 is the most current version, released 10/10/2023.

A standard configuration of this technology was developed by the DDE team. At the time of writing, the standard version is 23.0.2, and version 24.0 is under testing and development for six weeks from11/21/2023
- The information contained on this page is accurate as of the Decision Date (12/01/2023 at 17:53:03 UTC).