| 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 |
Future> |
| 9.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 22.x |
Approved w/Constraints
[4, 11, 13, 14, 15, 17, 18] |
Approved w/Constraints
[4, 11, 13, 14, 15, 17, 18] |
Approved w/Constraints
[4, 11, 13, 14, 15, 17, 18] |
Authorized w/ Constraints (DIVEST)
[4, 11, 13, 14, 15, 17, 18] |
Authorized w/ Constraints (DIVEST)
[4, 11, 13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST)
[4, 11, 13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 23.x |
Approved w/Constraints
[4, 11, 13, 14, 15, 17, 18] |
Approved w/Constraints
[4, 11, 13, 14, 15, 17, 18] |
Approved w/Constraints
[4, 11, 13, 14, 15, 17, 18] |
Authorized w/ Constraints
[4, 11, 13, 14, 15, 17, 18] |
Authorized w/ Constraints (DIVEST)
[4, 11, 13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST)
[4, 11, 13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| 24.x |
Unapproved |
Unapproved |
Unapproved |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (DIVEST)
[4, 11, 13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (DIVEST)
[4, 11, 13, 15, 17, 18, 19, 20] |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (POA&M) |
| Note: |
At the time of writing, version 24.10.9 is the most current version, released 02/05/2025. |
| | | | [4] | 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. | | | [11] | Browser plug-ins and extensions may only be installed by VA IT Operations (ITOPS) and must be used with official VA browser installation packages that are managed by ITOPS. For installation, contact the National Service Desk [Mail Group: National Service Desk - Austin]. Browser extensions must be kept up to date with security patches and enhancements. | | | [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] | Users must ensure that Microsoft Edge, Firefox, and Google Chrome are implemented within VA-authorized baselines.
Per the Security Assessment Review (SAR), users must abide by the following constraints:
-
The UiPath Browser Extension utilizes multiple permissions including critical permission including . This permission grants access to any URL that starts with a permitted scheme (e.g. http, https, file, ftp etc.). An extension does not normally need access to all schemes. Instead of using the permission, it is advised to use preferred specific sites (i.e. https://*.google.com). The UiPath Browser Extension also uses nativeMessaging, which is considered medium risk. This permission gives the extension access to the native messaging API.
Per the vendor, these permissions cannot be changed without hindering functionality of the extension. To address this there is a governance framework to ensure that only authorized automations are accessible to the robot and the robot can only execute those authorized automations. It is also important to ensure that automations go through a security check prior to production release. Once in production, it is important to ensure logging is enabled to provide auditing capabilities.
If free trialware is utilized, the software must be purchased or removed at the end of the trial period. | | | [15] | 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. | | | [17] | 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. | | | [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, visit the Product Marketplace. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102). | | | [19] | Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Edge, Firefox, and Google Chrome are implemented within VA-authorized baselines.
Per the Security Assessment Review (SAR), users must abide by the following constraints:
- UiPath uses permissions that may not be necessary for the extension to
function. One critical, one high, seven medium, and one low risk permission
was noted. It is advised that permissions are verified with the developer and
removed if they are not absolutely necessary for the extension to function.
Using permissions that are not essential to the extension’s functionality
expose the system, using the UiPath Browser Extension, to potential
vulnerabilities and addition risk that could otherwise be avoided by disabling
nonessential permissions.
- UiPath Browser Extensions are not Federal Information Processing Standards
(FIPS) 140-2 (or its successor) certified. UiPath 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.
- UiPath can be deployed in the cloud. Due to potential information security
risks, Software as a Service/Platform as a Service 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.
- The Chrome, Edge, and Firefox Extension are not available on their respective
browser stores. They can only be installed through the UiPath Studio desktop
installer. System Owners/Administrators should ensure access to install
programs/add-ons is limited to privileged accounts as the application list
includes programs that are prohibited or unapproved on the One-VA
Technical Reference Model. Access to Studio Backstage View within Tools of
UiPath Studio should be limited.
| | | [20] | 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. |
|
