| 3.7.x |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints
[1, 10, 13, 14, 15, 16, 17] |
| | | | [1] | This Technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. | | | [2] | Per the Initial Product Review, users must abide by the following constraints:
- 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. This software must not be used in production until the baseline is completed.
- 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 | | | [3] | 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. | | | [4] | 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). | | | [5] | 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. | | | [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] | 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 (PSF) team, please use their online form.
(Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [8] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations.
Per the Initial Product Review, users must abide by the following constraints:
- 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.
-
There is no Secure Configuration Baseline for MKE currently in development. This software should not be used in production until the baseline is completed.
- MKE must only be installed on TRM approved platforms.
- 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 and must have an approved 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 | | | [9] | 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. | | | [10] | 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. | | | [11] | 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). | | | [12] | 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. | | | [13] | 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. | | | [14] | 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. | | | [15] | 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). | | | [16] | If free trialware is utilized, the software must be purchased or removed at the end of the trial period.
This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations.
Per the Initial Product Review, users must abide by the following constraints:
- Due to potential information security risks, SaaS/PaaS solutions must complete
the Business Integration and Outcomes Service (BIOS) 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.
- There is no Secure Configuration Baseline for MKE currently in development.
This software should not be used in production until the baseline is completed.
- MKE must only be installed on TRM approved platforms.
- OpenShift is the VA approved solution and has a VA baseline developed from
the DISA STIG as well as continuous monitoring of the controls. Mirantis
Kubernetes Engine will need the same, but that will be the system owner’s
responsibility to develop a system level baseline.
| | | [17] | Use of this product is limited to laboratory and development test systems only. Only non-production data should be used to test and develop systems that have not undergone Assessment and Authorization (A&A). Systems under development should not process live data or perform any real time processing, and not be attached to VA networks without first being assessed and authorized. |
|
