Security, Data Protection & Key Governance
Shield Platform Encryption is not an access-control model
Encryption does not change who can see data
A team encrypts a National ID field and expects service agents to see masked values. The agents still see the identifier because their object, record and field permissions allow it. The implementation is declared broken, yet it is working as designed: Salesforce explicitly states that a user authorised to see data can see it whether or not the data is encrypted.
The JSBC Labs position is that Shield Platform Encryption is a data-protection control—not an access-control model. It reduces exposure if stored data or infrastructure is compromised and adds customer-controlled key lifecycle capabilities. It does not replace least privilege, sharing, field-level security, careful page design or data minimisation. Confusing these control planes creates expensive encryption projects that leave the original visibility risk untouched.
Start with classification and a threat model
Do not begin by selecting every field that looks sensitive. Classify the data, identify who owns it, establish retention obligations and name the threats the control must address. Salesforce's Well-Architected guidance connects classification to concrete controls such as encryption, access, retention and monitoring. That produces a defensible scope instead of a catalogue of fields encrypted because their labels contain words such as secret or personal.
Separate storage compromise, privileged-user misuse, accidental disclosure and downstream leakage. Encryption at rest is relevant to the first threat; authorisation, monitoring and minimisation address the others. Salesforce already provides baseline infrastructure encryption, while Shield adds selective field encryption and additional key control. Encrypt where regulation, contractual commitments or risk justify those capabilities. Over-encryption increases operational complexity without automatically improving the outcome.
Keep authorisation as a separate design
For every encrypted field, define who can read it, who can update it and which automated identities can process it. Enforce those decisions through object permissions, field-level security, sharing and permission-set assignments. Review reports, list views, APIs and integration users as well as record pages. A hidden component is not a security boundary, and ciphertext at rest does not make plaintext unavailable to an authenticated process with access.
Salesforce describes data masking in this context as a troubleshooting aid for encryption-key issues, not a way to control visibility. If the requirement is to show only the last four digits, model that experience explicitly: restrict the source field, expose a purpose-built display value and control any privileged reveal path. Test with real personas. An administrator's successful encryption check says nothing about whether a frontline user has excessive access.
Choose the encryption scheme deliberately
Probabilistic encryption is the default and produces different ciphertext for identical plaintext, strengthening resistance to pattern analysis. The trade-off is that encrypted values cannot support equality filtering in the same way. Deterministic encryption produces consistent ciphertext for matching values, enabling exact-match filters, but it reveals equality patterns and therefore provides a different security profile. This is a risk decision, not a setup preference.
Design from required business operations. If a support process must find a customer by an encrypted membership number, deterministic encryption may be justified for that field. Salesforce documents important limits: exact matches are supported, while operations such as LIKE, STARTS WITH, ORDER BY and GROUP BY are generally not. Case-sensitive and case-insensitive modes also differ. Record the chosen scheme, query requirement and accepted leakage for every field.
Inventory functional consequences before enabling
Encryption can affect search, filters, reports, formulas, validation logic, duplicate detection, indexes and integrations. Create an impact map that links each candidate field to every feature and consumer that reads or compares it. Then test those behaviours in a representative environment. A checkbox-level rollout plan will miss the operational dependency that only appears when a nightly job groups records or an external service performs partial matching.
Treat unsupported behaviour as a design constraint rather than a defect to work around with copied plaintext. A separate searchable token, approved surrogate or narrower business key may be safer than weakening the encryption scheme. Revisit whether the process needs the sensitive value at all. The best result is often less data in Salesforce, fewer users able to retrieve it and fewer copies crossing trust boundaries—not more elaborate handling of the same secret.
Key lifecycle is an operating model
Salesforce derives data-encryption keys using key material protected by hardware security modules, and Shield gives customers options for managing key material and rotation. Those capabilities introduce responsibilities. Restrict Manage Encryption Keys, separate key administration from routine platform administration and require recorded approval for rotation, import, archive and destruction. A powerful control without clear decision rights becomes a concentrated operational risk.
Define rotation frequency, re-encryption expectations, recovery evidence and incident procedures. Salesforce notes that new data uses the current key while older data can remain encrypted under older keys until it is re-encrypted. Key destruction can make protected data unrecoverable, so rehearse the decision path and backup dependencies before an emergency. Measure coverage by key version rather than assuming that generating a new key completed the rotation.
Protect the complete data path
Enabling encryption for a field does not automatically transform every existing value. Salesforce's best-practice guidance calls for background encryption or an update process for existing data. Plan that migration, verify completion and account for files and attachments separately. Include failure handling and capacity considerations; a partially encrypted estate is especially dangerous when governance documentation claims uniform protection.
Trace the data beyond the record. Exports, logs, email, analytics stores, backups and receiving systems need their own controls. Platform event messages also require event-bus encryption to be enabled; field encryption on a source record does not silently protect a copied event payload. Define the protection state at each hop, the identity allowed to decrypt and the retention period. Encryption boundaries should follow data movement, not product boundaries.
Test security and operability together
Build regression tests around user access, queries, reports, automations, integrations and key operations. Prove both sides of the contract: authorised processes still work, and unauthorised personas cannot obtain the value through the UI, API or reporting. Test historical data as well as newly created records, and include rotation and re-encryption in release rehearsals. Representative volume matters because remediation and background operations can change the deployment window.
Operate encryption with a dashboard of classified fields, chosen schemes, data owners, key versions, migration status and failed jobs. Review privileged permissions and exceptions on a fixed cadence. Run a recovery exercise before relying on destructive key actions in an incident. Shield Platform Encryption is strongest when it is one layer in a coherent protection model—classification defines the need, authorisation limits use, encryption protects storage and monitoring proves the controls remain effective.
Official references
- Salesforce Help — Why Isn't My Encrypted Data Masked?
- Salesforce Help — Shield Platform Encryption Best Practices
- Salesforce Help — How Deterministic Encryption Supports Filtering
- Salesforce Help — Considerations for Using Deterministic Encryption
- Salesforce Help — How Shield Platform Encryption Works
- Salesforce Architects — Data Protection and Privacy Patterns
- Salesforce Architects — Trust
- Salesforce Developers — Encrypting Platform Event Messages at Rest in the Event Bus