Red Hat build of Open Java Development Kit (OpenJDK)

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:	Red Hat build of Open Java Development Kit (OpenJDK) is a version of OpenJDK that runs on the Red Hat Enterprise Linux environment. Versions of Open Java Development Kit that are bundled, patched and supported by Red Hat Enterprise Linux for a specific version of Red Hat Enterprise Linux may be used on that version of Red Hat Enterprise Linux as long as that version of Open Java Development Kit is patched, maintained and supported.
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.7
Decision Date:	07/15/2024 at 19:06:16 UTC
Introduced By:	TRM Request
Vendor Name:	Red Hat

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.8.x (LTS)
11.x (LTS)
12.x (non-LTS)
13.x (non-LTS)
14.x (non-LTS)
15.x (non-LTS)
16.x (non-LTS)
17.x (LTS)
18.x (non-LTS)
19.x (non-LTS)
21.x (LTS)	05/09/2024

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

CY2024

CY2025

CY2026

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

1.8.x (LTS)

Approved w/Constraints
[4, 5, 8, 9]

Approved w/Constraints
[4, 8, 9, 10, 11]

11.x (LTS)

Approved w/Constraints
[4, 5, 8, 9]

Approved w/Constraints
[4, 8, 9, 10, 11]

12.x (non-LTS)

Unapproved

13.x (non-LTS)

Unapproved

14.x (non-LTS)

Unapproved

15.x (non-LTS)

Unapproved

16.x (non-LTS)

Unapproved

17.x (LTS)

Approved w/Constraints
[4, 5, 8, 9]

Approved w/Constraints
[4, 8, 9, 10, 11]

18.x (non-LTS)

Unapproved

19.x (non-LTS)

Unapproved

21.x (LTS)

Unapproved

Approved w/Constraints
[4, 8, 9, 10, 11]

Decision Constraints


[1]	Use of this is restricted to Red Hat Enterprise Linux which supports Open Java Development Kit versions that run on their product. Versions of Open Java Development Kit that are bundled, patched and supported by Red Hat Enterprise Linux for a specific version of Red Hat Enterprise Linux may be used on that version of Red Hat Enterprise Linux as long as that version of Open Java Development Kit is patched, maintained and supported. Use of this Java on any other platform is unapproved at this time. Per the Initial Product Review, users must abide by the following constraints: System administrators must ensure an underlying infrastructure (Operating System (OS), Web Server, etc.) or a third party FIPS 140-2 cryptographic module can protect the security of Red Hat OpenJDK when it processes, stores, or transmits VA sensitive information. Open source software must be obtained from an official source. The VA requires support for all software used on the VA network. Enterprise level support must be acquired from the vendor for any open source product to be deployed on the VA network. System administrators must ensure that they are using OpenJDK 8 and/or OpenJDK 11 distributions as these are the versions that are provided with long term support until June 2023 and October 2024, respectively.

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

[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]	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]	Use of this is restricted to Red Hat Enterprise Linux which supports Open Java Development Kit versions that run on their product. Versions of Open Java Development Kit that are bundled, patched and supported by Red Hat Enterprise Linux for a specific version of Red Hat Enterprise Linux may be used on that version of Red Hat Enterprise Linux as long as that version of Open Java Development Kit is patched, maintained and supported. Use of this Java on any other platform is unapproved at this time. Users must ensure that Red Hat Enterprise Linux is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’). Per the Initial Product Review, users must abide by the following constraints: System administrators must ensure an underlying infrastructure (Operating System (OS), Web Server, etc.) or a third party FIPS 140-2 cryptographic module can protect the security of Red Hat OpenJDK when it processes, stores, or transmits VA sensitive information. Open source software must be obtained from an official source. The VA requires support for all software used on the VA network. Enterprise level support must be acquired from the vendor for any open source product to be deployed on the VA network. System administrators must ensure that they are using OpenJDK 8 and/or OpenJDK 11 distributions as these are the versions that are provided with long term support until June 2023 and October 2024, respectively.

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

[7]	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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

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

[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 ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[10]	Use of this is restricted to Red Hat Enterprise Linux which supports Open Java Development Kit versions that run on their product. Versions of Open Java Development Kit that are bundled, patched and supported by Red Hat Enterprise Linux for a specific version of Red Hat Enterprise Linux may be used on that version of Red Hat Enterprise Linux as long as that version of Open Java Development Kit is patched, maintained and supported. Use of this Java on any other platform is unapproved at this time. Users must ensure that Red Hat Enterprise Linux is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’). Per the Initial Product Review, users must abide by the following constraints: System administrators must ensure an underlying infrastructure (Operating System (OS), Web Server, etc.) or a third party FIPS 140-2 (or its successor) certified cryptographic module can protect the security of Red Hat OpenJDK when it processes, stores, or transmits VA sensitive information. Open source software must be obtained from an official source. The VA requires support for all software used on the VA network. Enterprise level support must be acquired from the vendor for any open source product to be deployed on the VA network. System administrators must ensure that they are using OpenJDK 8 and/or OpenJDK 11 distributions as these are the versions that are provided with long term support until June 2023 and October 2024, respectively.

[11]	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 21.0.3 is the most current version, released 05/09/2024.

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
No components have been identified for this entry.

VA Categories View the VA Categorization Framework

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

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Comparable Technologies:

Companion Technologies/Supported Standards:

No companion technologies/standards have been identified.

General Analysis

Adoption Benefits

At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Network Security Operations Center (NSOC) bulletins had been issued for the latest versions of this technology.
This is a well-documented technology.
This technology provides complementary functionality to the Java Development Kit (JDK) as the JDK is a development utility.
This technology may improve productivity for specific staff whose responsibilities include working with Open Java Development Kit (OpenJDK).
This technology extends the functionality of Red Hat Enterprise Linux.

Adoption Risks

IPR/SAR Adoption Risk - The product is not Federal Information Processing Standards (FIPS) 140-2 (or its successor) certified.
IPR/SAR Adoption Risk - The Red Hat build of OpenJDK is open source and freely available to users. Per vendor: “Support is included or available via the following subscriptions: RHEL, Red Hat Middleware, Red Hat Runtimes, and Red Hat build of OpenJDK for Windows (for all non-Red Hat Middleware Java workloads) …A standalone Windows subscription is also available for purchase.”
IPR/SAR Adoption Risk - OpenJDK 7 for RHEL has an end of support date of June 2020. Additionally, OpenJDK 13 is available to the public; however Red Hat has yet to establish Lifecycle support dates for OpenJDK 13 RHEL and Windows versions.
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.
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.
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.

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/27/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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

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

EMAIL UPDATES