Data in production is encrypted by a variety of keys, some of which you control via
Shield Platform Encryption. When you move data out of production and into an archive, Salesforce
encrypts it with a data encryption key (DEK) that you can pair with a root key via Shield
Platform Encryption. You control your root key, which means you maintain control of all keys
that encrypt data while it’s in the archive.
Required Editions
Available in both Lightning Experience and Salesforce Classic (not available in
all orgs).
Available in: Enterprise, Performance, Unlimited, and
Developer Editions. Requires purchasing Salesforce Shield or Shield
Platform Encryption and the Archive add-on license in Hyperforce.
Encryption for Archive uses a two-tier key architecture. You control your Archive root key
with Platform Encryption, which Salesforce uses in turn to protect the data encryption keys
(DEKs) that encrypt and decrypt data in your archive. When you turn on encryption for Archive
in Setup or via the API, Salesforce generates an initial root key for you. It’s applied to all
of your archived data.
After that first root key is created, you can opt to use Bring Your Own Key (BYOK) or the
Shield External Key Management (EKM) to generate root keys outside Salesforce. To bring your
own key, generate a root key and then upload it. When you have data residency or other
requirements that dictate that keys be stored outside of Salesforce, generate and store your
root key in an AWS KMS key store. Then connect your root key to Salesforce via Shield EKM.
Regardless of how you generate or store root keys, review and audit all of your root keys on
the Key Management page in Setup.
Note Archive root keys encrypt archived types in the native Archive app. Root keys don’t
encrypt data archives made with the Own from Salesforce Archive managed package or legacy
Salesforce Archive.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
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.