Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.1

Java SE

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:	Java Platform, Standard Edition (Java SE), formerly Java 2 Standard Edition (J2SE), is the specification of a Java virtual machine and Java application programming interface (API). Java SE has been developed under the Java Community Process. Note: This is a standards entry and does not itself expressly approve software. Please see the related technology entries for authorized software that may be installed. The Java Platform API specification contains: User interface Toolkits: Includes Abstract Window Toolkit, Swing, Java 2D, Accessibility, Drag n Drop, Input Methods, Image Input/Output, Print Service, and Sound Integration Libraries: Includes Interface Definition Language, Java Database Connectivity, Java Naming and Directory Interface, Remote Method Invocation (RMI), RMI-Internet Inter-Orb Protocol, and Scripting Other Base Libraries: Includes Beans, International Support, Input/Output, Java Management Extensions, Java Native Interface, Math, Networking, Override Mechanism, Security, Serialization, Extension Mechanism, extensible markup language (XML), and Java API for XML processing Language and Utility Base Libraries: Includes Language and Utilities, Collections, Concurrency Utilities, Java Archive, Logging, Management, Preferences API, Reference Objects, Reflection, Regular Expressions, Versioning, Zip, and Instrument
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:
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.11
Decision Date:	11/08/2024 at 02:03:26 UTC
Aliases:	Java 2 Standard Edition; J2SE; Oracle Java SE
Introduced By:	Extended Tool List (ETL)
Standards Body:	Oracle

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Industry Standard, 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
4 (aka 1.4)	02/06/2002	10/30/2008	10/30/2008
5 (aka 1.5)	09/30/2004	10/01/2009	10/01/2009
6 (aka 1.6)	12/11/2006	12/31/2015	12/31/2018
7 (aka 1.7)	07/28/2011	07/31/2019	07/31/2022
8 (aka 1.8)	03/18/2014	03/31/2022	12/31/2030
9 (aka 1.9)	09/01/2017	03/31/2018	03/31/2018
10 (aka 1.10)	03/01/2018	09/30/2018	09/30/2018
11 (aka 1.11)	09/01/2018	09/30/2023	09/30/2026
12 (aka 1.12)	03/01/2018	09/30/2019	09/30/2019
13 (aka 1.13)	09/01/2019	03/31/2020	03/31/2020
14 (aka 1.14)	03/01/2020	09/30/2020	09/30/2020
15 (aka 1.15)		03/31/2021	03/31/2021
16 (non-LTS).x	03/01/2021	09/01/2021
17 (LTS).x	09/01/2021	09/01/2026	09/01/2029
18 (non-LTS).x	03/01/2022	09/01/2022
19 (non-LTS).x	09/01/2022	03/01/2023
20 (non-LTS).x	03/08/2023	09/01/2023	09/01/2023
21 (LTS).x	09/13/2023	09/20/2031	09/20/2031
22 (non-LTS).x	03/13/2024	09/01/2024	09/01/2024
23 (non-LTS).x	09/10/2024	03/01/2025	03/01/2025
24 (non-LTS).x	06/04/2024	09/01/2025	09/01/2025

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

CY2024

CY2025

CY2026

Future>

Release

4 (aka 1.4)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

5 (aka 1.5)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

6 (aka 1.6)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

7 (aka 1.7)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

8 (aka 1.8)

Approved w/Constraints
[6, 7, 8]

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

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

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

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

9 (aka 1.9)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

10 (aka 1.10)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

11 (aka 1.11)

Approved w/Constraints
[6, 7, 8]

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

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

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

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

12 (aka 1.12)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

13 (aka 1.13)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

14 (aka 1.14)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

15 (aka 1.15)

Prohibited

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

16 (non-LTS).x

Approved w/Constraints
[6, 7, 8]

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

17 (LTS).x

Approved w/Constraints
[6, 7, 8]

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

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

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

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

18 (non-LTS).x

Approved w/Constraints
[6, 7, 8]

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

19 (non-LTS).x

Approved w/Constraints
[6, 7, 8]

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

20 (non-LTS).x

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

21 (LTS).x

Unapproved

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

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

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

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

22 (non-LTS).x

Unapproved

Authorized w/ Constraints (POA&M)

Unapproved

Authorized w/ Constraints (POA&M)

23 (non-LTS).x

Unapproved

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

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

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

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

24 (non-LTS).x

Unapproved

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

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

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

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

Decision Constraints


[1]	This Industry Standard 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.

[2]	Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. Configuration and deployment standards images which are defined and maintained by the Core Systems Engineering organization within VA Enterprise Systems Engineering must be followed and adhered to unless an appropriate waiver is granted.

