Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

Mule Runtime

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Mule runtime engine (Mule) is a lightweight integration engine that runs Mule applications and supports domains and policies. Mule applications, domains, and policies share an XML (Extensible Markup Language) DSL (Domain-Specific Language). Mule applications connect systems, services, Application Programming Interfaces (APIs), and devices using API-led connectivity instead of point-to-point integrations. Mule applications provide functionality for message routing, data mapping, orchestration, reliability, security, and scalability. Runtime manager is to deploy and manage mule application on mule runtime engine, where mule runtime is running on Cloudhub or on-premise or on RTF (Rich Text Format). By using runtime manage the user can deploy/undeploy the mule app and can change the runtime version at any time. This technology is available in three editions, Gold, Platinum, and Titanium. This entry covers all three editions. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g., VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e., SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO
Technology/Standard Usage Requirements:	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.
Section 508 Information:	This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.10
Decision Date:	10/02/2024 at 21:47:33 UTC
Aliases:	Mule
Introduced By:	TRM Request
Vendor Name:	Mulesoft

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor Desupport Date
3.3.x	06/26/2012
3.4.x	04/16/2013
3.5.x	05/19/2014
3.6.x	01/14/2015
3.7.x	06/30/2015
3.8.x	09/13/2016	11/16/2021
3.9.x	10/09/2017	09/30/2024
4.1.x	03/21/2018
4.2.x	05/06/2019
4.3.x	04/30/2020
4.4.x	11/01/2022
4.5.x	01/04/2024
4.6.x	02/06/2024
4.7.x	06/04/2024

Current Decision Matrix (09/26/2024)

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

CY2023

CY2024

CY2025

Future>

Release

3.3.x

Unapproved

Authorized w/ Constraints (POA&M)

3.4.x

Unapproved

Authorized w/ Constraints (POA&M)

3.5.x

Unapproved

Authorized w/ Constraints (POA&M)

3.6.x

Unapproved

Authorized w/ Constraints (POA&M)

3.7.x

Unapproved

Authorized w/ Constraints (POA&M)

3.8.x

Unapproved

Authorized w/ Constraints (POA&M)

3.9.x

DIVEST
[18, 20, 21, 22, 23]

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]

Authorized w/ Constraints (POA&M)

4.1.x

Unapproved

Authorized w/ Constraints (POA&M)

4.2.x

Unapproved

Authorized w/ Constraints (POA&M)

4.3.x

DIVEST
[18, 20, 21, 22, 23]

Unapproved

Authorized w/ Constraints (POA&M)

4.4.x

Approved w/Constraints
[18, 20, 21, 22, 23]

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]

Authorized w/ Constraints (DIVEST)
[20, 22, 23, 26, 27, 28]

Authorized w/ Constraints (POA&M)

4.5.x

Unapproved

DIVEST
[20, 22, 23, 25, 26, 27]

DIVEST
[20, 22, 23, 25, 26, 27, 28]

Authorized w/ Constraints (DIVEST)
[20, 22, 23, 26, 27, 28]

Authorized w/ Constraints (POA&M)

4.6.x

Unapproved

Approved w/Constraints
[20, 22, 23, 25, 26, 27]

Approved w/Constraints
[20, 22, 23, 25, 26, 27, 28]

Authorized w/ Constraints (DIVEST)
[20, 22, 23, 26, 27, 28]

4.7.x

Unapproved

Authorized w/ Constraints
[20, 22, 23, 26, 27, 28]

Decision Constraints


[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.

[20]	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. 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 authorized 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-authorized 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.7.3 is the most current version, released 09/01/2024.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.

Name	Description
Anypoint Monitoring Agent	The Anypoint Monitoring Agent reports performance metrics of applications running on-prem to the govcloud, where they can be viewed via built-in as well as custom dashboards by authorized users.
Anypoint Runtime Management Agent	The Anypoint Runtime Manager agent is a Mule runtime engine plug-in that enables communication with Mule runtime engine.
Anypoint Studio	Anypoint Studio is a desktop Integrated Development Environment (IDE) for building and testing Application Programming Interfaces (APIs) and integrations for the Anypoint Platform.
Tracing Module	Tracing module enables users to enhance logs by adding, removing, and clearing all variables from the logging context for a given Mule event. It also enables users to modify the correlation ID during flow execution.


Application Technology Integration Software	Enterprise Service Bus (ESB)

General Analysis

Adoption Benefits

This technology may improve productivity for specific staff through improvements to specialized enterprise service bus (ESB) related tasks.
This technology has a comprehensive set of documentation.
This technology is available at no cost through open-source licensing and supports VA`s open source initiative.

Adoption Risks

This technology relies on Java Runtime Environment (JRE) - Oracle, which has a rapid release and update schedule.
There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see <a href = "https://nvd.NIST.gov/vuln/search" target="_blank">https://nvd.NIST.gov/vuln/search</a> for more details.
IPR/SAR Adoption Risk - The application is not FIPS 140-2 compliant until version 3.5 and does not run in FIPS mode by default. The product is not FIPS 140-2 certified without a third-party module. 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.”
IPR/SAR Adoption Risk - This is a development tool and as such should not be installed in the VA production environment.
IPR/SAR Adoption Risk - Mule ESB supports Java JDK 1.8.0 or JDK 11.
IPR/SAR Adoption Risk - There are published vulnerabilities CVE-2021-1626, CVE-2021-1627 and CVE-2021-1628 for this software that affect version up to 4.2 with CVSS severity of 9.8 (critical).
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
There are other authorized solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.

Architectural Benefits

The technology is portable as it runs on multiple VA-authorized operating systems.
This technology expands VA interoperability with existent VA technologies and solutions.

Architectural Risks

This technology includes cloud-based functionality which has potential information security risks.

- The information contained on this page is accurate as of the Decision Date (10/02/2024 at 21:47:33 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (09/26/2024)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (09/26/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework