When it comes to security, let’s try to understand the source of security loopholes.
UiPath woks on top of applications or it interact with the application. here security will be at application level.
Uipath Works on web, so we will be using Https URL for any source which need automation, here the security will be at application level .
When we pass the credential over the wire, UiPath use AES_CBC_256, which is a highly secure cryptography algorithm to make our credential safe.
UiPath use HIPAA & SOX as storage technology to store our information, which is very structured in nature.
UiPath used to connect with REST services for different requirement, ex. Cognitive services where the security is from the service side, they will be using SSL or any other.
There is no threat so far with respect to the implementation.
Till date as per my knowledge nothing has been detected in UiPath and Orchestrator.
It drives the business application in the similar fashion like a human.
It depends upon the developer also, how secure the code is and whether he is keeping any confidential/important information in any risky place (inside workflow/in logs etc).
Example:
Reading confidential data from application and pushing this to the centralized logging server. Again the logging server relies inside the client’s network which is a secured zone. So no risk.
Keeping credentials securely in windows credential manager or Orchestrator assets will decrease the chance of vulnerability. This leads towards less risk too.
There are many more prevention ways, which can be used to avoid the vulnerability of a Automation script/workflow.
You’ve mentioned about many others ways to decrese information security risk of automation scripts. May be there is any best practice with all of them?
Could you recommend something as a kind of security methodology to keep in mind during robots developming?