12.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Approved w/Constraints [1, 2, 3, 4, 5, 6] |
Approved w/Constraints [1, 2, 3, 4, 6, 7] |
Approved w/Constraints [1, 2, 3, 4, 6, 7] |
Approved w/Constraints [1, 2, 3, 4, 6, 7] |
Approved w/Constraints [1, 2, 3, 4, 6, 7] |
| | [1] | This technology can be implemented with Kubernetes. At the time of writing, Kubernetes is limited to on premises VA Enterprise Cloud implementations on Amazon Web Services (AWS) Servers. Other uses of this technology are unapproved.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
Users must ensure that VMware vSphere, Apache Hypertext Transfer Protocol (HTTP) Server, and Kubernetes are implemented with VA-approved baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’)
Users must not utilize Docker Compose, as it is at the time of writing, unapproved in the TRM. | | [2] | 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. | | [3] | 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. | | [4] | In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process. | | [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 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. | | [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, visit the Product Marketplace.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). |
|