For many organisations, Salesforce is the heart of their relationship management, fundraising, service, marketing and programme management. It not only contains names and contact details, but often also donation history, cases, preferences, segmentations, communication history and integrations with external systems.
That makes Salesforce valuable. But it also means that you need to know well which data is sensitive, who can access it, what happens to it and for how long changes remain verifiable.
Here it comes Salesforce Shield pictured.
Salesforce Shield is a suite of four security products on top of the platform's standard security: Platform Encryption, Field Audit Trail, Event Monitoring and Data Detect. Together they help organisations to better protect sensitive data, monitor usage, retain changes for longer periods and recognise sensitive information more quickly.
Why standard Salesforce security is sometimes not enough
Salesforce already offers plenty of security features as standard. Think of MFA, profiles, permission sets, sharing rules, field-level security, login policies and Security Health Check. For many organisations, that is the foundation.
However, some organisations need more. For example, because they work with sensitive personal data, medical data, donor data, financial data or compliance requirements from laws and regulations. Then simply restricting access is not enough. You also want to be able to encrypt data, monitor anomalous behaviour, track down sensitive fields and retain changes for longer.
Salesforce Shield helps precisely at that level: not only who is allowed to join, but also what happens to the data, how do we protect that data, and how do we prove that afterwards?
Platform Encryption: encrypting sensitive data
With Platform Encryption can you encrypt sensitive data in Salesforce. Think about fields, files, attachments and search indexes. Salesforce describes that organisations can use this to set encryption policies and gain more control over the lifecycle of encryption keys themselves, including capabilities such as key rotation and Bring Your Own Key.
For impact organisations, this may be relevant when Salesforce contains data that requires extra protection. Think of sensitive cases, special category personal data, financial information, or data that you do not want to end up unprotected in systems or exports.
One thing is important, though: encryption is not a substitute for proper permission management. Platform Encryption is an extra layer of protection. You still need to ensure that profiles, permission sets, sharing and integrations are properly configured.
Field Audit Trail: demonstrating changes for longer periods
With standard field history tracking, you can track changes to fields, but for organisations with stricter auditing or compliance needs, that is often not sufficient. Field Audit Trail makes it possible to retain field history for much longer, with retention policies that can extend to long-term retention periods such as ten years or longer, depending on the configuration and licence terms.
Salesforce positions Field Audit Trail as a solution to reinforce data integrity and make changes to critical fields auditable: who changed what, when did it happen, and what were the old and new values?
That is valuable for audits, incident investigation and governance. When a bank account number, donation status, consent value, case field or risk classification is modified, you sometimes want to know not only that something has been changed, but also by whom, when and from what to what.
Event Monitoring: see what is happening in your Salesforce environment
Event Monitoring provides insight into user activity and system usage. Salesforce cites examples such as logins and logouts, API calls, report exports, Apex executions, page load times and user interactions. This allows you to better monitor who has access to which data and which activities may be anomalous or risky.
For security this is important because many incidents do not start with a technical alarm, but with anomalous behaviour. A user suddenly exports a lot of reports. An integration makes an unusually high number of API calls. There are login attempts from unusual locations. Or an account is used in a way that does not fit normal working behaviour.
Event Monitoring allows you to spot such signals earlier. In combination with Transaction Security Policies, you can also set up policies to block risky actions or trigger notifications.
Data Detect: discovering sensitive data
An organisation can only properly protect data if it knows where sensitive data is located. In practice, this is often harder than it seems. Sensitive information can end up in free text fields, notes, legacy objects, description fields or custom fields that no one remembers the exact purpose of anymore.
Data Detect helps to discover and classify sensitive data in Salesforce. Salesforce gives examples such as credit card numbers, national identification numbers, email addresses and other sensitive patterns. Organisations can also define their own patterns using regular expressions, for example for industry-specific or organisation-specific data.
This is relevant for impact organisations because sensitive data sometimes grows organically. An employee enters extra information in a text field. An old form writes data to a field that was never marked as sensitive. An integration puts data in a place where no one looks later on. Data Detect helps to make such blind spots visible.
Shield is not a replacement for good management
Salesforce Shield is powerful, but it doesn't solve everything automatically. It's no excuse to skip basic measures.
Before deploying Shield, the basics must be in order:
- MFA and login policies;
- least privilege;
- current profiles and permission sets;
- controlled Guest User Access;
- management of Connected Apps and OAuth Usage;
- clear API and integration users;
- periodic security audits;
- ownership of data, processes and follow-up.
Shield sits on top of that. It helps organisations that want or need to go further in protection, monitoring and compliance.
What does this mean for organisations that run on trust?
For organisations that run on trust, Salesforce Shield is particularly interesting because it helps to better answer three questions:
Where is our sensitive data located?
Data Detect helps to find and classify sensitive information.
How do we provide extra protection for that data?
Platform Encryption helps to store sensitive data encrypted and to manage encryption keys.
Can we prove afterwards what happened?
Field Audit Trail and Event Monitoring help to make changes, access and user activity transparent.
That makes Shield not just a technical security solution, but also a governance instrument. It helps organisations to make trust demonstrable.
More than the standard configuration
Salesforce Shield is intended for organisations that need more than standard configuration alone. With Platform Encryption, Field Audit Trail, Event Monitoring and Data Detect, you get greater control over sensitive data, user activity, changes and compliance.
But the core remains the same: technology only works properly when it is part of a broader approach. Salesforce Shield delivers extra protection and insight, but digital resilience only arises when people, processes, rights, integrations and monitoring well organised together.
For impact organisations, that is essential. After all, anyone who works from a basis of trust must also be able to demonstrably protect that trust.