| 5.x |
Unapproved |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
Approved w/Constraints
[2, 3, 4, 6, 8, 9] |
| | | | [1] | Users must not utilize Docker Engine (Community), as it is at the time of writing, unapproved in the TRM.
Users must not utilize Windows Subsystem for Linux (WSL), as it is at the time of writing, unapproved in the TRM.
Users must ensure that Kubernetes is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) | | | [2] | 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. | | | [3] | 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. | | | [4] | 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. | | | [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] | 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. | | | [7] | 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. | | | [8] | 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). | | | [9] | Users must not utilize Docker Engine (Community), as it is at the time of writing, unapproved in the TRM.
Users must not utilize Windows Subsystem for Linux (WSL), as it is at the time of writing, unapproved in the TRM.
Users must ensure that Kubernetes is implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Per the Initial Product Review, users must abide by the following constraints:
- The product uses certified encryption (NIST CERT #3538, #3565, #3571) for FIPS 140-2 compliance which is in a historical status. The NIST website states:
The referenced cryptographic module should not be included by Federal Agencies in new procurements. Agencies may make a risk determination on whether to continue using this module based on their own assessment of where and how it is used.
- Windows Subsystem for Linux is unapproved on the VA Technical Reference Model (TRM); therefore, Podman must not be used on Windows operating systems.
- The product is a container solution used for developing, managing, and running Open Container Initiative (OCI) containers and container images and currently
does not have an approved baseline within the VA. Container solutions with an approved baseline should be used.
- The VA requires support for all software used on the VA network. Vendor or third-party support at an enterprise level is not free and must be acquired for
any open-source product to be deployed on the VA network. Support for Podman is offered through the Podman community’s Slack and IRC channel,
Podman mailing list. Additionally, Red Hat states that “Support for Podman is included as part of a RHEL subscription as it’s a component of the operating system.”
|
|
