Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to,
VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information
Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users
should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology
(OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation. |
The VA Decision Matrix displays the current and future VAIT
position regarding different releases of a TRM entry. These decisions are
based upon the best information available as of the most current date. The consumer of this information has the
responsibility to consult the organizations responsible for the desktop, testing, and/or production environments
to ensure that the target version of the technology will be supported.
|
|
Legend: |
White |
Authorized: The technology/standard has been authorized for use.
|
Yellow |
Authorized w/ Constraints: The technology/standard can be used within the specified constraints located
below the decision matrix in the footnote[1] and on the General tab.
|
Gray |
Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by
the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee
and based upon a recommendation from the POA&M Compliance Enforcement,
has been granted to the project team or organization that wishes to use the technology.
|
Orange |
Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard.
As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of
the technology/standard. Additional information on when the entry is projected to become unauthorized may be
found on the Decision tab for the specific entry.
|
Black |
Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
|
Blue |
Authorized w/ Constraints (PLANNING/EVALUATION): The period of time 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. If a customer would like to use this technology, please work with
your local or Regional OI&T office and contact the appropriate evaluation office
displayed in the notes below the decision matrix. The Local or Regional OI&T
office should submit an
inquiry to the TRM
if they require further assistance or if the evaluating office is not listed in the notes below.
|
|
Release/Version Information: |
VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.
|
For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision
would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.
|
VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than
what is specified but is not to exceed or affect previous decimal places.
|
For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401
is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.
|
Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M). |
<Past |
Future> |
2.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
3.0.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
3.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
3.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
3.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
3.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
3.5.x |
Approved w/Constraints (PLANNING/EVALUATION) [1, 8, 10, 13, 14, 15] |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
3.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
3.7.x |
Unapproved |
Approved w/Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Authorized w/ Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Authorized w/ Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Authorized w/ Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Authorized w/ Constraints (PLANNING/EVALUATION) [1, 10, 13, 14, 15, 16, 17] |
Authorized w/ Constraints (PLANNING/EVALUATION) [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 authorized 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 authorized for Development and Test systems usage. Production system use of this technology is considered TRM unapproved must have an authorized 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 authorized 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 authorized for Development and Test systems usage. Production system use of this technology is considered TRM unapproved and must have an authorized 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 authorized 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 authorized 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 authorized platforms.
- OpenShift is the VA authorized 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. |
|
Note: |
At the time of writing, version 3.7.9 is the most current version, released.
Note: This is only authorized for Development and Test Environments at this time. Please visit the recommended constraints via the `Analysis` tab for more information. |