Category: CRM & Sales
Secure Salesforce browsing
Secure Salesforce browsing means protecting CRM logins, sessions, and customer data from phishing and session theft while sales teams work in the browser.
Quick answer
Legba can isolate browser sessions while your team uses Salesforce.
Sales tools are link-heavy and often connected to inbound email and outreach. Isolation helps reduce exposure from external links and downloads that reach Salesforce users.
This page does not imply an official integration with Salesforce—it’s a guide to securing browser workflows around the app.
When you need this
- Your team uses Salesforce in a browser every day.
- You want to reduce phishing, malicious downloads, and session theft without slowing users down.
- You need role-based policies for employees, admins, and contractors.
Last updated
2026-01-29
Common browser risks
- Lookalike Salesforce login pages and SSO prompts that steal credentials or tokens.
- Session hijacking that reuses an authenticated session to access customer data.
- Phishing links embedded in records, emails, or integrations that route reps to malicious destinations.
- Data leakage when reps copy customer details into untrusted tools or AI prompts.
- Malicious downloads from external links (pricing sheets, PDFs) clicked during sales workflows.
Typical sensitive data in Salesforce
- Customer and prospect PII (names, emails, phone numbers).
- Pipeline details, deal notes, and pricing information.
- Contracts, quotes, and order forms.
- Support and account history linked to records.
- Integration tokens and connected app permissions (depending on setup).
- User access roles and login history.
Recommended policies by role
Sales
- Open unknown external links from records and emails in isolation by default.
- Restrict downloads from unfamiliar domains; use a scan-and-release workflow for shared PDFs and docs.
- Avoid pasting customer PII into untrusted web tools or AI prompts; use approved systems.
IT Admins
- Enforce SSO and strong session controls; require re-auth for sensitive changes.
- Use browser policies to restrict extensions and risky permissions across sales teams.
- Isolate ad-click and unknown domains to reduce phishing exposure without blocking research.
Security
- Monitor for anomalous logins and session behavior; investigate new OAuth grants and connected apps.
- Use isolation for investigation of suspicious links and external file shares.
- Prioritize controls for roles with broad CRM exports and admin access.
FAQs
Is Salesforce a common phishing target?
Yes. CRM access is valuable and commonly accessed through the browser, making it a high-leverage target for credential and token theft.
How does isolation help a sales team?
It lets reps click and research without running untrusted web content on their endpoints, and supports tighter download controls for risky sources.
Should Salesforce itself be isolated?
Many teams keep Salesforce normal but isolate unknown external links and risky sources. For admin workflows, stricter profiles or isolation may be appropriate.
What’s the biggest data leak risk in CRM?
Copy/paste into unapproved tools and accidental sharing/exports. Combine browser controls with governance and least-privilege access.
References
- Salesforce Trust — Salesforce
- Cloudflare: Browser Isolation — Cloudflare
- Chrome Enterprise: Policies — Google