Skip to main content
The browser collector covers AI usage you don’t control at the server: employees using third-party AI web apps (ChatGPT, Copilot, Claude, internal tools). A Chrome / Edge / Firefox extension intercepts the prompts and responses in the page and calls /v1/guard.

​
Setup

The extension is provided by NeuralTrust and deployed to managed devices via MDM, GPO, or Intune — there’s no per-user install. The steps shown in the collector side panel:
  1. Create an API key on the collector.
  2. Add the extension ID to your MDM policy.
  3. Set the policy endpoint (your TrustGuard host) and enrolled realm.
  4. Deploy to managed browsers.
Once deployed, the extension hooks the AI app’s request/response in the page and calls /v1/guard (direction:"input" for prompts, direction:"output" for responses). It reports the browser user’s enterprise identity as consumer_id and groups activity into sessions automatically, then acts on the verdict — warning or blocking the user, or masking content before it’s sent.

​
What it’s good for

  • Shadow-AI coverage — apps with no server-side integration point.
  • DLP at the source — catch PII/secrets before they leave the browser, using a data_loss_prevention detector with the Transform or Block action.
  • Per-user attribution — the browser knows the signed-in user, so behavioral and multi-turn detection are accurate.

​
Notes

  • Use a dedicated collector (and policy) for browser traffic so its rules and telemetry are separate from server-side collectors.
  • Because enforcement happens in the page, treat the browser collector as a control for managed devices; pair it with edge/WAF or gateway collectors for defense in depth.