23.0.x |
Approved w/Constraints [8, 9, 11, 12] |
Approved w/Constraints [8, 9, 11, 12] |
Approved w/Constraints [8, 9, 11, 12] |
Approved w/Constraints [8, 9, 12, 13] |
Approved w/Constraints [9, 12, 13, 14] |
Approved w/Constraints [9, 12, 13, 14] |
Approved w/Constraints [9, 12, 13, 14] |
Authorized w/ Constraints [12, 13, 14, 15] |
Authorized w/ Constraints [12, 13, 14, 15] |
Authorized w/ Constraints [12, 13, 14, 15] |
Authorized w/ Constraints [12, 13, 14, 15] |
Authorized w/ Constraints [12, 13, 14, 15] |
| | [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 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). | | [9] | 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:
- This product should be used with a VA authorized container platform that has a developed and authorized baseline configuration with specific hardening guidance regarding the secure implementation of Mirantis Container Runtime. Please reference the TRM for the authorized solution and the Baseline Configuration Management website for more information.
-
System Owners/Administrators should monitor active vulnerabilities and ensure the latest version of the product is being deployed.
| | [11] | 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. | | [12] | 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. | | [13] | 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. | | [14] | 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). | | [15] | 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:
- 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 Mirantis Container Runtime. Please reference the TRM for the approved solution and the Baseline Configuration Management website for more information.
|
|