May 20 2024 01:11 PM - edited May 20 2024 01:16 PM
Creating an exception to your sensitivity label policies can be essential in certain situations where these labels interfere with automated processes.
For instance, in a recent incident I managed, a Robotic Process Automation (RPA) system faced an issue due to the Default and Mandatory label policy. The process involved an SAP automated workflow that needed to create a new Excel document. However, the process was interrupted because the policy required a sensitivity label to be selected for the document, something the automated system couldn't do. By creating an exception for this specific process, we were able to ensure smooth operation without compromising the overall security and compliance framework.
This is very similar to what this SAP user has encountered: https://community.sap.com/t5/technology-q-a/how-to-setup-sensitivity-level-label-while-sending-an-em...
How to Set Up an Exception (Step-by-Step Guide)
Scenario: Your organization has a standard set of sensitivity labels (example: Public, Internal, Highly Confidential) and Default and Mandatory label policies turned on for the entire organization.
The requirement is to turn off the Default and Mandatory policies for a small set of specific users (in my case RPA users). In the steps below, assume that the policy has already been created and we need to create a "duplicate" policy and make it rank higher than the current policy but without the offending policies.
The last and very important step to make sure that this is a success is: