Salesforce Security Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
Salesforce Security Guide
Salesforce Security Basics
Authenticate Users
Give Users Access to Data
Share Objects and Fields
Strengthen Your Data’s Security with Shield Platform Encryption
Audit and Monitor Your Organization’s Security
Real-Time Event Monitoring
Real-Time Event Monitoring Definitions
Considerations for Using Real-Time Event Monitoring
Enable Access to Real-Time Event Monitoring
Stream and Store Event Data
Create Logout Event Triggers
How Chunking Works with ReportEvent and ListViewEvent
Enhanced Transaction Security
Types of Enhanced Transaction Security Policies
ApiEvent Policies
ApiAnomalyEventStore Policies
BulkApiResultEventStore Policies
CredentialStuffingEventStore Policies
FileEvent Policies
ListViewEvent Policies
LoginEvent Policies
PermissionSetEventStore Policies
ReportEvent Policies
ReportAnomalyEventStore Policies
SessionHijackingEventStore Policies
Enhanced Transaction Security Actions and Notifications
Build a Transaction Security Policy with Condition Builder
Create an Enhanced Transaction Security Policy That Uses Apex
Best Practices for Writing and Maintaining Enhanced Transaction Security Policies
Enhanced Transaction Security Metering
Exempt Users from Transaction Security Policies
Test and Troubleshoot Your New Enhanced Policy
Threat Detection
Event Log File Browser
Store and Query Log Data with Event Log Objects
Security Guidelines for Apex and Visualforce Development
API End-of-Life Policy
PDF

ApiEvent Policies

API events monitor API transactions, such as SOQL queries and data exports.
Available in both Salesforce Classic (not available in all orgs) and Lightning Experience.
Available in: Enterprise, Unlimited, and Developer Editions

Requires Salesforce Shield or Salesforce Event Monitoring add-on subscriptions.

Policy at a Glance

Object Conditions Available in Condition Builder Actions Considerations
ApiEvent API Type, API Version, Application, Client, Elapsed Time, Operation, Platform, Queried Entities, Query, Rows Processed, Session Level, Source IP, User Agent, User ID, Username Block, Notifications Multi-factor authentication isn’t supported.

What You Can Do With It

You can monitor user behaviors taken through the API on a granular level. Create a policy that can:

  • Block access to particular versions of the API from specific platforms
  • Notify you when users run queries that return many rows

Considerations for ApiEvent Policies

  • The supported SOAP, REST, Bulk API, and Bulk API 2.0 calls are query(), query_more(), and query_all(). Transaction Security supports only query(). API calls made from Visualforce (via an Apex controller) or XMLRPC aren’t supported in ApiEvent and ApiEventStream.
  • For Bulk API and Bulk API 2.0 queries, expect blank values for LoginHistoryId, Client, and UserAgent in ApiEvent. These queries are asynchronous and executed by a background job.