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> |
3.3.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.8.x |
DIVEST [4, 5, 9, 11, 12] |
DIVEST [4, 5, 9, 12, 13] |
DIVEST [4, 5, 9, 12, 13] |
DIVEST [4, 5, 9, 12, 13] |
DIVEST [4, 5, 13, 14, 15] |
DIVEST [4, 5, 13, 14, 15] |
DIVEST [4, 5, 13, 14, 16] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.9.x |
DIVEST [4, 5, 9, 11, 12] |
DIVEST [4, 5, 9, 12, 13] |
Approved w/Constraints [4, 5, 9, 12, 13] |
Approved w/Constraints [4, 5, 9, 12, 13] |
Approved w/Constraints [4, 5, 13, 14, 15] |
Approved w/Constraints [4, 5, 13, 14, 15] |
Approved w/Constraints [4, 5, 13, 14, 16] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.1.x |
DIVEST [4, 5, 9, 11, 12] |
DIVEST [4, 5, 9, 12, 13] |
DIVEST [4, 5, 9, 12, 13] |
DIVEST [4, 5, 9, 12, 13] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.2.x |
Approved w/Constraints [4, 5, 9, 11, 12] |
Approved w/Constraints [4, 5, 9, 12, 13] |
DIVEST [4, 5, 9, 12, 13] |
DIVEST [4, 5, 9, 12, 13] |
DIVEST [4, 5, 13, 14, 15] |
DIVEST [4, 5, 13, 14, 15] |
DIVEST [4, 5, 13, 14, 16] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.3.x |
Unapproved |
Unapproved |
Approved w/Constraints [4, 5, 9, 12, 13] |
Approved w/Constraints [4, 5, 9, 12, 13] |
Approved w/Constraints [4, 5, 13, 14, 15] |
Approved w/Constraints [4, 5, 13, 14, 15] |
Approved w/Constraints [4, 5, 13, 14, 16] |
DIVEST [4, 5, 14, 16, 17] |
DIVEST [4, 5, 14, 16, 17] |
DIVEST [4, 5, 14, 17, 18] |
DIVEST [4, 5, 14, 17, 18] |
DIVEST [4, 5, 14, 18, 19] |
4.4.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints (PLANNING/EVALUATION) [1, 4, 5, 14, 16, 17] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 4, 5, 14, 16, 17] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 4, 5, 14, 17, 18] |
Approved w/Constraints (PLANNING/EVALUATION) [1, 4, 5, 14, 17, 18] |
Approved w/Constraints [4, 5, 14, 18, 19] |
4.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.7.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
| | [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] | 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. | | [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 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. | | [5] | 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. | | [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 potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. 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). | | [8] | 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). | | [9] | 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. | | [10] | 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). | | [11] | This technology must use the latest version of Java Runtime Environment (JRE) - Oracle.
Mule 4 Runtime must be configured and enabled to run in a FIPS (Federal Information Processing Standards) 140-2.
There are two requirements to run in FIPS mode:
Have a certified cryptography module installed in your Javaenvironment
Adjust Mule Runtime settings to run in FIPS(Federal Information Processing Standards) security mode
This software must be used in a development environment as applications underdevelopment have not been vetted and may be vulnerable.
| | [12] | 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). | | [13] | This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Mule 4 Runtime must be configured and enabled to run in a FIPS 140-2. There are two requirements to run in FIPS mode:
- Have a certified cryptography module installed in your Java environment.
- Adjust Mule Runtime settings to run in FIPS security mode.
- This utility must be used in a development environment as applications under development have not been vetted and may be vulnerable.
- Ensure a current and supported version of Java is installed to use with Mule ESB at all times.
| | [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 ISO (Information Security Officer) to ensure compliance with VA Handbook 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 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). | | [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 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). | | [17] | This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Mule 4 Runtime must be configured and enabled to run in a FIPS 140-2. There are two requirements to run in FIPS mode:
- Have a certified cryptography module installed in your Java environment.
- Adjust Mule Runtime settings to run in FIPS security mode.
- This tool must be used in a development environment as applications under
development have not been vetted and may be vulnerable..
- Ensure a current and supported version of Java is installed to use with Mule ESB at all times.
- Ensure to use latest version 4.3 and monitor the National Vulnerability
Database for any new security vulnerabilities.
| | [18] | 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). | | [19] | This technology must use the latest TRM-authorized version of Java Runtime Environment (JRE) - Oracle.
Per the Initial Product Review, users must abide by the following constraints:
- Mule 4 Runtime must be configured and enabled to support FIPS 140-2 encryption. There are two requirements to run in FIPS mode:
- Have a certified cryptography module installed in your Java environment.
- Adjust Mule Runtime settings to run in FIPS security mode.
- This tool must be used in a development environment as applications under
development have not been vetted and may be vulnerable..
- Ensure a current and supported version of Java is installed to use with Mule ESB at all times.
- ISSO’s and administrators must monitor the National Vulnerability Database
for any new security vulnerabilities.
|
|
Note: |
At the time of writing, version 4.7.3 is the most current version, released 09/01/2024. |