Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Red Hat Satellite and Proxy

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 Satellite and Proxy is an infrastructure management product that provides centralized utilities to manage the lifecycle of Red Hat systems across the enterprise. Functionality includes provisioning new systems, re-provisioning existing systems, managing security updates and configuration changes, and monitoring system performance. Administration and management of systems can be distributed across proxy systems in large organizations to allow more granular control of regional systems. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
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 v22.11
Decision Date:	11/04/2022 at 01:37:24 UTC
Aliases:	Red Hat Network Satellite
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 Desupport Date
4.x	08/31/2005	12/31/2010
5.x	06/26/2007	03/31/2017
6.x	09/10/2014

Current Decision Matrix (10/28/2022)

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

CY2023

CY2024

CY2025

Future>

Release

4.x

Unapproved

5.x

Unapproved

6.x

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

Approved w/Constraints
[15, 18, 19, 20, 22, 23]

Decision Constraints


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

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

[3]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. This product uses an embedded database, PostgreSQL, which is currently unapproved on the TRM. However, as this product is embedded and managed by Red Hat Satellite it is approved for use with this product regardless of the TRM decision of the individual database product. This can be a security concern if the database is not configured to the proper security baselines. Red Hat does allow the user access to configure the database per customer requirements, but has not tested the database against security baselines to see if the changes will break the default configurations. Users must test the configurations against the security baseline before implementation. Puppet Enterprise is embedded with this product, identical factors apply to the Puppet modules as the PostgreSQL in regards to baseline configuration changes made by the user and the adverse effect it may have on the security and functionality of the Satellite product. Red Hat Satellite is not Federal Information Processing Standard (FIPS) Publication (FIPS) 140-2 compliant as per the FIPS 140-2 Crypto Module Validation website. If this technology is used for sensitive VA data, a mitigating control must be in place.

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

[5]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Puppet Enterprise is embedded with this product, identical factors apply to the Puppet modules as the PostgreSQL in regards to baseline configuration changes made by the user and the adverse effect it may have on the security and functionality of the Satellite product. Red Hat Satellite is not Federal Information Processing Standard (FIPS) Publication (FIPS) 140-2 compliant as per the FIPS 140-2 Crypto Module Validation website. If this technology is used for sensitive VA data, a mitigating control must be in place.

[6]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Puppet Enterprise is embedded with this product, identical factors apply to the Puppet modules as the PostgreSQL in regards to baseline configuration changes made by the user and the adverse effect it may have on the security and functionality of the Satellite product. Red Hat Satellite is not Federal Information Processing Standard (FIPS) Publication (FIPS) 140-2 compliant as per the FIPS 140-2 Crypto Module Validation website. If this technology is used for sensitive VA data, a mitigating control must be in place.

[7]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[8]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[9]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[10]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[11]	Users must ensure that PostgreSQL is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-approved version of PostgreSQL.

[12]	Users must ensure that PostgreSQL is implemented with VA-approved baselines.

[13]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[14]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[15]	This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details.

[16]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[17]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[18]	Users must ensure that PostgreSQL is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)

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

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

[21]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[22]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

[23]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

Note:

At the time of writing, the most current version is 6.11 and was released 07/05/2022.

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	Red Hat Satellite and Proxy Documentation	This document repository provides users with user guides, release notes, administration guides, etc.
Vendor Provided*	Red Hat Satellite Newest Release 6.11	This site includes new features in the release and how to upgrade to the newer release.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

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
Candlepin	Candlepin is the subscription management subsystem within Red Hat Satellite. The only supported methods of using Candlepin are through the Red Hat Satellite web User Interface (UI), Command Line Interface (CLI), and Application Programming Interface (API). Red Hat does not support direct modification and interactions with Candlepin, its local API or database, as this can cause irreparable damage to the Red Hat Satellite databases. 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 software.
Fog	FOG is a Linux-based, open source computer imaging solution that is a core package of Red Hat satellite. 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 software`s.
Foreman	Foreman makes up a large amount of Red Hat Satellite`s core functionality including the web User Interface (UI) container, users, organizations, security and other significant functions. Foreman can be extended using plug-ins to include Bootdisk, Discovery, Hooks, Ovirt provisioning, Red Hat Access, foreman Tasks, SCAP, and Docker. However, only Red Hat Satellite packaged plug-ins are supported. Red Hat does not support plug-ins in the Red Hat Satellite Optional repository. 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 software`s.
Gutterball	Gutterball is a java servlet optionally deployed alongside Candlepin, as well as a component within Satellite. It integrates with Candlepin via a message bus. Candlepin emits events to the bus and Gutterball will process them and store the relevant data. User Interface (UI) for viewing reporting data will be implemented in Katello/Satellite. 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 software`s.
Hammer	Hammer is a Command Line Interface (CLI) utility that provides command line and shell equivalents of most Web UI functions. 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 technologies.
Katello	Katello is Red Hat Satellite`s Content and Subscription user interface(UI) and Application Programming (API). The only supported methods of using Katello are through the Red Hat Satellite web UI, API, and database. Red Hat does not support direct interactions and modifications to Katello. 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 technologies.
Mongodb	Mongo is a free and open source cross-platform document-oriented database and is a core package of Red Hat Satellite. 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 technologies.
PostgreSQL	PostgreSQL is an open source object-relational database system and is a part of Red Hat Satellite`s core package. 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 technologies.
Pulp	Pulp is the content management subsystem within Red Hat Satellite. Pulp usage is only supported via the Satellite Server web User Interface (UI), command line interface (CLI), and application program interface (API). Direct modification or interaction with Pulp`s local API or database is not supported. Red Hat does not support direct modification with Pulp as this can cause irreparable damage to the Red Hat Satellite databases. 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 technologies.
Puppet	Red Hat Satellite includes supported puppet packages. The installation program allows users to install and configure Puppet Masters as a part of Red Hat Satellite Capsule Servers. 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 technologies.
Qpid	Apache Qpid, an open source messaging system, implements the Advanced Message Queuing Protocol. It provides transaction management, queuing, distribution, security, management, clustering, federation and heterogeneous multi-platform support. Qpid is essential for capsule to Satellite Communication. 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 technologies.


Systems Management Systems Management Tools	System Change and Configuration Management

- The information contained on this page is accurate as of the Decision Date (11/04/2022 at 01:37:24 UTC).

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 (10/28/2022)

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

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (10/28/2022)

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

Architectural Risks

EMAIL UPDATES