DLP for Salesforce: Protecting CRM Data From Export to Exfiltration
Salesforce DLP protects CRM data inside Salesforce and after it leaves. Learn the seven export paths, what native controls cover, and how to close the gaps.

Key Takeaways:
- Salesforce data loss prevention (DLP) protects sensitive CRM data inside Salesforce and after it leaves.
- Data leaves Salesforce through seven ordinary paths: report exports, the Data Export service, Data Loader and API tools, connected apps, file downloads, copy and paste, and email or external sharing.
- Native controls such as Event Monitoring, Transaction Security Policies, and step-up authentication are worth turning on. None of them follows a file once it leaves Salesforce.
- The 2025 Salesforce thefts Google documented ran through authorized connected apps, not a platform flaw.
- Most exports are normal work. The risk sits in what happens next, so the export, the save, and the upload have to be read as one sequence.
- ORION Security detects downloads, uploads, and report exports from Salesforce that contain sensitive customer data. It reports first detections within 30 minutes of deployment.
Protecting Salesforce data now means following it past the export button. Controls inside Salesforce decide who can pull data out. Controls on the browser and endpoint decide what happens to it next. You'll need both for a complete program.
What Is Salesforce DLP?
Salesforce DLP is the set of controls that stop sensitive CRM data from being exposed, exported, or moved somewhere it shouldn't go. It covers data inside Salesforce, such as case comments and attachments, and data after it leaves, such as a pipeline report saved to a laptop and uploaded to a personal AI tool.
Most definitions stop at the edge of the org, which leaves out the moment CRM data actually moves: a download by someone with legitimate access. The same thinking applies to other SaaS apps, as our guide to cloud data loss prevention explains.
Where Sensitive Data Sits Inside Salesforce
Customer data doesn't stay on the Account record:
- Cases and case comments, where agents paste whatever the customer sent.
- Email-to-case threads, with full email bodies and signatures.
- Files and attachments, such as contracts and spreadsheets.
- Chatter posts, where teams share notes and files.
- Custom fields that hold identifiers nobody removed.
- Reports, which pull all of it into one exportable view.
How Data Leaves Salesforce: 7 Export Paths
Most Salesforce data leaves through ordinary features: report exports, the scheduled Data Export service, Data Loader and other API tools, connected apps that hold OAuth tokens, file and attachment downloads, copy and paste from records, and email or external sharing. Each path needs its own control, and several end on an employee's laptop.
| Path | Who normally uses it | Native Salesforce control | What that control can't see |
|---|---|---|---|
| Report exports | Sales managers, operations, finance | Export Reports permission, step-up authentication, Transaction Security Policies | Where the file goes after it's downloaded |
| Data Export service | Admins running weekly or monthly backups | Limiting who can run or schedule exports | The zip of CSV files once someone downloads it |
| Data Loader and API tools | Admins and integration users | API Enabled permission, connected app access policies | A modified tool a user was talked into authorizing |
| Connected apps with OAuth tokens | Chat, email, and enrichment integrations | OAuth scopes, IP restrictions, app approval | Queries run with a stolen token that look like the integration's normal work |
| File and attachment downloads | Support agents, account teams | Record access and sharing settings | The file on the laptop and every place it's copied next |
| Copy and paste from records | Anyone who can view the record | Field-level security | What leaves through the clipboard |
| Email and external sharing | Reps, support, partner teams | Email and sharing settings | What the recipient does with the data |
Four of the seven paths end with a file on a laptop. That's where Salesforce's own controls hand off.
Does Salesforce Have Built-In DLP?
No, not as a single product. Salesforce gives you strong pieces: Shield Event Monitoring logs report activity and API queries, Transaction Security Policies can block or flag risky actions such as large exports, and step-up authentication now challenges report exports. None of them follows a file once it leaves Salesforce.
Shield Event Monitoring
Event Monitoring records user activity in the org, including the reports people run and the queries API tools execute. It's one of four products in Salesforce Shield, alongside Platform Encryption, Field Audit Trail, and Data Detect, and each can be bought separately. Its logs don't follow data past the edge of the org.
Transaction Security Policies
Transaction Security Policies ship with Event Monitoring and act on events as they happen. Salesforce's own example is blocking a user from running a report with 100,000 customer records and exporting it. That's a good fit for volume. A small export of your top accounts can still pass under a volume threshold.
Step-Up Authentication on Report Exports
In 2026, Salesforce narrowed step-up authentication so it triggers only on report export, adding an identity check before the file is created. Salesforce describes it as a checkpoint that stops an attacker with a stolen session from extracting sensitive data. Sessions from an org's defined IP ranges are exempt, and the check confirms who's exporting, not where the file goes.
Setup Audit Trail, Field History, and Security Center
Setup Audit Trail records configuration changes, and Field History Tracking records changes to the fields you select. Security Center, a separate product, brings security settings and Shield data into one view. All three show how the org changed. They don't watch data leaving it.
How to Prevent Data Export From Salesforce in 6 Steps
Start inside Salesforce, then cover where exports land. Limit the Export Reports and API Enabled permissions to the people who need them, review connected apps and their OAuth scopes, turn on export logging and Transaction Security Policies, classify the fields that matter, and watch downloaded files on the browser and endpoint.
1. Limit Who Can Export Reports
The Export Reports permission controls who can download report data as a file. Grant it through permission sets to the roles that need it, and remove it from broad profiles.
2. Restrict API Access and Data Loader
Data Loader needs the API Enabled permission, which Google's threat researchers note allows broad data export. They recommend removing it from profiles and granting it only to authorized users through a permission set.
3. Review Connected Apps and OAuth Scopes
List every connected app with OAuth access and its scopes. Remove apps nobody owns, narrow scopes such as full access, enforce IP restrictions, and limit who can authorize new apps.
4. Log Exports and Set Transaction Security Policies
Turn on Event Monitoring and send its logs to your security tools. Add Transaction Security Policies for large exports and new connected apps, starting with alerts and moving to blocks once you know what normal looks like.
5. Classify the Fields That Matter
Decide which objects and fields hold the data you can't afford to lose, such as customer identifiers, pricing, and support case contents. Salesforce's Data Detect scans the org for sensitive data, and our guide to data classification covers how to set the levels.
6. Cover the Places Exports Land
Steps 1 through 5 decide who can take data out. Monitor downloaded files on managed laptops and in the browser, where a report can move to personal storage, personal email, or an AI tool within minutes.
Following a Salesforce Record After It Leaves Salesforce
A sales manager exporting a pipeline report is doing their job. The risk appears in what happens next: the file is saved, renamed, and uploaded to a personal AI tool or personal email. Salesforce's own logs stop at the export, so the sequence has to be read where the file travels.
Why the Export Itself Is Usually Normal
Sales, support, and finance teams export reports every day. Alerting on every export trains people to ignore alerts, and blocking every export stops the business.
The Sequence That Matters: Save, Rename, Upload
| Step | Where it happens | Visible in Salesforce's logs? |
|---|---|---|
| Report exported | Salesforce | Yes |
| File saved to the laptop | Endpoint | No |
| File renamed | Endpoint | No |
| File uploaded to a personal AI tool or personal email | Browser | No |
Each step looks normal alone, and Salesforce can't see three of them. Together, they show customer data moving from a sanctioned system to a personal account. With AI tools, the account matters more than the website, as we explain in personal vs. corporate ChatGPT and our guide to DLP for ChatGPT. Personal cloud storage follows the same pattern, as the public court record in How 12,000 Files Left Pfizer Through a Personal Google Drive shows.
Salesforce Data Exfiltration: How Recent Attacks Took CRM Data
Two well-documented Salesforce thefts in 2025 didn't exploit the platform itself. Attackers used stolen OAuth tokens from a connected chat app to query Account, Opportunity, User, and Case records, and another group talked employees into authorizing a modified Data Loader. Both ran through connected-app access an employee or integration had authorized.
For the broader set of techniques, see our guide to data exfiltration.
Stolen OAuth Tokens From a Connected Chat App
Google Threat Intelligence Group reported in August 2025 that a group it tracks as UNC6395 used compromised OAuth tokens from the Salesloft Drift integration to reach Salesforce customer instances between August 8 and at least August 18, 2025. The actor ran queries against Cases, Accounts, Users, and Opportunities, then searched the stolen data for credentials such as AWS access keys and passwords. Google states the issue didn't stem from a vulnerability in the core Salesforce platform.
Phone Calls That Authorize a Modified Data Loader
In June 2025, Google described a group it tracks as UNC6040 whose callers posed as IT support. They walked employees through Salesforce's connected app setup page to approve a modified version of Data Loader, then exported data from the org. Google reports that in every case it observed, the attackers manipulated users rather than exploiting a Salesforce vulnerability.
Departing Employees and Report Exports
Most CRM data loss isn't that dramatic. A departing rep exports an account list, or a manager saves a pipeline report to personal storage to work from home. Both start with an export the person was allowed to make, so the export alone doesn't show which is which. Our guide to insider threats covers the signals that separate accident from intent.
How ORION Security Sees Salesforce Data Movement
ORION Security connects to Salesforce and detects file downloads, uploads, and report exports that contain sensitive customer data. It then follows the exported file through the browser and endpoint channels it monitors, so a download that's normal for a sales role and an upload to a personal AI account are judged as one sequence.
The sales manager's export raises nothing, because it's normal for the role. When the same file reaches a personal AI tool minutes later, ORION Security weighs what the data is, where it came from, and who moved it where. The result is a verdict a reviewer can act on, not another line in a log.
On the browser and endpoint channels it monitors, teams choose whether a risky upload is monitored, gets a warning, or is blocked. ORION Security reports roughly five percent false positives in its production customer materials, which is a figure from its own deployments, not a universal rate.
Interested in ORION Security? Learn more.
Frequently Asked Questions
What does Salesforce Shield include?
Salesforce Shield bundles four products: Event Monitoring, Platform Encryption, Field Audit Trail, and Data Detect. Event Monitoring includes Transaction Security Policies. Each product can be bought separately, and Security Center is a separate product that brings Shield data together.
Why does Salesforce ask me to re-authenticate when I export a report?
That's step-up authentication. Salesforce added an extra identity check on report exports so a stolen session can't be used to pull sensitive data. Sessions from an org's defined IP ranges are exempt, so your admin's network settings decide how often you see it.
Can you stop users exporting reports in Salesforce entirely?
You can remove the Export Reports permission from everyone who doesn't need it. That stops file exports from the report screen for those users, but it doesn't affect API access, copy and paste, or screenshots. Most teams restrict the permission and monitor the people who keep it.
Does Salesforce DLP need data classification first?
No. Restricting export permissions, reviewing connected apps, and turning on logging don't depend on it. Classification decides which exports matter, so it becomes necessary once you start writing policies or judging what a download contained.
How do sandboxes increase Salesforce data exposure?
Full and Partial Copy sandboxes copy production data into environments that developers, testers, and contractors often reach more easily than production. Sandbox templates control which objects are copied, and Salesforce's Data Mask & Seed can anonymize sensitive fields before anyone uses the sandbox.
Does endpoint DLP protect Salesforce data?
Partly. Endpoint DLP sees a report once it lands on a managed laptop, which covers exports and downloads. It doesn't see data pulled through the API or a connected app, because that data never touches the laptop. Salesforce's own logs cover that side.

.webp)

.webp)