<Past |
Future> |
1.18.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.20.x |
DIVEST [5, 6, 8, 10, 11] |
DIVEST [5, 6, 8, 10, 11] |
DIVEST [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.24.x |
DIVEST [5, 6, 8, 10, 11] |
DIVEST [5, 6, 8, 10, 11] |
DIVEST [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.26.x |
DIVEST [5, 6, 8, 10, 11] |
DIVEST [5, 6, 8, 10, 11] |
DIVEST [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.27.x |
Unapproved |
Unapproved |
DIVEST [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.28.x |
DIVEST [5, 6, 8, 10, 11] |
DIVEST [5, 6, 8, 10, 11] |
DIVEST [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.29.x |
Approved w/Constraints [5, 6, 8, 10, 11] |
Approved w/Constraints [5, 6, 8, 10, 11] |
DIVEST [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (DIVEST) [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
1.31.x |
Unapproved |
Unapproved |
Approved w/Constraints [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints [5, 6, 8, 10, 11, 12] |
Authorized w/ Constraints [5, 6, 8, 10, 11, 12] |
| | [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 authorized 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] | Kubernetes is only authorized 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`. For more details, the baseline documentation can be accessed via the `Reference` tab.`
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.
Users must ensure that Kubernetes is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500. | | [5] | 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. | | [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 authorized and the user should take the proper steps to decline those installations. | | [7] | 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). | | [8] | 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. | | [9] | 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. | | [10] | 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.
Users must ensure that Kubernetes is implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | [11] | 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). | | [12] | 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. |
|
Note: |
At the time of writing, version 1.31.0 is the most current version, released 08/29/2024.
Please note that the version scheme for kubectl follows the same scheme set for the Kubernetes technology. |