Adobe Integrated Runtime (AIR)

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:	Adobe Integrated Runtime (AIR) is a cross-operating-system runtime that enables developers to use Hypertext Markup Language (HTML), JavaScript, Adobe Flash Professional, and ActionScript to build web applications that run as standalone client applications without the constraints of a browser. The runtime supports installable applications on Windows, macOS, and mobile operating systems including Android, iOS, and BlackBerry Tablet OS. Additionally, AIR is a key component of the Adobe Flash Platform. AIR enables applications to work with data in different ways, including using local files, local SQLite (Structured Query Language) databases (for which AIR has built-in support), a database server, or the encrypted local store included with AIR. The encrypted local store uses Advanced Encryption Standard (AES) - Cipher Block Chaining (CBC) 128-bit encryption. This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
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 not been assessed by the Section 508 Office. 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.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v20.3
Decision Date:	03/05/2020
Aliases:	Adobe AIR
Introduced By:	TRM Request
Vendor Name:	Adobe

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
1
1.1
1.5
2	06/09/2010
2.5	10/25/2010
2.6	03/22/2011
2.7	06/14/2011
3.0	10/03/2011
3.1	11/11/2011
3.2	03/28/2012
3.3	06/08/2012
3.4	08/21/2012
3.5	11/06/2012
3.6	02/13/2013
3.7	04/09/2013
3.8	07/24/2013
3.9	12/10/2013
4.0	01/14/2014
13	05/13/2014
14	09/09/2014
15	12/09/2014
16	02/12/2015
17	03/12/2015
18	06/09/2015
21.x.x	03/10/2016
26.x.x	06/13/2017
27.x.x	09/12/2017
28.x.x	12/12/2017
29.x.x	03/13/2018
30.0.0.x	06/07/2018
31.0.0.x	09/11/2018
32.0.0.x	12/11/2018

Current Decision Matrix (03/02/2020)

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 waiver, signed by the Associate Deputy Assistant Secretary (ADAS), Enterprise Program Management Office (EPMO) or designee and based upon a recommendation from the STAT Working Group, 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.

<Past

CY2019

CY2020

CY2021

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2.5

Divest
[2, 3, 5]

Unapproved

3.8

Divest
[2, 3, 5]

Unapproved

17

Divest
[2, 3, 5]

Unapproved

18

Divest
[2, 3, 5]

Unapproved

21.x.x

Divest
[2, 3, 5]

Unapproved

26.x.x