| 1.28.x |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
Approved w/Constraints
[10, 12, 13, 14, 15, 16] |
| | | | [1] | Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [2] | 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. | | | [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 ISO can provide assistance in reviewing the NIST vulnerabilities. | | | [4] | Based on the IPR findings from Security Engineering and pending required VA security policy guidance from OIS DevSecOps on container and orchestrator technology, this technology is only approved for Development and Test systems usage. Production system use of this technology is considered TRM unapproved must have an approved TRM waiver to accept the risks of using this technology in production without required policy and configuration standards. This constraint will be revisited after VA determines relevant policy and creates configuration standard(s). See the reference section and the Baseline Configuration Management website for more information: https://vaww.vashare.oit.va.gov/sites/itops/svcs/sma/BCM/Pages/BCM.aspx
Per the Initial Product Review, users must abide by the following constraints:
- Kubernetes should not be used until the VA develops a container strategy and establishes an enterprise orchestration solution.
- Kubernetes should not be used to process, store, or transmit VA sensitive information.
- This technology is currently unapproved due to VA standardization and the lack of a required VA baseline. In order to reduce costs, risk and overhead in many areas including: training, patching, configuration standards, and documentation, VA has standardized the types and configurations of the platforms/technologies it uses and maintains baselines for in its internal operating environment.
Without a published DISA STIG or NIST validated checklist, creating a baseline requires substantial effort and significant time and cost. The project team will require written vendor commitment for assistance and continued vendor support and a VA Subject Matter Expert (SME) point of contact with a signed Baseline ownership Memorandum of Understanding (MOU). To begin exploring baseline creation, the project team requesting to use this technology must submit a request for a new product or technology review to Solution Delivery, Security Engineering via the following link:
https://vaww.portal2.va.gov/sites/infosecurity/ess/Lists/Request%20New%20ProductTechnology%20Review/AllItems.aspx
Security Engineering will work with the project team and the SD Baseline and Configuration Management (BCM) team to identify the appropriate foundational checklist (e.g. DISA SRG, DISA STIG, or NIST Validated Checklist) to use as a basis for the VA security controls checklist. Once provided, the project team will be responsible for working with the product vendor to complete the checklist with special emphasis on VA Check Content and VA Fix text columns with specific commands related to the product.
- Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).
- Open source software may be obtained at no cost. 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 Kubernetes is offered through vendors designated as Kubernetes Certified Service Providers, the Kubernetes community forum, and Kubernetes’ Slack channel.
| | | [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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [6] | 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 Project Special Forces (SPF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [7] | 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`. For more details, the baseline documentation can be accessed via the `Reference` tab.
Per the Initial Product Review, the following constraints are applied for use of this technology outside of the baselined VAEC AWS environment:
- Kubernetes should not be used. Baselines are available for approved products that should be used as an orchestration solution.
- Kubernetes should not be used to process, store, or transmit VA sensitive information.
- This technology is currently unapproved due to VA standardization and the lack of a required VA baseline. In order to reduce costs, risk and overhead in many areas including: training, patching, configuration standards, and documentation, VA has standardized the types and configurations of the platforms/technologies it uses and maintains baselines for in its internal operating environment.
The project team will require written vendor commitment for assistance and continued vendor support and a VA Subject Matter Expert (SME) point of contact. To begin exploring the creation of an implementation standard, the project team, requesting to use this technology, must submit a Baseline Configuration Management (BCM) SNOW intake request via the following link: https://yourit.va.gov/va?id=sc_cat_item&sys_id=4894aef0dbedc0949b1534cc7c961902
Once the request is received, it will be reviewed by the Baseline Configuration Management Team (BCM) led by Solution Delivery. BCM will determine whether a baseline/standard is warranted and if approved for development, the group will assign ownership and establish a plan for development, testing, and compliance monitoring.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non-AWS/Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by PSF.
- Open source software may be obtained at no cost. 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 Kubernetes is offered through vendors designated as Kubernetes Certified Service Providers, the Kubernetes
community forum, and Kubernetes’ Slack channel.
| | | [8] | 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 ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. | | | [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 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). | | | [10] | 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. | | | [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] | 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. | | | [13] | 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. | | | [14] | 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`. For more details, the baseline documentation can be accessed via the `Reference` tab.
Per the Initial Product Review, the following constraints are applied for use of this technology outside of the baselined VAEC AWS environment:
- Ensure that the latest stable version of Kubernetes is used. Additionally,Kubernetes must be added to the list of applications for continuous monitoring for published vulnerabilities, updates, and patches. ISSO’s and administrators must monitor the CVE Details website for any new security vulnerabilities.
- Kubernetes will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information.
- Kubernetes should only be used on a VA approved AWS platform. For use on any other platform the project team will require written vendor
commitment for assistance and continued vendor support and a VA Subject Matter Expert (SME) point of contact. To begin exploring the creation of an implementation standard, the project team, requesting to use this technology, must submit a Baseline Configuration Management (BCM) SNOW intake request via the following link:
https://yourit.va.gov/va?id=sc_cat_item&sys_id=4894aef0dbedc0949b1534cc
7c961902
Once the request is received, it will be reviewed by the Baseline Configuration Management Team (BCM) led by Solution Delivery. BCM will determine whether a baseline/standard is warranted and if approved for development, the group will assign ownership and establish a plan for development, testing, and compliance monitoring.
- Due to potential information security risks, SaaS/PaaS solutions must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Digital Transformation Center (DTC), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO), and stakeholders determines the SaaS/PaaS category during the Discovery Phase. All SaaS and Non AWS or Azure (VAEC) PaaS assets are routed to EPMO IA for Analysis and Approval to Operate (ATO) with technical oversight, acquisition, production, and sustainment provided by DTC.
- Open source software may be obtained at no cost. 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 Kubernetes is offered through vendors designated as Kubernetes Certified Service Providers, the Kubernetes community forum, and Kubernetes’ Slack channel. Open source software may be obtained at no cost. 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 Kubernetes is offered through vendors designated as Kubernetes Certified Service Providers, the Kubernetes
community forum, and Kubernetes’ Slack channel.
| | | [15] | 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. | | | [16] | 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). |
|
