Microsoft Edge is the default browser in a huge slice of the market: Entra-joined laptops, VDI pools, and “we standardized on Edge for compliance” shops. If your secure browsing policy only lived in Chrome, you were always one default-browser setting away from a gap.
That gap closes today.
Anti-Venom Secure Access — the Dual-Strike XISEM browser extension — is available on the Microsoft Edge Add-ons store, alongside Chrome Web Store and Firefox Add-ons, aligned on the current 8.7.x release line.
What Anti-Venom does (in plain language)
Anti-Venom is not a generic “web filter.” It’s the browser-side enforcement and telemetry layer for Dual-Strike XISEM:
• Session visibility — domains, duration, AI-tool usage, risky categories (feeds Browsing Insights)
• Policy enforcement — allow, warn, and block with verdict watermarks your analysts can explain
• Agent-gated posture — production deployments pair the extension with the Dual-Strike XISEM Agent on the same endpoint so policy and telemetry stay under your control (LocalApi / agent relay paths — not ad-hoc user configuration)
End users don’t paste API keys. MSPs deploy agent + extension through RMM, Intune, or store policy — the same playbook you already use for Chrome.
Why Edge store matters
Enterprise Edge deployments often block sideloads and unsigned CRX paths. Store distribution means:
• Fewer “organization blocked this extension” tickets
• Cleaner alignment with Intune / Edge management policies
• One version line with Chrome and Firefox — no shadow 6.x installs fighting your 8.7 fleet
What to do
1. Confirm Dual-Strike XISEM Agent 8.7.x is deployed to the endpoint (extension expects the agent companion).
2. Deploy Anti-Venom from the Edge Add-ons listing (or your existing enterprise force-install policy pointing at store IDs).
3. Publish browser policy in Settings → Browser Extension; allow ~15 minutes for refresh.
4. Open Browsing Insights and Extension Health to confirm check-ins.
Downloads & store links: dual-strike.com/downloads
Questions about monitor vs protect modes or learning vs enforce? That’s a great follow-up post — reply here and we’ll cover deployment tiers next.