[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 authorized and the user should take the proper steps to decline those installations.

[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]	This is a standards entry and does not itself expressly approve software. Please see the related TRM technology entries for authorized software versions that may be installed related to this standard.

[6]	This is a standards entry and does not itself expressly approve software. Please see the related TRM technology entries for authorized software versions that may be installed related to this standard.

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

[8]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[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 24 (non-LTS) is the most current version, released 06/04/2024. This is a standards entry and does not itself expressly approve software. Please see the related technology entries for authorized software that may be installed. Also note that as of this writing, Oracle has no plans to release a separate JRE for Java 11 and later and users will be required to install the full Oracle JDK to support Java 11 and beyond. Java 12, 13, 14, and 15 are not long term supported releases and only have 6 month lifecycles. These versions will not be authorized in VA. Only Long Term Support versions are supported in VA.

Standard 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.
Source	Name	Description
JSR-250	Common Annotations for the Java Platform	Added in Java Standard Edition 6 (Java SE), this specification provides annotations for common semantic concepts in the Java 2 Standard Edition (J2SE) and Java 2 Enterprise Edition (J2EE) platforms that apply across a variety of individual technologies.
JSR-206	Java API for Extensible Markup Language (XML) Processing (JAXP)	This specification defines a set of implementation independent portable application programming interfaces (API) supporting extensible markup language processing.
JSR-224	Java API for XML-Based Web Services (JAX-WS)	This specification is fundamental for developing Simple Object Access Protocol (SOAP) based and RESTful Java Web services. The web services component of this specification is designed to take the place of remote procedure calls in Web services and Web applications.
JSR-222	Java Architecture for XML Binding (JAXB)	JAXB provides a convenient way to process Extensible Markup Language (XML) content using Java objects by binding its XML schema to Java representation.
JSR-208	Java Business Integration (JBI)	This specification extends J2EE and J2SE with business integration service provider interface.
JSR-199	Java Compiler API	JSR-199 provides a service provider API that allows a Java program to select and invoke a Java Language Compiler programmatically.
JSR-255	Java Management Extensions (JMX)	This specification provides management architecture, APIs and services for building Web-based, distributed, dynamic and modular solutions to manage Java enabled resources.
JSR-10	Java Naming and Directory Interface (JNDI)	The Java Naming and Directory Interface provides naming and directory functionality to applications written in the Java programming language. It is defined to be independent of any specific directory service implementation.
JSR-270	Java Platform, Standard Edition 6 (Java SE 6)	The Java SE 6.0 specification defines a wide range of general purpose APIs and also includes the Java Language Specification and the Java Virtual Machine Specification. In addition to being used standalone on servers, Java SE is also used as the base for Java Platform, Enterprise Edition ("Java EE").
JSR-221	JDBC API	This API is the industry standard for database-independent connectivity between the Java programming language and a wide range of databases. The API provides a call-level API for Structured Query Language-based database access. The specification defines "Write Once, Run Anywhere" capabilities for applications that require access to enterprise data.
JSR-203	More New I/O APIs for the Java Platform ("NIO.2")	This specification defines the application programming interfaces for file system access, scalable asynchronous I/O operations, socket-channel binding and configuration, and multicast datagrams.
JSR-223	Scripting for the Java Platform	Added in Java SE 6, this specification describes mechanisms allowing scripting language programs to access information developed in the Java Platform and allowing scripting language pages to be used in Java server-side applications.
JSR-334	Small Enhancements to the Java Programming Language (OpenJDK Project Coin)	This specification defines assorted changes to the Java programming language to improve productivity.
JSR-173	Streaming API for XML (StAX)	The Streaming API for XML (StAX) is a Java based API for pull-parsing XML. StAX provides an alternative to SAXParser, document object model (DOM), Transformation API for XML, and DOM.
JSR-292	Supporting Dynamically Typed Languages on the Java Platform	This specification supports execution method invocations in the absence of static type information.
JSR-181	Web Services Metadata for the Java Platform	This specification defines an annotated Java format that that uses Java Language Metadata (JSR 175) to enable easy definition of Java Web Services in a J2EE container.
JSR-105	XML Digital Signature APIs	This document defines and incorporates a standard set of high-level implementation-independent APIs for XML digital signatures services. The XML Digital Signature specification is defined by the World Wide Web Consortium (W3C).


Application Technology Development Tools	Development Frameworks

General Analysis

Adoption Benefits

This Standard supports VA major initiatives which are used implement certain specifications to help develop and deploy code for desktop and server environments.
This Standard defines support for multithreading in object processing. Multithreading functionality provides increased productivity resulting from the ability to complete higher numbers of processes per unit of processing time.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this standard. Please see https://nvd.NIST.gov/vuln/search for more details.
There is no indication based on either the vendor documentation or the Cryptographic Module Validation Program (CMVP) that this standard is Federal Information Processing Standard (FIPS) 140-2 compliant.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this standard.

Architectural Benefits

Java SE provides for distributed applications. Using Java remote method invocation, applications can access and use objects on remote machines.
Java Platform, Standard Edition (Java SE) is portable to all VA operating systems. The specification defines a virtual machine that translates Java byte code to the assembler code of the underlying operating system and machine hardware.

- The information contained on this page is accurate as of the Decision Date (11/08/2024 at 02:03:26 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.1

General Information

Vendor Release Information

Current Decision Matrix (11/06/2024)

Decision Constraints

References

Standard Components

VA Categories

View the VA Categorization Framework

Technologies/Standards Relationships

Implemented By/Verified With:

Comparable Standards:

Associated Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 25.1

General Information

Vendor Release Information

Current Decision Matrix (11/06/2024)

Decision Constraints

References

Standard Components

VA Categories View the VA Categorization Framework

Technologies/Standards Relationships

Implemented By/Verified With:

Comparable Standards:

Associated Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES

VA Categories

View the VA Categorization Framework