Skip to main content
App security

Category: IT & Support

Secure Intercom browsing

Secure Intercom browsing means protecting support and success teams from risky links and file shares while they handle customer conversations in a browser.

Quick answer

Support tools bring outside links and files into daily work. Agents open them at high volume. Treat customer links and attachments as untrusted.

Last updated

2026-01-29

Main browser risks for Intercom

  • Customer-provided links leading to phishing pages, scam sites, or malware downloads.
  • Attachments shared in conversations that contain malicious files.
  • Impersonation attempts where attackers pose as customers to request credential resets or sensitive actions.
  • Session hijacking risk from high volumes of external content and link-clicking.
  • Copy/paste leakage of customer data into untrusted tools or AI prompts.

Typical sensitive data in Intercom

  • Customer identity and account details (PII).
  • Conversation transcripts and internal notes.
  • Attachments and screenshots shared for troubleshooting.
  • Links to customer environments and internal tools.
  • Automation rules and templates.
  • Admin and access settings.

Recommended controls by role

Support

  • Open customer links in isolation by default; treat them as untrusted.
  • Restrict downloads of attachments from unknown senders; scan and release through a controlled workflow.
  • Avoid pasting customer PII into untrusted web tools or AI prompts; use approved systems for summarization and analysis.

IT Admins

  • Enforce extension allowlists and permission controls for support teams.
  • Isolate unknown domains and redirect chains commonly encountered in support workflows.
  • Use separate profiles for admin actions vs daily support work.

Security

  • Use isolation for investigation of suspicious links and scam pages encountered by agents.
  • Monitor for unusual exports and admin changes in customer support platforms.
  • Deploy controls to reduce data leakage into AI tools from browser-based support workflows.

Where Shield fits with Intercom

The controls above are general security practices, not Legba features. Intercom 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.

Add to Chrome

Free for 30 days. No card required.

Intercom security questions

Are support chat tools a common attack vector?
They can be. Attackers exploit any channel that gets agents to click external links or open files from unknown sources.
Does isolation slow down support work?
When scoped to unknown links and risky domains, isolation typically keeps work fast while reducing endpoint exposure.
Should we block all external links in support chats?
That usually breaks support. Isolating unknown links and controlling downloads is a more practical approach.
How do we reduce data leakage risk?
Treat customer data as sensitive: prevent copy/paste into unapproved tools and enforce policies for AI prompts.

References

  1. 01
    Intercom SecurityIntercom
  2. 02
    Cloudflare: Browser IsolationCloudflare
  3. 03
    Chrome Enterprise: PoliciesGoogle

Keep exploring

Try it on the next page you do not trust

Legba is a Chrome extension with two modes. Ghost gives you a private browser route. Shield opens a page in an isolated browser off your device.

Add to Chrome

Free for 30 days. No card required.

Ghost. A private route for your browser. Shield. An isolated browser, off your device. Choose the mode. Close when finished.