PrimedLogging Enterprise Library

Efficiently manage Sensitive Logging in Enterprise RPA Processes

Automating applications that handle highly sensitive business processes in the modern enterprise is very challenging. The business owners are constantly worried about the sensitive nature of the messages being logged to resources outside of the corporate network. We are going to develop this idea based on information logged in the UiPath Orchestrator.

While business users have a solid argument in terms of confidentiality and compliance, it’s becoming difficult for RPA teams to constantly enable/disable or remove the Write Line and Log Message activities each time the RPA process is deployed to production. Besides these, debug and log output lines are put in place so that developers may troubleshoot and fix applications during development. In addition, it becomes easier to demonstrate the workings of the application to business groups during the demo sessions.

PrimedLogging is a simple library that can help you classify certain log output messages as sensitive or confidential and then, through a mechanism, to suppress them at the application level when the RPA process is finally deployed to production.

With such an arrangement, developers can retain the advantages of logging in the development environment, whilst being able to automatically disable sensitive logging in the UAT or PROD environment with a simple and efficient flip of a configuration setting.

Eliminate the archaic habit of disabling or removing the Write Line and/or Log Message activities when deploying projects to UAT and Production This practice can impair pace of development on medium and large projects as a lot of time will be spent just enabling/disabling these activities PrimedLogging will enable you with opportunity of recognizing and understanding the sensitive nature of the messages you plan to log Use PrimedLogging activity instead of the regular Write Line or Log Message activities to log sensitive messages Define a global setting that will help enable or disable "PrimedLog" messages - use the global setting to allow or disallow PrimedLogging to write outputs to the log This setting can be easily input to the RPA process as an argument to the client workflow and overridden in the Orchestrator at the process or job level Alter the behavior of your RPA processes almost instantly to suppress all sensitive logging when they become operational in UAT and Production All of this will not prevent you from using Write Line or Log Message activities - you will still use them to log non-sensitive information to your logs.