Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

OpenShift Container Platform

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:	OpenShift Container Platform (formerly known as OpenShift Enterprise) is a cloud computing Platform-as-a-Service (PaaS) solution designed for on-premise or private cloud deployments that provides a self-service development environment to developers. 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 v24.9
Decision Date:	09/23/2024 at 17:08:26 UTC
Aliases:	Platform-as-a-Service (PaaS); cloud infrastructure
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).

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
2.0	12/02/2013
3.1.x
3.5	04/13/2017
3.6	08/09/2017
3.7	11/01/2017
3.8	11/22/2017
3.9	03/28/2018
3.11	09/01/2018	06/30/2022	06/30/2022
4.2	10/16/2019	02/23/2020	02/23/2020
4.3	01/15/2020	06/30/2020	12/31/2020
4.4	05/04/2020	08/13/2020	02/24/2021
4.5	07/01/2020	11/27/2020	07/27/2021
4.6.x	10/27/2020	03/24/2021	10/18/2021
4.7.x	02/23/2021	10/27/2021	08/24/2022
4.8.x	05/07/2021	01/27/2022	01/27/2023
4.9.x	10/17/2021	06/10/2022	04/18/2023
4.10.x	03/10/2022	11/10/2022	09/10/2023
4.11.x	08/10/2022	04/17/2023	02/10/2024
4.12.x	01/17/2023	08/17/2023	01/17/2025
4.13.x	05/17/2023	01/31/2024	11/17/2024
4.14.x	10/31/2023	05/27/2024	05/01/2025
4.15.x	02/27/2024	09/27/2024	08/27/2025
4.16.x	07/16/2024		12/27/2025

Current Decision Matrix (09/19/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

CY2022

CY2023

CY2024

Future>

Release

2.0

Unapproved

Authorized w/ Constraints (POA&M)

3.1.x

Unapproved

Authorized w/ Constraints (POA&M)

3.5

Unapproved

Authorized w/ Constraints (POA&M)

3.6

Unapproved

Authorized w/ Constraints (POA&M)

3.7

Unapproved

Authorized w/ Constraints (POA&M)

3.8

Unapproved

Authorized w/ Constraints (POA&M)

3.9

Unapproved

Authorized w/ Constraints (POA&M)

3.11

DIVEST
[8, 10, 16, 19, 20, 21]

DIVEST
[8, 10, 16, 20, 21, 22]

Unapproved

Authorized w/ Constraints (POA&M)

4.2

Unapproved

Authorized w/ Constraints (POA&M)

4.3

Unapproved

Authorized w/ Constraints (POA&M)

4.4

Unapproved

Authorized w/ Constraints (POA&M)

4.5

Unapproved

Authorized w/ Constraints (POA&M)

4.6.x

Unapproved

Authorized w/ Constraints (POA&M)

4.7.x

DIVEST
[8, 10, 16, 19, 20, 21]

DIVEST
[8, 10, 16, 20, 21, 22]

Unapproved

Authorized w/ Constraints (POA&M)

4.8.x

DIVEST
[8, 10, 16, 19, 20, 21]

DIVEST
[8, 10, 16, 20, 21, 22]

DIVEST
[8, 10, 16, 20, 22, 23]

DIVEST
[20, 22, 23, 24, 25, 26]

Unapproved

Authorized w/ Constraints (POA&M)

4.9.x

Approved w/Constraints
[8, 10, 16, 19, 20, 21]

Approved w/Constraints
[8, 10, 16, 20, 21, 22]

DIVEST
[8, 10, 16, 20, 21, 22]

DIVEST
[8, 10, 16, 20, 22, 23]

DIVEST
[20, 22, 23, 24, 25, 26]

Unapproved

Authorized w/ Constraints (POA&M)

4.10.x

Approved w/Constraints
[8, 10, 16, 19, 20, 21]

Approved w/Constraints
[8, 10, 16, 20, 21, 22]

DIVEST
[8, 10, 16, 20, 22, 23]

DIVEST
[20, 22, 23, 24, 25, 26]

DIVEST
[20, 22, 24, 25, 26, 27]

DIVEST
[20, 22, 24, 25, 27, 28]

DIVEST
[3, 20, 24, 25, 27, 28, 29]

Unapproved

Authorized w/ Constraints (POA&M)

4.11.x

Unapproved

Approved w/Constraints
[8, 10, 16, 20, 22, 23]

Approved w/Constraints
[20, 22, 23, 24, 25, 26]

Approved w/Constraints
[20, 22, 24, 25, 26, 27]

DIVEST
[20, 22, 24, 25, 27, 28]

DIVEST
[3, 20, 24, 25, 27, 28, 29]

DIVEST
[20, 24, 25, 28, 29, 30]

Authorized w/ Constraints (DIVEST)
[20, 24, 25, 28, 29, 30]

4.12.x

Unapproved

Approved w/Constraints
[20, 22, 24, 25, 27, 28]

DIVEST
[3, 20, 24, 25, 27, 28, 29]

DIVEST
[20, 24, 25, 28, 29, 30]

Authorized w/ Constraints (DIVEST)
[20, 24, 25, 28, 29, 30]

4.13.x

Unapproved

DIVEST
[3, 20, 24, 25, 27, 28, 29]

DIVEST
[20, 24, 25, 28, 29, 30]

Authorized w/ Constraints (DIVEST)
[20, 24, 25, 28, 29, 30]

4.14.x

Unapproved

DIVEST
[3, 20, 24, 25, 27, 28, 29]

DIVEST
[20, 24, 25, 28, 29, 30]

Authorized w/ Constraints (DIVEST)
[20, 24, 25, 28, 29, 30]

4.15.x

Unapproved

Approved w/Constraints
[3, 20, 24, 25, 27, 28, 29]

DIVEST
[20, 24, 25, 28, 29, 30]

Authorized w/ Constraints (DIVEST)
[20, 24, 25, 28, 29, 30]

4.16.x

Unapproved

Approved w/Constraints
[20, 24, 25, 28, 29, 30]

Authorized w/ Constraints
[20, 24, 25, 28, 29, 30]

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 potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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).

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

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

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

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

