| 22.x |
Unapproved |
Approved w/Constraints
[3, 4, 7, 9, 10, 11] |
Approved w/Constraints
[3, 4, 7, 9, 10, 11] |
Approved w/Constraints
[3, 4, 7, 9, 10, 11] |
Approved w/Constraints
[4, 9, 10, 11, 12, 13] |
Approved w/Constraints
[4, 9, 10, 11, 12, 13] |
Approved w/Constraints
[4, 9, 10, 11, 12, 13] |
Approved w/Constraints
[4, 9, 10, 11, 12, 13] |
Approved w/Constraints
[4, 9, 10, 11, 12, 13] |
Approved w/Constraints
[4, 9, 10, 11, 12, 13] |
Approved w/Constraints
[4, 9, 10, 11, 12, 13] |
Approved w/Constraints
[4, 9, 10, 11, 12, 13] |
| | | | [1] | 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.
UiPath Chrome Extension has an encryption capability for Federal Information Processing Standards (FIPS) 140-2 compliance, however it is not FIPS 140-2 certified. System owners must configure UiPath Chrome Extension to run on the FIPS compliant mode to ensure that VA sensitive data is secure.
UiPath uses Orchestrator to store all sensitive information using FIPS compliant Advanced Encryption Standard (AES) 256 algorithm for encrypting data at rest and Hypertext Transfer Protocol Secure (HTTPS) port 443 for the data in transit (2048-bit certificate is supported). VA must develop a policy that users must not use, disclose, transmit or otherwise process any Personally Identifiable Information (PII)/ Protected Health Information (PHI) as defined in Health Insurance Portability and Accountability Act (HIPAA) through the UiPath Chrome Extension and its associated components. UiPath must be configured to have the automation and robot data stored by Orchestrator, to eliminate the need to store the data on the local machine.
UiPath can be deployed in the cloud. Due to potential information security risks, Software as a Service (SaaS) must complete the Veterans-Focused Integration Process Request (VIPR) process where a collaborative effort between Demand Management (DM), Enterprise Program Management Office Information Assurance (EPMO IA), Project Special Forces (PSF), Enterprise Cloud Solutions Office (ECSO), Chief Technology Officer (CTO) and stakeholders determines the SaaS/Platform as a Service (PaaS) category during the Discovery Phase. All SaaS and Non-AWS/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 PSF.
UiPath Chrome Extension is shown to conform to Category 2 definitions. Category 2 mobile code technologies have full functionality, allowing mediated or controlled access to workstation, server, and remote system services and resources. Category 2 mobile code technologies can pose a moderate threat to VA information systems. Category 2 mobile code technologies may be used when the Category 2 restrictions in the VA Mobile Code Policy are implemented. | | | [2] | 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. | | | [3] | 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 approved and the user should take the proper steps to decline those installations. | | | [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. | | | [5] | 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). | | | [6] | 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). | | | [7] | 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. | | | [8] | 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). | | | [9] | Users must ensure that Firefox and Google Chrome are implemented within VA-approved 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 approved automations are accessible to the robot and the robot can only execute those approved 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.
| | | [10] | 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). | | | [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. | | | [12] | 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. | | | [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 approved and the user should take the proper steps to decline those installations. |
|
