Security Center

Centralized Threat Detection is now generally available. Create in-app and email alerts to instantly learn about changes to security settings that you want to monitor. Parse metric data with filters for the results view.

Security Center (salesforce.com)


Encrypt More Financial Services Cloud Data

You take your clients’ confidentiality seriously and so do we. Now you can add an extra layer of protection to deal information and data discussed in your interactions with Financial Services Cloud customers.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions.

Who: This change applies to editions that have both Shield Platform Encryption and Financial Services Cloud add-on subscriptions.

Why: You can now encrypt these Financial Services Cloud fields.

  • Financial Deal—Description, Financial Deal Code, Name
  • Financial Deal Interaction—Comment
  • Financial Deal Interaction Summary—Comment
  • Interaction—Description, Name
  • Interaction Summary—Next Steps, Meeting Notes, Title
  • Interaction Summary Discussed Account—Comment

How: On the Encryption Policy page in Setup, click Encrypt Fields. Then click Edit, and select the fields you want to encrypt.

Encrypt More Financial Services Cloud Data (salesforce.com)


Shield Platform Encryption

Bring even more security to Financial Services Cloud data with encryption at rest for deal and interaction fields.

  • Encrypt More Financial Services Cloud Data
    You take your clients’ confidentiality seriously and so do we. Now you can add an extra layer of protection to deal information and data discussed in your interactions with Financial Services Cloud customers.

Shield Platform Encryption (salesforce.com)


Retention Policy Now Associated with Only One Custom Object

Previously, a retention policy could be associated with both the custom object that you explicitly set it for and another custom object with a similar key prefix. This behavior no longer happens.

Where: This change applies to Lightning Experience, Salesforce Classic, and all versions of the mobile app in Enterprise, Performance, and Unlimited editions.

Who: Field Audit Trail is available to customers who purchased a Salesforce Shield or Salesforce Field Audit Trail add-on subscription.

How: A key prefix is the three-character code in an object ID that specifies the object type, such as 001 for Account. Let’s say you previously created two custom objects, Object1 and Object2, whose key prefixes differ only in their case sensitivity, such as a0B and a0b. You then defined a retention policy for Object1 but not Object2. Salesforce used to associate the same retention policy with Object2. Starting in this release, Salesforce no longer associates the policy with Object2.

Retention Policy Now Associated with Only One Custom Object (salesforce.com)


Field Audit Trail

When you set a retention policy on an object, Salesforce no longer sets the same policy for a different object with a similar key prefix.

Field Audit Trail (salesforce.com)


Review Threat Detection Data in Security Center (Generally Available)

Now generally available, Threat Detection integration with Security Center helps you understand threat event trends and plan your responses accordingly. You can view aggregated data about threat events for single and multiple orgs, and drill in to event details right from the Security Center app.

Where: This change applies to Lightning Experience in Enterprise, Unlimited, and Developer editions.

Who: This change is available to customers who purchase Salesforce Shield or Salesforce Event Monitoring add-on subscriptions.

Review Threat Detection Data in Security Center (Generally Available) (salesforce.com)


Review Bulk API 2.0 Workload Information

The new Bulk API 2.0 event log file type helps you query Bulk API 2.0 job information. Previously, Bulk API 2.0 information was available only on the Bulk Data Load Jobs page in Setup. Use the new event type to track how long Bulk API 2 jobs take to complete, what kinds of data they process and how much, who runs jobs, and more.

Where: This change applies to Enterprise, Performance, Unlimited, and Developer editions.

Who: The Bulk API 2.0 event type is free to all customers. Customers who purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions can use the EventLogFile object to monitor events.

Review Bulk API 2.0 Workload Information (salesforce.com)


Get the Namespace of Installed Managed Packages That Access Named Credentials

Capture information about Apex callouts that use named credentials as their endpoints with the EventLogFile object’s new Named Credential event type. This event type is ideal for auditing the installed managed packages that use named credentials. For example, you’re sometimes required to create a named credential as part of the installation of a managed package from an AppExchange partner. However, in previous Salesforce releases, you didn’t have a way to determine whether other packages also used the named credential, which was a potential security risk. This new event type allows you to track all packages that use a named credential and investigate packages you don’t recognize.

Where: This change applies to Enterprise, Performance, Unlimited, and Developer editions. This event is available in the API but not in the Event Monitoring Analytics app.

Who: The Named Credential event type is free to all customers. Customers who purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions can use the EventLogFile object to monitor events.

Get the Namespace of Installed Managed Packages That Access Named Credentials (salesforce.com)


Get Information About CORS Violation Records in the EventLogFile

The new CORS Violation Record event type in the EventLogFile object captures information about Cross-Origin Resource Sharing (CORS) violations for Lightning apps. Cross-origin requests to Lightning apps are blocked unless the request comes from a URL listed in your CORS allowlist. Use this event type to monitor CORS violation records and help you decide if your CORS allowlist requires an update before the Enforce CORS Allowlist for Lightning Apps release update is enforced. Currently, the CORS allowlist in Setup isn’t enforced for Lightning apps.

Where: This change applies to Enterprise, Performance, Unlimited, and Developer editions. This event is available in the API but not in the Event Monitoring Analytics app. It’s available for free for two releases because it’s intended to help you prepare for the enforcement of the Enforce CORS Allowlist for Lightning Apps release update.

How: CORS enables web browsers to request resources from origins other than their own. For example, using CORS, JavaScript code at https://www.example.com can request a resource from https://www.salesforce.com.

The Event Log File Browser application is the easiest tool to download event monitoring data. See these instructions.

Get Information About CORS Violation Records in the EventLogFile (salesforce.com)


Analyze Your Flows in the Flow Execution Event Type

To analyze the usage trends and performance health of your flows, access the new Flow Execution event type in the EventLogFile object.

Where: This change applies to Lightning Experience and Salesforce Classic in Enterprise, Performance, Unlimited, and Developer editions. This event is available in API version 53.0 and later but not in the Event Monitoring Analytics app.

Who: This change is available to customers who purchased the Salesforce Shield or Salesforce Event Monitoring add-on subscription and use the EventLogFile object data to monitor events.

Analyze Your Flows in the Flow Execution Event Type (salesforce.com)


Privacy Preference Center