[7]	Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. 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).

[8]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

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

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

[12]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Due to potential information security risks, Software as a Service/Platform as a Service (SaaS/PaaS) must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. Based on the IPR findings from Security Engineering and pending required VA security policy guidance from OIS DevSecOps on container and orchestrator technology, this technology is only authorized for Development and Test systems usage. Production system use of this technology is considered TRM unapproved must have an authorized TRM waiver to accept the risks of using this technology in production without required policy and configuration standards. This constraint will be revisited after VA determines relevant policy and creates configuration standard(s). See the reference section and the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx

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

[14]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Due to potential information security risks, Software as a Service/Platform as a Service (SaaS/PaaS) must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. Based on the IPR findings from Security Engineering and pending required VA security policy guidance from OIS DevSecOps on container and orchestrator technology, only Version 3.11 is authorized for production use at this time and the referenced VA Security Baseline for version 3.11 must be followed. Version 4.4 and 4.5 and newer versions of this technology are only authorized for Development and Test systems usage at this time. Production system use of Version 4.x of this technology is considered TRM unapproved must have an authorized TRM waiver to accept the risks of using this technology in production without required policy and configuration standards. This constraint will be revisited after VA determines relevant policy and creates configuration standard(s) for Version 4. See the reference section and the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx

[15]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review, users must abide by the following constraints: Due to potential information security risks, Software as a Service/Platform as a Service (SaaS/PaaS) must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. TheRed Hat OpenShift v3.11 Secure Configuration Baseline must be followed. Based on the IPR findings from Security Engineering and pending required VA security policy guidance from OIS DevSecOps on container and orchestrator technology, only Version 3.11 is authorized for production use at this time and the referenced VA Security Baseline for version 3.11 must be followed. Version 4.4, 4.5 and 4.6 of this technology are only authorized for Development and Test systems usage at this time. Production system use of Version 4.x of this technology is considered TRM unapproved must have an authorized TRM waiver to accept the risks of using this technology in production without required policy and configuration standards. This constraint will be revisited after VA determines relevant policy and creates configuration standard(s) for Version 4. See the reference section and the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx

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

