Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.9

Hibernate Object/Relational Mapping (ORM)

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:	Hibernate Object/Relational Mapping (ORM) enables the development of persistent classes following natural object-oriented idioms, including inheritance, polymorphism, association, composition, and the Java collections framework. Hibernate ORM requires no interfaces or base classes for persistent classes and enables any class or data structure to be persistent. This technology also provides data query and retrieval facilities. Hibernate ORM generates SQL calls and relieves the developer from manual handling and object conversion of the result subset. This technology contains portability functionality for a plethora of databases, to include: Microsoft Structured Query Language (SQL) Server, Oracle, MySQL, PostgreSQL, CockroachDB, MariaDB, Firebird, H2, and HyperSQL databases. Hibernate ORM is not dependent on a database for use; rather, this technology provides functionality to port data to and integrate with these databases if needed.
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 System Security Officer (ISSO), 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 not been assessed by the Section 508 Office. 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.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v25.7
Decision Date:	07/30/2025 at 03:04:30 UTC
Aliases:	Hibernate Core; Hibernate
Introduced By:	Extended Tool List (ETL)
Vendor Name:	Hibernate

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.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date
3.2
3.2.3	01/02/2007
3.2.4	01/09/2007
3.2.5	01/31/2007
3.2.6	01/07/2008
3.3.0	01/15/2008
3.3.2	06/24/2009
3.5	03/31/2010
3.6	10/14/2010
4.0	12/15/2011
4.1	02/09/2012
4.2	03/18/2013	10/23/2015
4.3	12/16/2013	08/05/2015
5.0.x	08/20/2015	01/19/2017
5.1.x	02/10/2016	11/28/2018
5.2.x	06/02/2016	11/16/2018
5.3.x	08/28/2018
5.4.x	12/12/2018	12/16/2021
5.5.x	06/02/2021	12/16/2021
5.6.x	10/13/2021
6.0.x	03/31/2022
6.1.x	06/07/2022	02/07/2023
6.2.x	12/22/2022
6.3.x	08/31/2023	09/19/2023
6.4.x	11/23/2023
6.5.x	04/25/2024	05/20/2024
6.6.x	08/08/2024
7.0.x	05/19/2025

Current Decision Matrix (07/22/2025)

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 System Security Officer (ISSO), 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.2

Unapproved

Authorized w/ Constraints (POA&M)

3.2.3

Unapproved

Authorized w/ Constraints (POA&M)

3.2.4

Unapproved

Authorized w/ Constraints (POA&M)

3.2.5

Unapproved

Authorized w/ Constraints (POA&M)

3.2.6

Unapproved

Authorized w/ Constraints (POA&M)

3.3.0

Unapproved

Authorized w/ Constraints (POA&M)

3.3.2

Unapproved

Authorized w/ Constraints (POA&M)

3.5

Unapproved

Authorized w/ Constraints (POA&M)

3.6

Unapproved

Authorized w/ Constraints (POA&M)

4.0

Unapproved

Authorized w/ Constraints (POA&M)

4.1

Unapproved

Authorized w/ Constraints (POA&M)

4.2

Unapproved

Authorized w/ Constraints (POA&M)

4.3

Unapproved

Authorized w/ Constraints (POA&M)

5.0.x

Unapproved

Authorized w/ Constraints (POA&M)

5.1.x

Unapproved

Authorized w/ Constraints (POA&M)

5.2.x

Unapproved

Authorized w/ Constraints (POA&M)

5.3.x

Unapproved

Authorized w/ Constraints (POA&M)

5.4.x

DIVEST
[10, 11, 12, 13, 14, 15]

Unapproved

Authorized w/ Constraints (POA&M)

5.5.x

DIVEST
[10, 11, 12, 13, 14, 15]

Unapproved

Authorized w/ Constraints (POA&M)

5.6.x

Approved w/Constraints
[10, 11, 12, 13, 14, 15]

Approved w/Constraints
[10, 11, 12, 13, 14, 16]

DIVEST
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints
[10, 11, 13, 14, 16, 18, 19]

6.0.x

Unapproved

DIVEST
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 18, 19]

6.1.x

Unapproved

DIVEST
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 18, 19]

6.2.x

Approved w/Constraints
[10, 11, 12, 13, 14, 15]

Approved w/Constraints
[10, 11, 12, 13, 14, 16]

DIVEST
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 18, 19]

6.3.x

Unapproved

DIVEST
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 18, 19]

6.4.x

Unapproved

DIVEST
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 18, 19]

6.5.x

Unapproved

DIVEST
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints (DIVEST)
[10, 11, 13, 14, 16, 18, 19]

6.6.x

Unapproved

Approved w/Constraints
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints
[10, 11, 13, 14, 16, 17, 18]

Authorized w/ Constraints
[10, 11, 13, 14, 16, 18, 19]

7.0.x

Unapproved

Authorized w/ Constraints (POA&M)

Authorized w/ Constraints
[10, 11, 13, 14, 16, 18, 19]

Note:

At the time of writing, version 7.0.6 is the most current version, released 07/12/2025.

Decision Constraints


[10]	This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details.

[11]	If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details.

[12]	Users must not utilize the Cockroach Database (CockroachDB), Maria Database (MariaDB) Server, Firebird, H2 Database Engine, and Hyper Structured Query Language (HyperSQL) Database technologies, as they are unapproved for use on the TRM. Users must ensure that My Structured Query Language (MySQL) Database and Oracle Database are implemented with VA-authorized baselines. (Refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle. Per the Initial Product Review, users must abide by the following constraints: Hibernate ORM will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. Thorough code review must be performed to ensure SQL injection vulnerabilities are remediated or mitigated. Developers may leverage the Hibernate Guidelines document in OWASP for best practices.

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

[15]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[16]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

[17]	Users must not utilize the Maria Database (MariaDB) Server, Firebird, H2 Database Engine, and Hyper Structured Query Language (HyperSQL) Database technologies, as they are unapproved for use on the TRM. This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle. Per the Initial Product Review, users must abide by the following constraints: Hibernate ORM will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. Thorough code review must be performed to ensure SQL injection vulnerabilities are remediated or mitigated. Developers may leverage the Hibernate Guidelines document in OWASP for best practices.

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

[19]	Users must not utilize the Maria Database (MariaDB) Server, Firebird, H2 Database Engine, and Hyper Structured Query Language (HyperSQL) Database technologies, as they are unapproved for use on the TRM. This technology must use the latest TRM-authorized version of Java Development Kit (JDK) - Oracle. Per the Initial Product Review, users must abide by the following constraints: Hibernate ORM will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. Thorough code review must be performed to ensure SQL injection vulnerabilities are remediated or mitigated. Developers may leverage the Hibernate Guidelines document in OWASP for best practices. Users must ensure that only VA TRM authorized databases are implemented with VA-authorized baselines. 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. 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 that 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. Ensure that the latest stable version of Hibernate Object Relational Mapping is used. Additionally, Hibernate Object Relational Mapping should be added to the list of applications for continuous monitoring for published vulnerabilities, updates, and patches. ISSO’s and administrators must monitor the National Vulnerability Database for any new security vulnerabilities. OMB Memorandum M-22-18,” Enhancing the Security of the Software Supply Chain through Secure Software Development Practices,” and OMB Memorandum M-23-16, “Update to Memorandum M-22-18,” limit agencies’ ability to use software that is not developed using secure practices. The attestation form will allow software producers to confirm that they follow those practices. VA Supply Chain Risk Management (SR) Policy and VA Handbook 6500.6, Contract Security, Appendix C states that the contractor (including producers and resellers) shall comply with Office of Management and Budget (OMB) M-22-18 and M-23-16 when using third-party software on VA information systems or otherwise affecting the VA information. This includes new software purchases and software renewals for software developed or modified by major version change after the issuance date of M-22-18 (September 14, 2022).

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
Hibernate Annotations	This module consists of metadata that governs the transformation of data between the object-oriented model and the relational database model.
Hibernate EntityManager	This module, together with Hibernate Annotations, is a wrapper that implements a Java Persistence Application Programming Interface (API) persistence solution on top of Hibernate.
Hibernate Open Service Gateway Initiative (Hibernate-OSGi)	This module is Hibernate`s support for running in Open Service Gateway Initiative (OSGi) containers.
Hibernate-C3P0	This module integrates the C3P0 connection pooling library into Hibernate.
Hibernate-Core	This module defines its ORM features and application programming interfaces (APIs) as well as the various integration Serial Peripheral Interfaces (SPIs).
Hibernate-Ehcache	This module integrates Ehcache caching library into Hibernate as a second-level cache provider.
Hibernate-Envers	This module is Hibernate`s historical entity versioning feature.
Hibernate-HikariCP	This module integrates the HikariCP connection pooling library into Hibernate.
Hibernate-Infinispan	This module integrates Infinispan caching library into Hibernate as a second-level cache provider.
Hibernate-JCache	This module integrates the JCache caching specification into Hibernate, enabling any compliant implementation to become a second-level cache provider.
Hibernate-Jpamodelgen	This module provides an annotation processor to generate JPA 2 static metamodel classes.
Hibernate-Spatial	This module is Hibernate`s Spatial/ Geospatial Information System (GIS) data type support.
Hibernate-Testing	This module provides support for testing Hibernate Object/Relational Mapping (ORM) functionality.


Information Management Technologies Data Integration	Extract, Transform, Load (ETL)
Information Management Technologies Data Management	Database Connectivity
Information Management Technologies Data Management	Database-Related Management Tools

General Analysis

Adoption Benefits

This technology is available at no cost through open-source licensing and supports VA's open-source initiative.
At the time of writing, there are a limited number of TRM options providing this functionality. The addition of this technology will provide end users with multiple viable options.
This technology may improve productivity for specific staff whose responsibilities include object-oriented coding and development.
This technology has a comprehensive set of documentation.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
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.
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.
This technology relies on Java Development Kit (JDK) - Oracle, which has a rapid release and update schedule.
This technology can integrate with and alter database technologies.
This product can be configured with a MySQL Commercial Edition Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms.
This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms.
This technology can potentially use Maria Database (MariaDB) Server, an unapproved technology.
This technology can potentially use Firebird, an unapproved technology.
This technology can potentially use H2 Database Engine, an unapproved technology.
This technology can potentially use Hyper Structured Query Language (HyperSQL) Database, an unapproved technology.
IPR/SAR Adoption Risk - Hibernate Object Relational Mapping is not Federal Information Processing Standards (FIPS) 140-2 (or its successor) certified.
IPR/SAR Adoption Risk - Hibernate Object Relational Mapping layers are known to be susceptible to SQL injection.
IPR/SAR Adoption Risk - Hibernate Object Relational Mapping supports database technologies that are unauthorized for use on the TRM, i.e. Cockroach Database (CockroachDB), Maria Database (MariaDB) Server, Firebird, H2 Database Engine, and Hyper Structured Query Language (HyperSQL).
IPR/SAR Adoption Risk - Hibernate Object Relational Mapping is not a cloud technology, but it is an object-relational mapping (ORM) framework for Java that can be used in cloud environments.
IPR/SAR Adoption Risk - Hibernate Object Relational Mapping is an open-source framework.
IPR/SAR Adoption Risk - TRM authorized versions of Hibernate Object Relational Mapping v6.4.x and v6.6.x are currently in limited support mode, meaning that it is not actively being developed with major features or bug fixes unless they are considered significant or arise in the context of paid support. TRM versions of Hibernate Object Relational Mapping v.6.5.x and v6.3.x and earlier have all reached End-of-Life and should not be used in the VA network.
IPR/SAR Adoption Risk - Hibernate does not provide a Secure Software Development Attestation Form for Hibernate Object Relational Mapping.

Architectural Benefits

This technology supports AES Encryption.
This technology can use a VA-preferred database.
This technology is portable as it runs on multiple TRM-authorized operating systems.
This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

- The information contained on this page is accurate as of the Decision Date (07/30/2025 at 03:04:30 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.9

General Information

Vendor Release Information

Current Decision Matrix (07/22/2025)

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 25.9

General Information

Vendor Release Information

Current Decision Matrix (07/22/2025)

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

EMAIL UPDATES

VA Categories

View the VA Categorization Framework