Risks in An RPA Environment: Phases of Audit Considerations
Risks in An RPA Environment: Phases of Audit Considerations
Risks in An RPA Environment: Phases of Audit Considerations
RPA brings its own inherent risks as well the ones that are resultant of the business environment it automates. As part of RPA
assurance, we can address following access security risks:
• Automation of process through RPA without embedding/aligning control design may lead to manual override or
unauthorized changes which often goes undetected.
• Generic BOT ID often poses risk of non compliance to software licenses due to potential indirect usage
• BOTs stores credentials of multiple applications, which are often empowered with extensive access. Unauthorized
access and use of BOT credentials may lead to data, security, privacy and fraud risks
A secured and compliant BOT environment requires effective management and monitoring of the seven risk domains. Depending on the
relevance, each of these domains would help strengthen security and controls in your RPA environment. The below framework presents
a clear view about the types of risk which need to be considered when auditing a BOT-enabled organization. The auditor should try to
use a risk based approach to identify the controls addressing each of the RPA-specific risk consideration. Every domain of general IT
controls such as user-access management, change management, operations, and program development is important to be looked at
for the relevant BOTs.