TransactionSecurityPolicy

Represents a transaction security policy definition. Transaction security policies give you a way to look through events in your organization and specify actions to take when certain combinations occur.

This type extends Metadata and inherits its fields.

TransactionSecurityPolicy components have the suffix .transactionSecurityPolicy and are stored in the transactionSecurityPolicies folder.

Introduced in API version 35.0.

• Type: TransactionSecurityAction
• Required: Yes
• Description: Required. Describes the action to take when the matching Transaction Security policy is triggered.

• Type: boolean
• Required: Yes
• Description: Required. If true, the policy is enabled and actively monitors its event.

• Type: string
• Required: No
• Introduced: API version 46.0
• Description: Required for Apex-based policies, and optional for all other policies. The name of the class that implements the TxnSecurity.PolicyCondition or TxnSecurity.EventCondition interface for this policy.

• Type: string

• Required: No

• Introduced: API version 49.0

• Description: The custom message sent to a user when a policy blocks their action. Used in Real-Time Event Monitoring only. Maximum of 1000 characters. This field is null when the default message option is selected in the UI. Available only when eventName is set to ApiEvent, ListViewEvent, BulkApiResultEventStore, or ReportEvent. Include org- or policy-specific information in your custom message, such as the name of the responsible administrator or the business unit. Be careful about what you include. Too much information on how the policy was designed. can aid a malicious user.

  Two-factor authentication (2FA) isn’t supported in Lightning Experience, so events like ListView and ReportEvent are upgraded to Block in Lightning.

  Custom messages aren’t translatable.

• Type: string
• Required: No
• Introduced: API version 54.0
• Description: The administrator-created custom email content sent when a policy is triggered. Used in Real-Time Event Monitoring only. Maximum of 1333 characters. This field is null when the Custom Email Content setting is selected in the UI but no message content is entered. Custom messages aren’t translatable.

• Type: string
• Required: No
• Description: A description of this component. The description should explain the component’s purpose and behavior so that administrators and developers understand when to use it.

• Type: string
• Required: No
• Description: The unique developer name of this component. Used as an API reference and must follow Salesforce identifier rules.

• Type: TransactionSecurityEventName (enumeration of type string)
• Required: No
• Introduced: API version 49.0
• Description: Used in Real-Time Event Monitoring only. Indicates the name of the event the policy monitors. This field is available in API 45.0 and later.
• Possible values:
  • AdminSetupEvent
  • ApiAnomalyEventStore — Tracks anomalies in how users make API calls. ApiAnomalyEventStore is an object that stores the event data of ApiAnomalyEvent. This object is available in API version 50.0 and later.
  • ApiEvent — Tracks these user-initiated read-only API calls: query(), queryMore(), and count(). Captures API requests through SOAP API and Bulk API for the Enterprise and Partner WSDLs. Tooling API calls and API calls originating from a Salesforce mobile app aren’t captured.
  • BulkApiResultEventStore — Tracks when a user downloads the results of a Bulk API request. BulkApiResultEventStore is a big object that stores the event data of BulkApiResultEvent. This object is available in API version 50.0 and later.
  • CredentialStuffingEventStore — Tracks when a user successfully logs into Salesforce during an identified credential stuffing attack. Credential stuffing refers to large-scale automated login requests using stolen user credentials.This value is available in API version 49.0 and later.
  • FileEventStore — Tracks when a user downloads, previews, or uploads a file. FileEventStore is a big object that stores the event data of FileEvent. This object is available in API version 57.0 and later.
  • GuestUserAnomalyEventStore — Tracks data access anomalies that are caused by guest user permission misconfiguration. This object is available in API version 60.0 and later.
  • ListViewEvent — Tracks when users access data with list views using Lightning Experience, Salesforce Classic, or the API. It doesn’t track list views of Setup entities.
  • LoginAnomalyEventStore
  • LoginAsEvent — Tracks the login activity of admins who log in to Salesforce as other users. This object is available in API version 46.0 and later.
  • LoginEvent — LoginEvent tracks the login activity of users who log in to Salesforce.
  • PermissionSetEventStore — Tracks changes to permission sets and permission set groups.
  • ReportAnomalyEventStore — This value is available in API version 49.0 and later.
  • ReportEvent — Tracks when reports are run in your org.
  • SessionHijackingEventStore — Tracks when unauthorized users gain ownership of a Salesforce user’s session with a stolen session identifier. To detect such an event, Salesforce evaluates how significantly a user’s current browser fingerprint diverges from the previously known fingerprint using a probabilistically inferred significance of change. Available in API version 49.0 and later.
  • UniversalAnomalyEventStore

• Type: MonitoredEvents (enumeration of type string)

• Required: No

• Description: Used in Legacy Transaction Security only. Required for Apex-based policies, and optional for all other policies. Indicates which type of event is being monitored.

  As of Summer ‘20, Legacy Transaction Security is a retired feature in all Salesforce orgs.