[18]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review, users must abide by the following constraints: Due to potential information security risks, Software as a Service/Platform as a Service (SaaS/PaaS) must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. The Red Hat OpenShift v4.7 Secure Configuration Baseline must be followed. (refer to the ‘Reference’ tab) Based on the IPR findings from Security Engineering and pending required VA security policy guidance from OIS DevSecOps on container and orchestrator technology, Version 4.7 is authorized for production use at this time and the referenced VA Security Baseline for version 4.7 must be followed. Version 4.4, 4.5 and 4.6 of this technology are only authorized for Development and Test systems usage at this time. Production system use of Version 4.4, 4.5 and 4.6 of this technology is considered TRM unapproved must have an authorized TRM waiver to accept the risks of using this technology in production without required policy and configuration standards. The vendor has announced that versions 4.6.x have exited the full support stage, and transitioned to the maintenance support stage. These versions will be de-supported by the vendor upon the release of 4.9. See the reference section and the Baseline Configuration Management website for more information:https://vaww.eie.va.gov/SysDesign/CS/Lists/Baseline%20List/AllItems.aspx

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

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

[21]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review, users must abide by the following constraints: Due to potential information security risks, Software as a Service/Platform as a Service (SaaS/PaaS) must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF. The Red Hat OpenShift Secure Configuration Baseline must be followed. (refer to the ‘Reference’ tab) Based on the IPR findings from Security Engineering and pending required VA security policy guidance from OIS DevSecOps on container and orchestrator technology, Version 4.7+ is authorized for production use at this time and the referenced VA Security Baseline for version 4.7+ must be followed.

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

[23]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period. Per the Initial Product Review, users must abide by the following constraints: Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC. The Red Hat OpenShift Secure Configuration Baseline must be followed. Administrators must ensure that the product is patched and updated according to vendor recommendations.

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

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

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

[27]	This platform has an active baseline configuration and is in use. However, this technology may not appear in software inventory tools due to that nature of the technology. This should not be unapproved due to lack of scans showing it in current system scans.

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

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

[30]	This platform has an active baseline configuration and is in use. However, this technology may not appear in software inventory tools due to that nature of the technology. This should not be unapproved due to lack of scans showing it in current system scans. Per the Initial Product Review, users must abide by the following constraints: Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC. The Red Hat OpenShift Secure Configuration Baseline must be followed. Administrators must ensure that the product is patched and updated according to vendor recommendations. The product should use a certified FIPS 140-2 cryptographic module for use with any data containing PHI/PII or VA sensitive information. The listed CVE and remediation steps should be monitored to ensure OpenShift uses certified FIPS 140-2 encryption.

Note:

At the time of writing, version 4.16 is the most current version released. A baseline configuration of this technology was developed by the BCM team. At the time of writing, the baseline version is 4.x.

Name	Description
No components have been identified for this entry.


Platforms and Storage Cloud Services/Server Virtualization	Cloud Technologies

General Analysis

Adoption Benefits

This technology is Federal Information Processing (FIPS) 140-2 compliant.
This technology supports several industry standard file formats.
This is a well-documented technology.
This technology may reduce administrative time devoted to software maintenance and support.
This technology supports Platform as a Service (PaaS) and may reduce application development and deployment time.
This technology is available at no cost through open-source licensing and supports VA`s open source initiative.

Adoption Risks

As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
IPR/SAR Adoption Risk - There are multiple published vulnerabilities for Red Hat OpenShift.
IPR/SAR Adoption Risk - OpenShift Container Platform can be deployed on-premise or in the cloud.
IPR/SAR Adoption Risk - The VA Secure Configuration Baseline for the corresponding version of Red Hat OpenShift must be followed.
IPR/SAR Adoption Risk - A compliance problem was found in the Red Hat OpenShift Container Platform. Red Hat discovered that, when FIPS mode was enabled, not all the cryptographic modules in use were FIPS-validated. This is referenced in CVE 2023-3089.
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.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
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.
This technology has a free trial period, which carries the potential for the disruption of service delivery and inaccurate financial planning.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see <a href = "https://nvd.NIST.gov/vuln/search" target="_blank">https://nvd.NIST.gov/vuln/search</a> for more details.

Architectural Benefits

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

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.
This technology is not portable as it runs only on Red Hat Enterprise Linux (RHEL) platforms.

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

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (09/19/2024)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional 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.11

General Information

Vendor Release Information

Current Decision Matrix (09/19/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework