Android Software Development Kit (SDK)

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:	The Android Software Development Kit (SDK) provides the application programming interface (API) libraries and developer utilities needed to build, test, and debug Java applications for the mobile device Android operating system. This technology also includes sample projects with source code, development software, and an emulator for building applications.
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 v24.6
Decision Date:	06/05/2024 at 16:37:41 UTC
Aliases:	Android SDK
Introduced By:	TRM Request
Vendor Name:	Google

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.16	09/01/2009
3.x	07/15/2011
4.1	07/09/2012
4.2.x	11/17/2012
4.3.x	07/12/2013
4.4.x	10/12/2013
5.0.x	10/15/2014
5.1	03/11/2015
6.0	09/29/2015
7.x	08/31/2016
8.x
9.0	08/31/2018
10.x
11.x
12.x
13.0
14.x

Current Decision Matrix (06/04/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

CY2025

CY2026

CY2027

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

1.16

Unapproved

3.x

Unapproved

4.1

Unapproved

4.2.x

Unapproved

4.3.x

Unapproved

4.4.x

Unapproved

5.0.x

Unapproved

5.1

Unapproved

6.0

Unapproved

7.x

Unapproved

8.x

Unapproved

9.0

Unapproved

10.x

Unapproved

11.x

Unapproved

12.x

Unapproved

13.0

Divest
[6, 7, 8, 9]

Unapproved

14.x

Approved w/Constraints
[6, 7, 8, 9]

Decision Constraints


[1]	Projects utilizing this technology must ensure that the technology is used in a development environment and no part of the technology is extended or re-distributed. Google has restrictions on redistributing any part of the Android software development kit (SDK), and restrictions on extending or modifying the code.

[2]	Projects utilizing this technology must ensure that the technology is used in a development environment and no part of the technology is extended or re-distributed.

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

[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]	Projects utilizing this technology must ensure that the technology is used in a development environment and no part of the technology is extended or re-distributed. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.

[6]	Users should check with their supervisor, Information System Security Officer (ISSO) 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]	Projects utilizing this technology must ensure that the technology is used in a development environment and no part of the technology is extended or re-distributed. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Per the Initial Product Review, users must abide by the following constraints: Android SDK will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information where applicable. Users should consult the VA Technical Reference Model (TRM) to ensure that the JDK version that they plan to use with this technology is approved. Certain versions are listed as Divest, Unapproved, or Prohibited in the VA Technical Reference Model depending on the specific version number. Product must be included on the list of applications for continuous monitoring for published vulnerabilities, updates, and patches in order to mitigate vulnerability vectors from outdated software. Although the Android SDK has a robust user community and active forums, the use of open-source products, lacking any vendor support, may pose severe security risks to the VA. Relying on vendor support may result in slow response times and non-timely patches. Users should check with their supervisor, ISSO or local OIT representative for permission to download and use this software.

[8]	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 ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[9]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

Note:

At the time of writing, version 14.1 is the most current version.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description

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
Android Application program interface (API)	This component contains resource classes used by applications included in the platform and defines application permissions for system features.
Android Software Development Kit (SDK) Build Tools	This component is required for building Android applications.
Android Software Development Kit (SDK) Command-Line Tools	This component provides functionality for debugging and testing. The component includes other utilities required to develop an application.
Android Software Development Kit (SDK) Manager	The Android SDK is composed of modular packages that can be downloaded using the Android SDK Manager.
Android Software Development Kit (SDK) Platform Tools	This component contains platform-dependent tools for developing and debugging your application.
Android Software Development Kit (SDK) Tools	The component includes other utilities required to develop an application.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Application Technology Development Tools	Application Development Tools

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology is available at no cost through open-source licensing and supports VA's open-source initiative.
This technology may improve productivity for specific staff whose responsibilities include developing Android compatible application, and is required for use.

Adoption Risks

This technology relies on Java Development Kit (JDK) - Oracle, which has a rapid release and update schedule.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
Although this vendor utilizes Federal Information Processing (FIPS) 140-2 encryption, there is no indication based on the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this technology is Federal Information Processing Standards (FIPS) 140-2 certified.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see <a href = "https://nvd.NIST.gov/vuln/search" target="_blank">https://nvd.NIST.gov/vuln/search</a> for more details.
IPR/SAR Adoption Risk
IPR/SAR Adoption Risk
IPR/SAR Adoption Risk

Architectural Benefits

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

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 (06/04/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (06/04/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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

EMAIL UPDATES