Red Hat Enterprise Linux (RHEL)

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 Enterprise Linux (RHEL) is a Linux distribution targeted toward the commercial market and provides installation routines, pre-configured components, and support services that make the installation and maintenance of the operating system more robust.
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 v23.2
Decision Date:	02/01/2023
Aliases:	RHEL, Redhat Linux
Introduced By:	ARB
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 Desupport Date
3.x
5.4	09/02/2009
5.5	03/30/2010
5.6	01/13/2011
5.7	07/21/2011
6.1	05/19/2011
4.x	02/15/2005	02/29/2012
5.x	03/15/2007	03/31/2017
6.x	11/10/2010	11/30/2020
7.x	07/31/2017	06/30/2024
8.x	05/07/2019	05/31/2029
9.x	05/17/2022

Current Decision Matrix (01/25/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 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

CY2022

CY2023

CY2024

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

4.x

Prohibited

5.x

Prohibited

6.x

Prohibited

7.x

Divest
[13, 16, 17, 18]

Divest
[17, 18, 19, 20]

8.x

Approved w/Constraints
[13, 16, 17, 18]

Approved w/Constraints
[17, 18, 19, 20]

9.x

Unapproved

Decision Constraints


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

[2]	Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities.

[3]	Use of this operating system in the production environment must conform to the published baseline (see reference tab) for installation, configuration and security. Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities.

[4]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[5]	Use of this operating system in the production environment must conform to the published baseline (see reference tab) for installation, configuration and security. Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

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

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

[8]	Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

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

[10]	Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[11]	Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Linux. See the reference section of this entry for more information. As of this writing, Red Hat Enterprise Linux 7, is the current published VA baseline. Due to multiple NIST security vulnerabilities and NSOC bulletins, extra vigilance should be applied to ensure supported versions of the product remain properly patched to mitigate known and future vulnerabilities. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[12]	Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Linux. See the reference section of this entry for more information. As of this writing, Red Hat Enterprise Linux 7, is the current published VA baseline. If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

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

[14]	Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Linux. See the reference section of this entry for more information. As of this writing, Red Hat Enterprise Linux 7, is the current published VA baseline.

[15]	Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Enterprise Linux. There are baselines for On-Premise, Azure, and AWS implementations. See the reference section of this entry for more information on baselines. As of this writing, Red Hat Enterprise Linux 7, is the current published VA baseline standard for all platforms.

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

[17]	Configuration Baselines standards for Red Hat Linux are published and maintained by VA on the BCM website and must be implemented and followed for each instance of Red Hat Enterprise Linux. There are baselines for On-Premise, Azure, and AWS implementations. See the reference section of this entry for more information on baselines. As of this writing, Red Hat Enterprise Linux 8, is the current published VA baseline standard for all platforms.

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

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

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

Note:

At the time of writing, version 9.1 is the most current version, released 11/15/2022.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Red Hat Enterprise Linux 7 Package Manifest	Red Hat	This document provides a package listing for this Operating System.
Vendor Provided*	Release Notes		This document provides documentation for Red Hat Enterprise Linux version 9.0 release notes.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

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
cURL versions bundled with Red Hat Enterprise Linux	Specific versions of cURL that are bundled, included and supported with this technology may be used with this technology. The technology vendor for this product has assumed responsibility for vulnerability patching and support of the version(s) it provides. The administrator of the machine is responsible for ensuring all relevant patches are applied. Any other version of cURL that are not bundled with this technology must comply with the cURL standalone installations TRM entry.
Firefox	Firefox is a free and open source web browser and a core package of Red Hat Enterprise Linux. Updates to core packages should be applied through the operating system to maintain inter-package compatibility as determined by the vendor. As a result, core package versions may lag behind available updates for individual products. As a core package of Linux without security constraints identified in the current approved Red Hat Enterprise Linux VA baseline, this browser is permitted for use on Red Hat Enterprise Linux.
Kickstart	This component is an interface for developing kickstart profiles that can be used to install Red Hat Enterprise Linux on either new or already-registered systems. This enables systems to be installed automatically to particular specifications.
Open Java Development Kit	Red Hat Enterprise Linux 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.
Open Lightweight Directory Access Protocol	Open Lightweight Directory Access Protocol is an open source implementation of the Lightweight Directory Access Protocol (Open Lightweight Directory Access Protocol - Request For Comments 4510) which provides access to X.500 standard directory services. Open Lightweight Directory Access Protocol is a core package of Red Hat Enterprise Linux . Updates to core packages should be applied through the operating system to maintain inter-package compatibility as determined by the vendor. As a result, core package versions may lag behind available updates for individual products.
Open Secure Sockets Layer	Open Secure Sockets Layer is an open source cryptography library for implementing Transport Layer Security (TLS) Secure Sockets Layer (SSL) security protocols typically used to encrypt internet traffic. Open Secure Sockets Layer is a core package of Red Hat Enterprise Linux . Updates to core packages should be applied through the operating system to maintain inter-package compatibility as determined by the vendor. As a result, core package versions may lag behind available updates for individual products.
Perl	Perl is a feature rich programming language with binary distribution packages for various platforms. It is an object-oriented, procedural and functional programming language, with C/C++ extensibility and database integration. Perl is a core package of Red Hat Enterprise Linux. Updates to core packages should be applied through the operating system to maintain inter-package compatibility as determined by the vendor. As a result, core package versions may lag behind available updates for individual products.
PHP	PHP is a hypertext processor and general-purpose scripting language that is typically used for web development to create dynamic web pages. PHP is a core package of Red Hat Enterprise Linux. Updates to core packages should be applied through the operating system to maintain inter-package compatibility as determined by the vendor. As a result, core package versions may lag behind available updates for individual products.
Red Hat Identity Manager (IdM)	Red Hat Identity Manager (IdM), is designed to provide an integrated identity management service for a wide range of clients, including Linux, Mac, and even Windows. IdM combines LDAP, Kerberos, DNS, and PKI with a rich management framework. Frequently, IdM is described as `Active Directory for Linux`.
x11	x11 provides a graphical user interface (GUI) for networked computers. This component creates a layer where software is written to use a generalized set of commands, allowing for reuse of programs on a computer that implements X. Use of x11 must conform to all VA security standards and policies and it is recommend that a standard configuration guide be developed and followed for this software.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Platforms and Storage Operating Systems	OS - Server

Operating Systems Supported by the Technology

This entry is an operating system.

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

The technology has a comprehensive set of documentation.
This product has a long support lifecycle with security patches and updates available for ten years for major versions.
This product adheres to the Linux Standard Base (LSB) in an effort to develop and promote a set of open standards that will increase compatibility among Linux distributions. This enables software applications to run on compliant systems.

Adoption Risks

The product includes several Federal Information Processing Standard (FIPS) validated functionality including Kernel Crypto API Cryptographic Module, dm-crypt Cryptographic Module, OpenSwan Cryptographic Module, OpenSSH-Client Cryptographic Module, OpenSSH-Server Cryptographic Module, OpenSSL Cryptographic Module, and Libgcrypt Cryptographic Module.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
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.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
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.

Architectural Benefits

This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 23.5

General Information

Vendor Release Information

Current Decision Matrix (01/25/2023)

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 23.5

General Information

Vendor Release Information

Current Decision Matrix (01/25/2023)

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