/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:- Create an API key on the collector’s Auth tab.
- Add the extension ID to your MDM policy.
- Set the policy endpoint (your TrustGuard host) and enrolled realm.
- Deploy to managed browsers.
/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_preventiondetector inredactorblock. - Per-user attribution — the browser knows the signed-in user, so behavioral and multi-turn detection are accurate.
Notes
- Use a dedicated collector (and detector chain) for browser traffic so its policies 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.