Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 25.5

UiPath Automation Platform

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:	Automation Suite allows users to deploy the entire UiPath automation platform in a Linux environment whether it be on bare metal machines, on-premises Virtual Machine infrastructure, or cloud subscriptions to any of the major providers. 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 This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and authorized by the Mobile Technology and Endpoint Security Engineering Team: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
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.3
Decision Date:	03/05/2025 at 01:04:35 UTC
Introduced By:	TRM Request
Vendor Name:	UiPATH

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
2022.10.x
2023.4.x	04/26/2023
2023.10.x	11/03/2023
2024.10.x	11/11/2024

Current Decision Matrix (02/27/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

2022.10.x

DIVEST
[6, 7, 8, 9, 10, 11]

Authorized w/ Constraints (DIVEST)
[6, 7, 8, 9, 10, 11]

Authorized w/ Constraints (POA&M)

2023.4.x

DIVEST
[6, 7, 8, 9, 10, 11]

Authorized w/ Constraints (DIVEST)
[6, 7, 8, 9, 10, 11]

Authorized w/ Constraints (DIVEST)
[8, 10, 11, 12, 13]

Authorized w/ Constraints (POA&M)

2023.10.x

Approved w/Constraints
[6, 7, 8, 9, 10, 11]

Authorized w/ Constraints
[6, 7, 8, 9, 10, 11]

Authorized w/ Constraints (DIVEST)
[8, 10, 11, 12, 13]

Authorized w/ Constraints (POA&M)

2024.10.x

Unapproved

Authorized w/ Constraints (POA&M)

Authorized w/ Constraints
[8, 10, 11, 12, 13]

Note:

At the time of writing, version 2024.10.2 is the most current version, released 02/17/2025.

Decision Constraints


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

[7]	Users must ensure that Microsoft Structured Query Language (SQL) Server, Firefox, Google Chrome, and Kubernetes are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Microsoft Internet Explorer, a dependency of this technology, is in End-of-Life status and must no longer be used. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Users must not utilize Redis and Ceph, as it is at the time of writing, unapproved in the TRM. This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations. Per the Security Assessment Review (SAR), users must abide by the following constraints: To mitigate, the administrator shall update the unsupported version of OpenSSL to a TRM authorized version. 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. To mitigate, the optional mobile code shall not be installed unless it is TRM authorized. Maintenance and support will be provided for the Open Source Software used within UiPath Studio v23.x as per the application’s lifecycle. To mitigate, System Administrators shall set Telemetry to disabled under Settings > General > Telemetry within the UiPath Studio interface or manually within the .config file. To mitigate, the administrator shall disable automatic update checking.

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

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

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

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

[12]	Users must ensure that Microsoft Structured Query Language (SQL) Server, Firefox, Google Chrome, and Kubernetes are implemented with VA-authorized baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology can be deployed with Kubernetes. At the time of writing, the baseline for Kubernetes dictates that it can only be used in on-premises in Amazon Web Services (AWS) VA Enterprise Cloud (VAEC) implementations. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it requires a POA&M. Users must not utilize Ceph, as it, at the time of writing, requires a POA&M. Users must not utilize Redis, as it, at the time of writing, requires a POA&M. Per the Security Assessment Review (SAR), users must abide by the following constraints: To mitigate, UiPath Studio will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI)/Personally Identifiable Information (PII) or VA sensitive information. To mitigate, system owners should use the latest version of this product and monitor both the Common Vulnerabilities and Exposures (CVE) Details and NIST National Vulnerability Database (NVD) websites for any new security vulnerabilities. To mitigate, users should be instructed to disable the telemetry option in the application 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 To mitigate, Administrators should be instructed not to enable any automatic updates for UiPath Studio. Only VA TRM approved versions of this product should be used. To mitigate, users should follow the vendor provided documentation to enable the Private property and configure the application to not send passwords in logging information To mitigate, system owners should use the latest version of this product and monitor both the CVE Details and NIST (NVD) websites for any new security vulnerabilities. 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. To mitigate, system owners should use the latest version of this product and monitor both the CVE Details and NIST (NVD) websites for any new security vulnerabilities. To mitigate, the vendor must maintain all third-party components during the entire product lifecycle, including responding to vulnerabilities discovered in third-party components used in the product.

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

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
UiPath Action Center	Actions are tasks that users are assigned to and that users can complete when dealing with long-running workflows. and user intervention is required before proceeding to the next step in the workflow.
UiPath AI Center	UiPath AI Center is an application that allows the user to deploy, manage, and improve Machine Learning models and consume them within workflows.
UiPath Apps	UiPath Apps is a low-code application development platform that enables the user to build and share enterprise-grade custom applications that deliver engaging user experiences.
UiPath Automation Hub	UiPath Automation Hub is a process identification, automation pipeline management, and process repository feature.
UiPath Automation Ops	UiPath Automation Ops is a centralized, web-based platform that enables administrators to configure and deploy governance policies for UiPath Studio, UiPath Robot, and UiPath Assistant.
UiPath Computer Vision	The UiPath Computer Vision feature enables the user to use the vendor`s in-house neural network in order to identify User Interface (UI) Elements and interact with them with Robots, simulating human interaction. The Computer Vision feature is composed of a set of Activities, that are part of the UIAutomation activities package, as well as a Server (which can be Cloud, On-Prem, or Local), which is needed to perform the actual analysis of the UI that is automating.
UiPath Data Service	UiPath Data Service is a persistent data storage service that brings powerful no-code data modeling and storage capabilities to Robotic Process Automation (RPA) projects.
UiPath Document Understanding	The UiPath Document Understanding framework facilitates the processing of incoming files, from file digitization to extracted data validation, all in an open, extensible, and versatile environment.
UiPath Insights	Insights is a web application that serves as a platform for data modeling and analytics using a combination of available business metrics and operational insights.
UiPath Orchestrator	UiPath Orchestrator is a web application that enables the user to orchestrate robots in executing repetitive business processes. Orchestrator manages the resources to be used in automation projects and consumed by robots, and access to them through support for hierarchical structuring combined with fine-grained role assignment. Its power comes from its capability of managing an entire robot fleet.
UiPath Process Mining	UiPath Process Mining is a Process Mining solution that transforms data from IT systems into visual interactive dashboards, allowing the user to see existing value decreases, bottlenecks, and discrepancies, as well as understanding the root-causes and possible risks.
UiPath Task Mining	UiPath Task Mining is an actionability discovery service. It collects user desktop data comprising of the screenshot and log data upon each user action (mouse click, keystroke), then runs a machine learning model to analyze the data and suggest a list of tasks with high automation potential.
UiPath Test Manager	UiPath Test Manager is a web application hosted by Test Management Hub that allows the user to manage the testing process.
uipathctl	uipathctl is a UiPath command-line tool that allows you to run commands against Automation Suite Kubernetes hosted on Azure Kubernetes Service (AKS) and Amazon Elastic Kubernetes Service (EKS).


Information Management Technologies Business Intelligence and Data Warehouse Platforms	Data Mining Tools
Information Management Technologies Data Management	Data Quality Management

General Analysis

Adoption Benefits

This technology has a comprehensive set of documentation.
This technology may improve productivity for specific staff whose responsibilities include working with uiPath automation.
There are minimal other TRM-authorized technologies that provide the same functionality.
This vendor stated that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
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.

Adoption Risks

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.
The potential of vendor lock exists when utilizing proprietary vendor technology.
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.
This technology can integrate with and alter database technologies.
This technology can be implemented with Kubernetes. At the time of writing, Kubernetes is limited to on premises VA Enterprise Cloud implementations on Amazon Web Services (AWS) Servers. Other uses of this technology requires a POA&M for use on the VA network.
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 use Ceph which requires a POA&M for use on the VA network.
This technology can potentially use Redis which requires a POA&M for use on the VA network.
IPR/SAR Adoption Risk - A vulnerability exists because UiPath Studio installs components of the following Open-Source Software (OSS)(s):
1. Multiple components of Actipro for WPF v24.1.2.0, 20.1.0.0, and 19.1.687.0
2. OpenXML v2.x
3. NotifyIcon for WFP v1.1.0.17
4. Json.Net v1.x, 2.x, 3.x, 4.x, 6.x, 7.x, 8.x, 9.x, 10.x 11.x, 12.x, 13.x
5. OpenSSL v1.1.1w, 1.0.24212.01
6. libssh2 v1.11.0
7. Microsoft.Web.Webview2.Wpf v1.x
8. NJsonSchema v10.9.0
9. SVG-to-XAML Convertors v1.7.7.0
10. NuGet v8.0.1024.46610
11. libcurl v8.9.1-DEV
12. ICSharpCode.SharpZipLib v1.3.3.11
IPR/SAR Adoption Risk - A vulnerability exists because UiPath Studio is not FIPS 140-2 (or its successor) certified. To mitigate, UiPath Studio will require a 3rd party FIPS 140-2 (or its successor) certified solution for any data containing Protected Health Information (PHI)/Personally Identifiable Information (PII) or VA sensitive information.
IPR/SAR Adoption Risk - A vulnerability exists because there are published vulnerabilities for previous versions of UiPath Studio. To mitigate, system owners should use the latest version of this product and monitor both the Common Vulnerabilities and Exposures (CVE) Details and NIST National Vulnerability Database (NVD) websites for any new security vulnerabilities.
IPR/SAR Adoption Risk - A vulnerability exists because under the General Settings tab of the application there is a telemetry setting to send anonymous usage data. This option is enabled by default. To mitigate, users should be instructed to disable the telemetry option in the application.
IPR/SAR Adoption Risk - A vulnerability exists because UiPath Studio has the ability to connect to multiple cloud services. According to vendor documentation “UiPath shares customer data with its sub-processors, when you are using UiPath cloud products.” 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.
IPR/SAR Adoption Risk - A vulnerability exists because policies can be set through UiPath Orchestrator to automatically update the UiPath Studio application. To mitigate, Administrators should be instructed not to enable any automatic updates for UiPath Studio. Only VA TRM approved versions of this product should be used.
IPR/SAR Adoption Risk - A vulnerability exists because by default UiPath Studio sends passwords in logging information. To mitigate, users should follow the vendor provided documentation to enable the Private property and configure the application to not send passwords in logging information.
IPR/SAR Adoption Risk - A vulnerability exists because UiPath Studio installs an outdated version of OpenSSL that has multiple published vulnerabilities and is listed as Authorized w/ Constraints (POA&M) on the VA TRM v25.12. To mitigate, system owners should use the latest version of this product and monitor both the CVE Details and NIST (NVD) websites for any new security vulnerabilities. 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.
IPR/SAR Adoption Risk - A vulnerability exists because UiPath Studio installs a component of libcurl that has multiple published vulnerabilities. To mitigate, system owners should use the latest version of this product and monitor both the CVE Details and NIST (NVD) websites for any new security vulnerabilities.

Architectural Benefits

This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).
This technology can use a VA-preferred database.

Architectural Risks

This technology is not portable as it runs only on Linux operating systems.
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 (03/05/2025 at 01:04:35 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 25.5

General Information

Vendor Release Information

Current Decision Matrix (02/27/2025)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

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 25.5

General Information

Vendor Release Information

Current Decision Matrix (02/27/2025)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

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