The first step to incorporating Transaction Security Policies is to create them. This part of the configuration is not specifically a SightLane action, but it is necessary for Salesforce to track and report Transaction Security Events.
|
Start by opening the setup menu and typing "Transaction Security Policies" into the Setup menu's Quick find search bar. If nothing is found, Salesforce Shield may not be enabled in your Salesforce org. To add a Transaction Security Policy, click the "New" button in the upper right-hand corner of your screen. |
You will see a modal screen pop up and ask you to choose between using the Condition Builder wizard and an Apex class. Select Apex and click Next. Don't worry. You won't have to actually write any Apex. We've taken care of that for you.
Next, you will select which Transaction Security Policy event you want to track. In the image below, we will track Login Events. In addition, you will select which Apex class will be used to "process" the event. Select sightlane_em__PolicyMonitor class that is part of the SightLane for Shield package.
Now that you have selected the event you are interested in, there are a few properties to fill out. Because SightLane handles processing, Email notifications and other properties are not as crucial in this case. For example, Salesforce makes you enter a "Recipient," but since we are not sending notifications through the standard process, the selected user makes very little difference. Remember to mark your Transaction Security policy as active and click the Finish button.
Note: The action parameter above (shown as "None") will contain various options, depending on the event you have selected. For example, the Login event includes actions for None, Block, and Multi-factor Authentication. These actions can be pretty valuable but are beyond the scope of this article. See more information in Salesforce help.
Repeat this process for all events you are interested in tracking. Once you have completed the configuration, you will see a list of your current Transaction Security Policies. Notice that they are set up to use the SightLane PolicyMonitor class to handle processing. This is what enables us to create powerful and flexible policy responses.
Policies can be enabled or disabled here OR in the SightLane interface, so you can choose whether to define all of them here or just the ones you are currently interested in. Congratulations! You have completed step one of the SightLane for Shield configuration process. Now that you've defined security policies for your favorite events, you are ready to take the next step!