<Past |
Future> |
1.2 |
Divest [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.6 |
Divest [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.7 |
Divest [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.8 |
Approved w/Constraints [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.11.x |
Approved w/Constraints [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7, 8] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
1.12.x |
Approved w/Constraints [3, 7, 8] |
Approved w/Constraints [3, 7, 8] |
Approved w/Constraints [3, 7, 8] |
Approved w/Constraints [3, 7] |
Approved w/Constraints [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7] |
Divest [3, 7, 9, 10] |
Unapproved |
Unapproved |
Unapproved |
1.13.x |
Approved w/Constraints [3, 7, 8] |
Approved w/Constraints [3, 7, 8] |
Approved w/Constraints [3, 7, 8] |
Approved w/Constraints [3, 7] |
Approved w/Constraints [3, 7] |
Approved w/Constraints [3, 7] |
Approved w/Constraints [3, 7] |
Approved w/Constraints [3, 7] |
Divest [3, 7, 9, 10] |
Divest [3, 7, 9, 10] |
Unapproved |
Unapproved |
19.03.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [3, 7, 9, 10] |
Divest [3, 7, 9, 10] |
Divest [3, 7, 10, 11] |
Divest [3, 7, 10, 11] |
20.10.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [1] | Cloud versions of this product are not permitted without a waiver from the Architecture and Engineering Review Board (AERB) and expressed authorization. Product must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines. | | [2] | Cloud versions of this product are not permitted without a waiver from the Architecture and Engineering Review Board (AERB) and expressed authorization. | | [3] | 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. | | [4] | 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. | | [5] | As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.
| | [6] | Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review. | | [7] | 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. | | [8] | 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). | | [9] | Due to potential information security risks, Software as a Service/ Platform as a Service (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.
The baseline for Docker EE is currently in development. It is not recommend that this software be used in production by new projects until the baseline is completed. However, projects that have already implemented this technology under prior TRM approvals are responsible for proper security configuration until a baseline is released.
Docker EE must only be installed on TRM-approved platforms.
Docker Enterprise Edition Advanced is the recommended subscription level for users to leverage the full suite of capabilities.
The VA must closely monitor the vendor’s website to keep pace with the frequent critical updates and version releases.
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 | | [10] | 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). | | [11] | Due to potential information security risks, Software as a Service/ Platform as a Service (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.
Docker Enterprise Edition Advanced is the recommended subscription level for users to leverage the full suite of capabilities.
The VA must closely monitor the vendor’s website to keep pace with the frequent critical updates and version releases.
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 |
|
Note: |
At the time of writing, version 20.10.11 is the most current version and was released 11/17/2021. Please see constraints on new production deployments after 1/31/2020. |