<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 |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
3.9.x |
Divest [18, 20, 21, 22, 23] |
Divest [18, 21, 22, 23, 24, 25] |
Divest [18, 21, 22, 23, 24, 25] |
Divest [18, 22, 23, 24, 25, 26] |
Divest [20, 22, 23, 25, 26, 27] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.1.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.2.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.3.x |
Divest [18, 20, 21, 22, 23] |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
4.4.x |
Approved w/Constraints [18, 20, 21, 22, 23] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 21, 22, 23, 24, 25] |
Approved w/Constraints [18, 22, 23, 24, 25, 26] |
Divest [20, 22, 23, 25, 26, 27] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Unapproved |
Unapproved |
4.5.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Divest [20, 22, 23, 25, 26, 27] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Divest [20, 22, 23, 25, 26, 27, 28] |
Unapproved |
Unapproved |
4.6.x |
Unapproved |
Unapproved |
Unapproved |
Unapproved |
Approved w/Constraints [20, 22, 23, 25, 26, 27] |
Approved w/Constraints [20, 22, 23, 25, 26, 27, 28] |
Approved w/Constraints [20, 22, 23, 25, 26, 27, 28] |
Approved w/Constraints [20, 22, 23, 25, 26, 27, 28] |
Approved w/Constraints [20, 22, 23, 25, 26, 27, 28] |
Approved w/Constraints [20, 22, 23, 25, 26, 27, 28] |
Approved w/Constraints [20, 22, 23, 25, 26, 27, 28] |
Approved w/Constraints [20, 22, 23, 25, 26, 27, 28] |
| | [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 approved 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-approved 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-approved 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-approved 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.
| | [20] | This technology must use the latest TRM-approved 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.
- Vendor documentations also states the following: “By default, Government Cloud is configured for FIPS 140-2, so you do not need to
perform the noted steps if you are using Government Cloud.”
- 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.
| | [21] | 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. | | [22] | 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. | | [23] | 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. | | [24] | This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle.
Mule Runtime is not Federal Information Processing Standards (FIPS) 140-2 certified. This technology will require third party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information
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.
- Vendor documentations also states the following: “By default, Government Cloud is configured for FIPS 140-2, so you do not need to
perform the noted steps if you are using Government Cloud.”
- 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.
| | [25] | 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. | | [26] | 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. | | [27] | 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). | | [28] | The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website. |
|
Note: |
At the time of writing, version 4.6.3 is the most current version, released 05/07/2024. |