Helm

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:	Helm is free, open source software that allows users to manage Kubernetes applications and define, install, and upgrade Kubernetes applications. This software does not utilize a database to store information and instead stores it on the local workstation. 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.2
Decision Date:	02/15/2024 at 23:04:10 UTC
Introduced By:	TRM Request
Vendor Name:	Cloud Native Computing Foundation

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
2.16.x	11/12/2019
3.0.x	11/14/2019
3.2.x	04/22/2020
3.3.x	08/11/2020
3.8.x
3.9.x	05/18/2022
3.10.x	09/21/2022
3.11.x	01/18/2023
3.12.x	05/10/2023
3.13.x	09/27/2023
3.14.x	01/17/2024

Current Decision Matrix (02/12/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

CY2026

CY2027

CY2028

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

2.16.x

Unapproved

3.0.x

Unapproved

3.2.x

Unapproved

3.3.x

Unapproved

3.8.x

Unapproved

3.9.x

Unapproved

3.10.x

Unapproved

3.11.x

Unapproved

3.12.x

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

3.13.x

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

3.14.x

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

Decision Constraints


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

[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]	Per the Initial Product Review, users must abide by the following constraints: Ensure to leverage use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data on servers and workstations that utilize Helm where applicable. Helm is an application manager for Kubernetes. Kubernetes is currently in a divest status on the One-VA TRM pending the development of a secure configuration baseline. The product is an open source solution. While Helm does release updates to their platform, relying on community support may result in slow response times and non-timely patches. This product should be used with a VA approved container platform that has a developed and approved baseline configuration with specific hardening guidance regarding the secure implementation of Helm. Currently Kubernetes, Docker, and OpenShift are container products VA is evaluating. Please reference the TRM for the approved solution and the Baseline Configuration Management website for more information. System owners should use the latest version of the software and check for updates regularly. Using older versions of Helm could allow unauthorized access noted in active CVE’s.

[4]	This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations. Per the Initial Product Review, users must abide by the following constraints: Ensure to leverage use of a FIPS 140-2 validated cryptographic module to secure VA sensitive data on servers and workstations that utilize Helm where applicable. Helm is an application manager for Kubernetes. Kubernetes is only approved with constraints in VA Enterprise Cloud (VAEC) Amazon Web Services (AWS) instances that abide by the configuration and system architecture outlined in the `Kubernetes v1.x for AWS Configuration Baseline`. Any implementations outside of this baseline configuration are expressly unapproved until a secure configuration baseline is developed that covers all on-premise deployments of this technology. The product is an open source solution. While Helm does release updates to their platform, relying on community support may result in slow response times and non-timely patches. System owners should use the latest version of the software and check for updates regularly. Using older versions of Helm could allow unauthorized access noted in active CVE’s.

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

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

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

[8]	This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations. Per the Initial Product Review, users must abide by the following constraints: Helm will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing PHI/PII or VA sensitive information. Helm is an application manager for Kubernetes. This product should be used with a VA approved container platform that has a developed and approved baseline configuration with specific hardening guidance regarding the secure implementation of Helm. Please reference the TRM for the approved solution and the Baseline Configuration Management website for more information. Users should check with their supervisor, 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. System owners should use the latest version of this product and monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities.

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

[10]	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 3.14.0 is the most current version and was released on 01/17/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	Build and Deployment Tools

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This is a well-documented technology.
This technology is available at no cost through open source licensing and supports VA’s open source initiative.
This technology may improve productivity for specific staff whose responsibilities include development.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.nist.gov/vuln/search/ for more details.
Due to the rapid release schedule of this product, 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 product is not Federal Information Processing Standards (FIPS) 140-2 certified.
Helm is an application manager for Kubernetes.
There are published vulnerabilities that affect versions prior to 3.11.1 of this software.
This technology can be implemented with Kubernetes. At the time of writing, Kuebernetes is limited to on premises VA Enterprise Cloud implementations on Amazon Web Services (AWS) Servers. Other uses of this technology are unapproved.
As open-source, this technology may be without clearly defined support options which may result in suboptimal enterprise level support.

Architectural Benefits

This technology is portable across several VA approved platforms.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

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 (02/12/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:

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 (02/12/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:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES