Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.9

eXtended Relationship Management (XRM) Toolbox

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:	eXtended Relationship Management (XRM) ToolBox is an open source Windows utility that connects to Microsoft Dynamics 365 Customer Relationship Management (CRM), providing technology for customization, configuration and operation tasks.
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.8
Decision Date:	08/28/2025 at 14:46:07 UTC
Aliases:	Xrm ToolBox
Introduced By:	TRM Request
Vendor Name:	XrmToolBox

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	Vendor Desupport Date
1.2018.x	10/24/2018
1.2020.x	02/12/2020
1.2021.x	02/20/2021
1.2022.x	02/23/2022
1.2023.x	02/01/2023
1.2024.x	09/21/2024
1.2025.x	05/30/2025

Current Decision Matrix (08/26/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

CY2024

CY2025

CY2026

Future>

Release

1.2018.x

Unapproved

Authorized w/ Constraints (POA&M)

1.2020.x

Unapproved

Authorized w/ Constraints (POA&M)

1.2021.x

Unapproved

Authorized w/ Constraints (POA&M)

1.2022.x

DIVEST
[2, 9, 11, 12, 13, 14]

Unapproved

Authorized w/ Constraints (POA&M)

1.2023.x

Approved w/Constraints
[2, 9, 11, 12, 13, 14]

Authorized w/ Constraints (DIVEST)
[2, 11, 12, 13, 14, 15, 16]

Authorized w/ Constraints (DIVEST)
[2, 11, 12, 13, 14, 16, 17]

Authorized w/ Constraints (POA&M)

1.2024.x

Unapproved

Authorized w/ Constraints
[2, 11, 12, 13, 14, 15, 16]

Authorized w/ Constraints (DIVEST)
[2, 11, 12, 13, 14, 16, 17]

1.2025.x

Unapproved

Authorized w/ Constraints (POA&M)

Authorized w/ Constraints
[2, 11, 12, 13, 14, 16, 17]

Note:

At the time of writing, version 1.2025.7.71 is the most current version and was released 05/30/2025.

Decision Constraints


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

[9]	Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.

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

[12]	In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004 , VA Directive 6517, and VA Directive 6513. The local ISSO (Information System Security Officer) can advise on the ESCCB review process.

[13]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an authorized VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. 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 and National Institute of Standards and Technology (NIST) standards. As of January 27th, 2017, Risk-based Decisions (RBD) will be handled per VAIQ # 7769667. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. The local ISSO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place.

[14]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[15]	Users must not utilize the Secure Sockets Layer (SSL) protocol, as it requires a POA&M.

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

[17]	Users must not utilize the Secure Sockets Layer (SSL) protocol, as it requires a POA&M. Per the Security Assessment Review, users must abide by the following constraints: A vulnerability exists because XrmToolBox v1.x supports third-party plugins/tools, many authored by community developers without formal security vetting. To mitigate, restrict to approved plugin/tool sources and enforce code signing where possible. A vulnerability exists because XrmToolBox v1.x connects to and makes use of multiple cloud-based services. To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated. A vulnerability exists because XrmToolBox v1.x collects anonymous statistics. To mitigate, administrators shall restrict this feature. A registry key can be created to block the execution of the data collection. A vulnerability exists because XrmToolBox v1.x installs an outdated (v5.3.0.0) NuGet package Microsoft.IdentityModel.Clients.ActiveDirectory. This package has been deprecated as it is legacy and is no longer maintained. To mitigate, users must work with the vendor to have this package replaced with one that is fully supported. See the NuGet Package Listing for this package for suggested alternatives and migration instructions. A vulnerability exists because XrmToolBox v1.x installs an outdated (v6.1.7601.24479) Microsoft.Identity extension for .Net. According to the Project’s website IdentityModel 6.x is deprecated and support ended May 2024. To mitigate, users must work with the vendor to validate this vulnerability. If it is valid, the extension must be upgraded to a supported version following the recommendations on the project’s website. A vulnerability exists because XrmToolBox v1.x provides automatic/user configurable checks for updates. To mitigate, it is recommended that the administrator disable automatic update checking from the application. A vulnerability exists because XrmToolBox v1.x is Open-Source Software (OSS). To mitigate, adequate maintenance and support must be provided for OSS. The Sponsor/Software admin personnel shall maintain and monitor the distribution of XrmToolBox v1.x.

Name	Description
No components have been identified for this entry.


Collaboration and Electronic Workplace Productivity Software	Multimedia Software

General Analysis

Adoption Benefits

At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
This technology is available at no cost through open source licensing and supports VA`s open source initiative.
This is a well-documented technology.
This technology may improve productivity for specific staff whose responsibilities include customization, configuration, and operational tasks for model-driven PowerApps.

Adoption Risks

There is no indication based on available vendor documentation that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.
This technology can potentially use Secure Sockets Layer (SSL), a protocol which requires a POA&M for use on the VA network.
This technology can potentially utilize publicly available artificial intelligence (AI) services.
IPR/SAR Adoption Risk - A vulnerability exists because XrmToolBox v1.x supports third-party plugins/tools, many authored by community developers without formal security vetting.
IPR/SAR Adoption Risk - A vulnerability exists because XrmToolBox v1.x connects to and makes use of multiple cloud-based services.
IPR/SAR Adoption Risk - A vulnerability exists because XrmToolBox v1.x collects anonymous statistics.
IPR/SAR Adoption Risk - A vulnerability exists because XrmToolBox v1.x installs an outdated (v5.3.0.0) NuGet package Microsoft.IdentityModel.Clients.ActiveDirectory. This package has been deprecated as it is legacy and is no longer maintained.
IPR/SAR Adoption Risk - A vulnerability exists because XrmToolBox v1.x installs an outdated (v6.1.7601.24479) Microsoft.Identity extension for .Net. According to the Project’s website IdentityModel 6.x is deprecated and support ended May 2024.
IPR/SAR Adoption Risk - A vulnerability exists because XrmToolBox v1.x provides automatic/user configurable checks for updates.
IPR/SAR Adoption Risk - A vulnerability exists because XrmToolBox v1.x is Open-Source Software (OSS).
This technology may utilize external data connections.
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.
Due to the frequency of this technology`s updates, the VA may be unable to keep up with the rapid release schedule of this technology and may require a usage model that requires specific versions.

Architectural Risks

The technology is not portable as it runs only on Windows platforms.

- The information contained on this page is accurate as of the Decision Date (08/28/2025 at 14:46:07 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 (08/26/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 Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 25.9

General Information

Vendor Release Information

Current Decision Matrix (08/26/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 Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework