Ensuring security and compliance is critical for RPA initiatives.
This is a place where IT needs to play a lead role in RPA. I have seen that it is prudent to bring all relevant parties in at the Pilot (POC) stage itself.
The RPA tools you select has to be able to meet the security and compliance requirements of IT and Audit.
A few key considerations from RPA security & compliance perspective:
- Establish an RPA development methodology with a clear separation between development, testing, and production environments.
- Never give someone configuration-build-test authority who also has authority to the run environment.
- Make sure that every RPA access is authenticated. Encrypt and secure data in transit and at rest.
- Bots now need to be GDPR compliant and not keep track of data that needs to be deleted under the ‘right to be forgotten’ clause.
As with any project, all standards you use elsewhere in the organization need to be applied to RPA as well.
Last Updated on 20th March 2019