We are a large multi-national corporate financial services provider. Governance and Business Continuity are a key part of our design and implementations.
We operate in 10+ geographies with various degrees of market maturity and capabilities in a "federated model" type.
I would like to understand the key "generic" but universal Governance and Business Continuity requirements that HelpSy...
Community Manager at PeerSpot (formerly IT Central Station)
20 July 20
@reviewer1356150 @Nilesh Pawar @reviewer1390509 @Alex Yuan @Hayaa Kayasseh you've all recently written reviews for one of these products. Do you have any insight to share with @reviewer1373997 about governance and business continuity requirements for these products?
For any RPA tool it required have a generic /universal governance model where
1. sponsor or Head of RPA implementation
2. Business analysts
4.Developers ( Full stack - Build, Test and SIT)
5.Scrum master or Sprints head or Project manager
6. QA ( Test automation) - optional
Above generic governance model/structure roles for handling any kind of RPA process.
One proven way to implement centralized automation management is via a CoE. The best practices of Robotic Process Automation states that the use of bots doesn’t increase negative risks for the organization in the development of reusable solutions. The responsibilities of a Centre of Excellence will depend on the exact governance model used. The most common activities include the following:
Drive RPA in the business, training teams, and increasing awareness of RPA in those.
Calculate the criticality and quality of the developed solutions, ensuring the application of best practices.
Monitor the operation of bots and guarantee that execution SLAs (service-level agreement) are met.
Follow and report the main development stages.
Guarantee the execution of established governance processes.
Guarantee the continual improvement of processes and tools.
Business Continuity Requirements:
To have backup or disaster recovery machines for the critical RPA processes with load balancing using central orchestration in different clusters.
For any of the RPA there is orchestration tool which handles all the initiation and processing from one location have it maintained well from risks and disasters with load balancing.
This will helps in business continuity.
Is it required in your company to conduct a security review before purchasing robotic process automation software? What are the common materials you use in the review?
Do you have any tips or advice for the community?
Any pitfalls to watch out for?
Founder | RPA Solution Architect at Auxiliobits Technologies
29 May 19
See here http://bit.ly/2WCIR53
Recognize the potential security risks associated with the Robotic Process Automation in an organization. Understand what features are available out of the box from the solution being deployed. For instance, if a solution being deployed is architecturally security supportive then we can make use of it to its best. Apply best practices while implementing and deploying an organization-wide RPA solution. The key to avoid security breaches is to first identify various potential security risks associated with an RPA project.
The risks that a company must consider may include one or all of the following:
- RPA robots may have access to the credentials that are normally possessed and used by a human worker.
- Robots may have access to company privileged information. This information can be anything from personal staff data to financial data.
-There is also a risk of unauthorized modification of automation workflows or their run time parameters in the production environment.
-The modifications of automation workflows can also happen during development for which measures should be taken beforehand.