Newer Version Available
What’s the Difference Between Classic Encrypted Custom Fields and Platform Encryption?
The following table compares Classic Encrypted Custom Fields and Platform Encryption solutions.
| Feature | Classic Encrypted Custom Fields (included in base user license) | Platform Encryption (additional fee applies) |
|---|---|---|
| Encryption at Rest | ![]() |
![]() |
| Native Solution (No Hardware or Software is Required) | ![]() |
![]() |
| Encryption Algorithm | 128-bit Advanced Encryption Standard (AES) | 256-bit Advanced Encryption Standard (AES) |
| HSM-based Key Derivation | ![]() |
|
| “Manage Encryption Keys” Permission | ![]() |
|
| Generate, Export, Import, and Destroy Keys | ![]() |
![]() |
| PCI-DSS L1 Compliance | ![]() |
|
| Text (Encrypted) Field Type |
![]() (Dedicated custom field type, limited to 175 characters) |
|
| Masking | ![]() |
![]() |
| Mask Types and Characters | ![]() |
|
| “View Encrypted Data” Permission is Required to Read Encrypted Field Values | ![]() |
![]() |
| Email Template Values Respect “View Encrypted Data” Permission | ![]() |
|
| Encrypted Standard Fields |
* |
|
| Encrypted Attachments, Files, and Content | ![]() |
|
| Encrypted Custom Short Text, Long Text Area, Phone, Email, and URL Fields | ![]() |
|
| Encrypt Existing Fields for Supported Custom Field Types | ![]() |
|
| Search (UI, Partial Search, Lookups) | ![]() |
|
| API Access | ![]() |
![]() |
| Available in Workflow Rules and Workflow Field Updates | ![]() |
|
| Available in Approval Process Entry Criteria and Approval Step Criteria | ![]() |
