Category: IT & Support
Secure Zendesk browsing
Zendesk's trust center lists SOC 2 Type II. It also lists ISO 27001:2022. Agents still open customer links and files all day.
Quick answer
Zendesk lists its audits in a public trust center. They include SOC 2 Type II and ISO 27001:2022. ISO 42001 appears too. Those cover Zendesk's systems, not your agents' browsers. Agent risk comes from the job itself. Agents open customer links and files all day. Some lead to phishing pages or malware. Verify account change requests outside the ticket. Open unknown customer links in an isolated browser.
Last updated
2026-11-01
Main browser risks for Zendesk
- Customer-provided links in tickets leading to phishing pages or malware downloads.
- Attachments uploaded by external users containing malicious files.
- Impersonation attempts that push agents to “verify” accounts or change credentials via links.
- Session hijacking risk because agents often handle high volumes of external content.
- Copy/paste leakage of customer data into untrusted tools or AI prompts.
Typical sensitive data in Zendesk
- Customer PII and account details.
- Ticket conversations and attachments.
- Links to internal tools and customer environments.
- Screenshots and logs shared during troubleshooting.
- Macros and templates that may include sensitive process details.
- Agent and admin settings.
How agents should handle ticket content
| Ticket content | Risk | Safe handling |
|---|---|---|
| Links in tickets | Phishing pages and drive-by downloads | Check the domain; open unknown links in an isolated browser |
| Attachments | Malware in documents and archives | Scan before opening; ask for screenshots instead of files |
| Screenshots and logs | Customer data or secrets shared by mistake | Redact or delete what you do not need |
| Account change requests | Impersonation to change email, password, or MFA | Verify through the contact method already on the account |
Handling steps are general practice. Zendesk's trust center describes redaction for deleting attachments. Checked October 30, 2026.
Recommended controls by role
Support
- Open customer-provided links in an isolated browser.
- Scan attachments from unknown senders before opening them.
- Keep customer PII out of unapproved AI tools.
IT Admins
- Require SSO or 2FA for agents and admins.
- Restrict agent access to trusted IP ranges where it fits.
- Enforce extension allowlists for support teams.
- Use separate profiles for admin access vs daily ticket handling.
Security
- Investigate suspicious links agents report in an isolated browser.
- Monitor unusual exports and admin actions in Zendesk.
- Set an AI use policy for ticket data.
Where Shield fits with Zendesk
The controls above are general security practices, not Legba features. Zendesk is not a Legba integration.
Legba's part is narrow. Shield opens a page in an isolated browser off your device. Use it for a link you do not trust.
Limits
Shield moves page execution off your device. Downloads and copied data still cross that boundary. It cannot stop you sharing passwords with unfamiliar sites. Treat downloads and sign-in prompts with care.
Free for 30 days. No card required.
Zendesk security questions
Is Zendesk secure?
Should support agents open customer attachments?
How do attackers impersonate customers in tickets?
Does isolation replace antivirus and file scanning?
References
- 01Zendesk Trust CenterZendesk
- 02
- 03
Keep exploring
- How to open a suspicious link safelyVerify the sender first. Isolate only what you must inspect.
- ShieldShield opens a page in an isolated browser off your device.
- All guidesThreats, secure apps, and AI security pages.
- All secure app guidesBrowse apps by category.
- Browser threatsUnderstand threats and mitigation patterns.
- AI security guidesBrowse guides about AI prompt leakage and prompt injection.
