TransactionSecurityPolicy
Represents a transaction security policy definition.
Introduced in API version 42.0.
create(), delete(), describeSObjects(), query(), retrieve(), update(), upsert()
- Type: textarea
- Properties: Create, Update
- Description: Describes the action to take when the matching Transaction Security policy is triggered. Also indicates the type of notifications selected and the ID of the intended recipient. The recipient must be active and assigned the Modify All Data and View Setup user permissions. Multiple actions can be taken. The actions available depend on the
Event Typefield.
- Type: reference
- Properties: Create, Filter, Group, Nillable, Sort, Update
- Description: Represents the Apex
TxnSecurity.PolicyConditionorTxnSecurity.EventConditioninterface for this policy. - Relationship name: ApexPolicy
- Relationship type: relationship
- Refers to: ApexClass
-
Type: string
-
Properties: Create, Filter, Nillable, Sort, Update
-
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
EventNameis set toApiEvent,ListViewEvent,BulkApiResultEventStore, orReportEvent.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
ListViewandReportEventare upgraded to Block in Lightning.Custom messages aren’t translatable.
-
Type: string
-
Properties: Create, Filter, Nillable, Sort, Update
-
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
- Properties: Create, Filter, Nillable, Sort, Update
- Introduced: API version 39.0
- Description: The description entered for this policy.
-
Type: string
-
Properties: Create, Filter, Group, Sort, Update
-
Description:
The API, or program name, for this policy.
Only users with View DeveloperName OR View Setup and Configuration permission can view, group, sort, and filter this field.
- Type: picklist
- Properties: Create, Filter, Group, Nillable, Restricted picklist, Sort, Update
- Description: Used in Real-Time Event Monitoring only. Indicates the name of the event the policy monitors.
- Possible values:
- AdminSetupEvent — AdminSetupEvent — Captures metadata and configuration changes made by administrators within the Setup area of your org.
- AdminSetupEventStore — AdminSetupEventStore — Tracks metadata and configuration changes made by administrators within the Setup area of your org.
- ApiEvent — ApiEvent — Tracks these user-initiated read-only API calls:
query(),queryMore(), andcount(). 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. - ApiAnomalyEventStore — 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. - BulkApiResultEventStore — BulkApiResultEventStore — Tracks when a user downloads the results of a Bulk API request.
BulkApiResultEventStoreis a big object that stores the event data ofBulkApiResultEvent. This object is available in API version 50.0 and later. - CredentialStuffingEventStore — 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 49.0 and later.
- FileEventStore — 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 — GuestUserAnomalyEventStore — Tracks data access anomalies that are caused by guest user permission misconfiguration. GuestUserAnomalyEventStore is an object that stores the event data of GuestUserAnomalyEvent. This object is available in API version 60.0 and later.
- ListViewEvent — 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 — LoginAnomalyEventStore — Stores the records of data access anomalies that are caused by potentially malicious login actions.This object is available in API version 64.0 and later.
- LoginAsEvent — 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 — LoginEvent tracks the login activity of users who log in to Salesforce.
- PermissionSetEventStore — PermissionSetEventStore — Tracks changes to permission sets and permission set groups.
- ReportAnomalyEventStore — ReportAnomalyEventStore — Tracks anomalies in how users run or export reports, including unsaved reports. This value is available in API 49.0 and later.
- ReportEvent — ReportEvent — Tracks when reports are run in your org.
- SessionHijackingEventStore — 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. This value is available in API 49.0 and later.
- UniversalAnomalyEventStore — UniversalAnomalyEventStore — Stores data for a broad range of system and user activity anomalies that do not map to standard event stores.
- Type: picklist
- Properties: Create, Filter, Group, Nillable, Restricted picklist, Sort, Update
- Description: Used in Legacy Transaction Security only. Indicates the type of event the policy monitors.
- Possible values:
- AccessResource — AccessResource — Notifies you when the selected resource has been accessed.
- AuditTrail — AuditTrail — Reserved for future use.
- DataExport — DataExport — Notifies you when any API query is made, such as from the Data Loader API client, or when a Report export occurs.
- Entity — Entity — Notifies you on use of an object type such as an authentication provider or chatter post.
- Login — Login — Notifies you when a user logs in.
- Type: reference
- Properties: Create, Filter, Group, Nillable, Sort, Update
- Description: Used in Legacy Transaction Security only. The 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.
- Relationship name: ExecutionUser
- Relationship type: relationship
- Refers to: User
-
Type: reference
-
Properties: Create, Filter, Group, Nillable, Sort, Update
-
Relationship name: Flow
-
Relationship type: relationship
-
Refers to: InteractionDefinitionVersion
- Type: picklist
- Properties: Create, Defaulted on create, Filter, Group, Nillable, Restricted picklist, Sort, Update
- Description: The combined language and locale ISO code, which controls the language of the Transaction Security Policy.
-
Type: string
-
Properties: Create, Filter, Group, Sort, Update
-
Description: The policy’s name.
Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.
-
Type: string
-
Properties: Filter, Group, Nillable, Sort
-
Description:
The namespace prefix associated with this object. Each Developer Edition organization that creates a managed package has a unique namespace prefix. Limit: 15 characters. You can refer to a component in a managed package by using the
namespacePrefix__componentNamenotation.The namespace prefix can have one of the following values:
- In Developer Edition organizations, the namespace prefix is set to the namespace prefix of the organization for all objects that support it. There is an exception if an object is in an installed managed package. In that case, the object has the namespace prefix of the installed managed package. This field’s value is the namespace prefix of the Developer Edition organization of the package developer.
- In organizations that are not Developer Edition organizations,
NamespacePrefixis only set for objects that are part of an installed managed package. There is no namespace prefix for all other objects.
- Type: string
- Properties: Create, Filter, Group, Nillable, Sort, Update
- Description: Used in Legacy Transaction Security only. A resource used to narrow down the conditions under which the policy triggers. For example, with a
DataExportevent, you can select a resource Lead to specifically monitor export activity occurring on your Lead entities. The resources available depend on theEventTypefield.
- Type: picklist
- Properties: Create, Filter, Group, Restricted picklist, Sort, Update
- Description: Indicates whether the policy is active.
- Possible values:
- Disabled — Disabled
- Enabled — Enabled
- Type: picklist
- Properties: Create, Filter, Group, Restricted picklist, Sort, Update
- Description: The type of validation that the policy uses. .
- Possible values:
- CustomApexPolicy — CustomApexPolicy — Created with Apex editor.
- CustomConditionBuilderPolicy — CustomConditionBuilderPolicy — Created with Condition Builder