• Possible values:

  • AccessResource — Notifies you when the selected resource has been accessed.
  • AuditTrail — Reserved for future use.
  • DataExport — Notifies you when the selected object type has been exported using the Data Loader API client.
  • Entity — Notifies you on use of an object type such as an authentication provider or Chatter comment.
  • Login — Notifies you when a user logs in.

• Type: string

• Required: No

• Description: Used in Legacy Transaction Security only. The name or ID of an active user who is assigned the Modify All Data and View Setup user permissions.

  As of Summer ‘20, Legacy Transaction Security is a retired feature in all Salesforce orgs.

• Type: string
• Required: No
• Introduced: API version 46.0
• Description: Required only for policies of type CustomConditionBuilderPolicy. The ID of the Flow object that contains the logic the Condition Builder transaction security policy.

• Type: string
• Required: No
• Description: The master label for this component. This display value is the internal label that isn’t translated.

• Type: string

• Required: No

• Description: Used in Legacy Transaction Security only. Required for Apex-based policies, and optional for all other policies. A resource used to narrow down the conditions under which the policy triggers. For example, with a DataExport event, you can select a resource Lead to specifically monitor export activity occurring on your Lead entities. The resources available depend on the Event Type field. The following valid resources are grouped by event type.

  • AccessResource—ConnectedApplication, Reports
  • DataExport—Account, Case, Contact, Lead, Opportunity
  • Entity—AuthProvider, ChatterMessage, FeedComment, FeedItem, Idea, Question
  • Login—LoginHistory

  As of Summer ‘20, Legacy Transaction Security is a retired feature in all Salesforce orgs.

• Type: TxnSecurityPolicyType (enumeration of type string)
• Required: No
• Description: The type of validation that the policy uses. The default value is CustomApexPolicy.
• Possible values:
  • CustomApexPolicy — Created with Apex editor.
  • CustomConditionBuilderPolicy — Created with Condition Builder.

Describes the action to take when the matching Transaction Security policy is triggered.

• Type: boolean
• Required: Yes
• Description: If true, the requested operation is blocked. This action only applies to Login and AccessResource events.

• Type: boolean

• Required: Yes

• Description: Used in Legacy Transaction Security only. If true, a current session must be closed before a new session can be started. This action only applies to Login events.

  As of Summer ‘20, Legacy Transaction Security is a retired feature in all Salesforce orgs.

• Type: boolean

• Required: Yes

• Description: Used in Legacy Transaction Security only. If true, the user that triggered the policy is frozen. This action only applies to Chatter resources for Entity events.

  As of Summer ‘20, Legacy Transaction Security is a retired feature in all Salesforce orgs.

• Type: TransactionSecurityNotification[]
• Required: No
• Description: Specifies how to notify the Salesforce administrator when the action is triggered. There can be none, one, or multiple notifications.

• Type: boolean

• Required: Yes

• Description: If true, multi-factor authentication (MFA) is required for a higher level of access before the requested operation can continue. This action only applies to Login and AccessResource events.

  Multi-factor authentication was formerly called two-factor authentication.

• Type: boolean
• Required: No

Describes who to notify and how to notify them when the matching Transaction Security policy is triggered.

• Type: boolean
• Required: Yes
• Description: True if an in-app notification is selected.

• Type: boolean
• Required: Yes
• Description: True if an email notification is selected.

• Type: string
• Required: Yes
• Description: The user to receive the notification.

The following is an example of a Real-Time Event Monitoring TransactionSecurityPolicy component.

1<?xml version="1.0" encoding="UTF-8"?>
2<TransactionSecurityPolicy xmlns="http://soap.sforce.com/2006/04/metadata">
3    <action>
4        <block>true</block>
5        <notifications>
6            <inApp>true</inApp>
7            <sendEmail>true</sendEmail>
8            <user>user@your.org</user>
9        </notifications>
10        <twoFactorAuthentication>false</twoFactorAuthentication>
11    </action>
12    <active>true</active>
13    <apexClass>TxnSecMDApiPolicyEventCondition</apexClass>
14    <blockMessage>You cannot view this report.</blockMessage>
15    <developerName>TxnSecPolicyMDApi</developerName>
16    <eventName>ReportEvent</eventName>
17    <masterLabel>Txn Sec MD Api Policy</masterLabel>
18    <type>CustomApexPolicy</type>
19</TransactionSecurityPolicy>

The following is an example package manifest used to deploy or retrieve the transaction security metadata for an organization.

1<?xml version="1.0" encoding="UTF-8"?>
2<Package xmlns="http://soap.sforce.com/2006/04/metadata">
3    <types>
4        <members>MySecurityPolicy</members>
5        <name>TransactionSecurityPolicy</name>
6    </types>
7    <version>35.0</version>
8</Package>

This metadata type supports the wildcard character * (asterisk) in the package.xml manifest file. For information about using the manifest file, see Deploying and Retrieving Metadata with the Zip File.