Table of Contents
What is legacy transaction security in Salesforce?
As of Summer ’20, Legacy Transaction Security is a retired feature in all Salesforce orgs. You can no longer create, edit, or enable transaction security policies using the legacy framework and will receive an error message if you try to do so.
What is enhanced transaction security framework in Salesforce?
The enhanced transaction security framework makes it easy to create policies that are more useful than policies created with of the legacy framework. You can migrate your legacy policies to the new framework. As of Summer ’20, Legacy Transaction Security is a retired feature in all Salesforce orgs.
What is a transaction security policy?
Each transaction security policy has conditions that evaluate events and the real-time actions that are triggered after those conditions are met. The actions are Block, Multi-Factor Authentication, and Notifications.
Why is transaction security locking me out of my Org?
Be careful—Transaction Security is a powerful feature. An incorrect Login Event policy that uses Block as its real-time action locks you out of your org. To prevent this from happening in an org you care about, create a new Trailhead Playground for this module.
What is transaction security policy Salesforce?
Transaction Security is a feature that monitors Salesforce events in real time to spot potential trouble based on rules you create. With Transaction Security, you can create policies that consist of events, notifications, and actions.
What is Transaction Security policies?
Transaction Security is a framework that intercepts real-time Salesforce events and applies appropriate actions and notifications based on security policies you create. Transaction Security monitors events according to the policies that you set up.
What are the benefits of Transaction Security Salesforce?
Transaction Security uses resource metering to help prevent malicious or unintentional monopolization of shared, multi-tenant platform resources. Metering prevents transaction security policy evaluations from using too many resources and adversely affecting your Salesforce org.
How do I create a transaction Security policy in Salesforce?
Required Editions and User PermissionsFrom Setup, in the Quick Find box, enter Transaction Security , and then select Transaction Security Policies.Click New, and then select Condition Builder.Click Next.Select an event that your policy is built on. … Select your condition logic. … Select your conditions. … Click Next.More items…
What is event monitoring Salesforce?
Event Monitoring is one of many tools that Salesforce provides to help keep your data secure. It lets you see the granular details of user activity in your organization. We refer to these user activities as events.
How many types of security are there in Salesforce?
Further, there are five types of record-level security: org-wide defaults, role hierarchy sharing, sharing rules, manual sharing, and Apex-based sharing.
What is Shield in Salesforce?
Salesforce Shield is a trio of security tools that helps admins and developers build extra levels of trust, compliance, and governance right into business-critical apps. It includes Shield Platform Encryption, Event Monitoring, and Field Audit Trail.
What is high assurance session Salesforce?
With this setting, users who verify their identity from an unrecognized browser or app establish a high-assurance session. When Activation is in the High Assurance column, profile users who verify their identity at login aren’t challenged to verify their identity again.
What is enhanced transaction security?
Enhanced Transaction Security is a framework that intercepts real-time events and applies appropriate actions to monitor and control user activity. Each transaction security policy has conditions that evaluate events and the real-time actions that are triggered after those conditions are met. The actions are Block, Multi-Factor Authentication, and Notifications. Before you build your policies, understand the available event types, policy conditions, and common use cases. Enhanced Transaction Security is included in Real-Time Event Monitoring.
Why are policies called conditions?
Because your policy’s actions are conditional to the fields that users interact with, these fields are called conditions. When you create a policy, you choose the conditions you want your policy to monitor and the action the policy takes when the conditions are met.
Warning
Be careful—Transaction Security is a powerful feature. An incorrect Login Event policy that uses Block as its real-time action locks you out of your org. To prevent this from happening in an org you care about, create a new Trailhead Playground for this module.
Enable Transaction Security
Now that you know what Transaction Security is, let’s get started using it. First, you need to enable Transaction Security in your Trailhead playground.
Create a Policy
Now that you’ve enabled Transaction Security, it’s time to learn how to use it. Policies can be built entirely with clicks, though Apex classes are needed for custom use cases. Let’s start with a simple example: preventing a large data export. For this use case, we’ll use Condition Builder to create the policy with just clicks.
Edit a Policy
Now let’s say you want to change the conditions in your Transaction Security policy. Editing a policy to change the conditions, notification, action, or most anything else is simple.
Enable Your Policy
After you create your policy, you need to enable it so it works in your org.
Hands-on Challenge
You’ll be completing this challenge in your own hands-on org. Click Launch to get started, or click the name of your org to choose a different one.
