Browsing Insights: see what your users actually do in the browser
Subtitle: SaaS discovery, AI-tool usage, and policy outcomes — without another agent on the wire.
You have EDR. You have email security. You still don’t know which SaaS apps, AI tools, or risky domains your users hit in the browser until something shows up on a credit report.
Browsing Insights is the Dual-Strike XISEM console for web session telemetry from Anti-Venom Secure Access — duration, categories, AI classification, risky flags, business-hours context, and investigation pivots.
Route: /browsing-insights
What you see
ViewOperator use Sessions over timeVolume trends — did rollout work? Top domains / SaaSShadow IT and unsanctioned apps AI tool usageChatGPT, Copilot, Claude, etc. Risky / blockedPolicy and reputation hits By user / by deviceInvestigation starting points Extension HealthWhich browsers report, which don’t
Data flows from Anti-Venom (direct cloud or agent relay — preferred at scale).
How it fits the stack
Deploy Dual-Strike XISEM Agent on the endpoint
Deploy Anti-Venom (Chrome, Edge, or Firefox — store GA on 8.7.x)
Publish browser policy in Settings → Browser Extension
Open Browsing Insights — filter by client, user, domain, time range
No manual Supabase URLs for end users. Production posture is agent-gated.
Recent improvements (8.7.0.17 platform)
Reliable session loading at MSP multi-client scope
24-hour default time window (better Monday reviews)
Extension Health weekend grace — spare laptops aren’t false “not detected” alarms
Tie-in to detections
Browser events feed COBRA² rules: shadow AI, DLP-class categories, exfil patterns. Turn on browsing first; tune detections second.
Start here
Pick one pilot client with agent + extension deployed
Confirm Extension Health shows green/idle — not “not detected”
Review top domains and AI sessions for a week
Add one COBRA rule for your highest-risk category
Docs path: Support wiki → Anti-Venom & Browsing Insights · dual-strike.com/downloads
Retention follows platform policy — aggregate reporting for large fleets should use rollups where available.