There are several situations that can affect onboarding to the different Shield
Platform Encryption features. These depend on the encryption policies you have adopted, and
whether you already are using one or more Shield Platform Encryption features.
Required Editions
Available in both Salesforce Classic (not available in all orgs) and Lightning
Experience.
Available in: Enterprise, Performance, and Unlimited
Editions with the Salesforce Shield or Shield Platform Encryption licenses.
Available for free in Developer Edition.
Onboard Database Encryption Database Encryption will give you sufficient encryption coverage for your org's data in Salesforce's transactional database.
Onboard Field-Level Encryption FLE enables you to apply fine-grained encryption to standard and custom fields. You can use FLE with or without Database Encryption enabled.
Onboard Search Index Encryption Search is a feature integrated into your Salesforce org. Search Index Encryption encrypts your search indexes, protecting any sensitive information that may exist within them. Search Index encryption is a feature that you can turn on and off. You can also rotate the root key, DEK, or tenant secret within the allowed rotation cycles.
Onboard BYOK Switch from Salesforce-generated keys to Bring Your Own Key (BYOK) for Shield Platform Encryption.
Onboard EKM With EKM you can use your key material housed in an external KMS. If you are currently using a Salesforce-generated root key or DEK, and you want to move to EKM, you can if the Shield Platform Encryption feature supports EKM. EKM is currently available for Platform Encryption for Data 360, Fields and Files (probabilistic), Fields (deterministic), Event Bus, and Shield Platform Encryption Search Indexes.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.