Chrome/Edge extension allowlist policy
Overview
Malicious extensions steal cookies and session tokens. Allowlisting reduces risk; balance against user demand.
Build the catalog
- Export current extensions in use (browser management reports or RMM inventory).
- Approve by business need; reject duplicates and deprecated extensions.
- Map extension IDs for Chromium policies.
Deployment
- Intune Administrative Templates for Edge/Chrome extension control.
- Block install from Web Store except allowlist; consider force-install of standard set (password manager, SSO helper).
Ongoing governance
- Monthly request queue for new extensions—security reviews phishing-prone categories (coupon, PDF converters).
- Remove extensions when vendor sunsets or CVE published.
User communication
Explain that allowlisting prevents shadow extensions that bypass MDM visibility.
Pitfalls
Overly strict policy driving personal device workarounds—pair with viable approved tools.
Related Articles
EDR deployment checklist for new workstations
## Overview Use this runbook when onboarding a new Windows workstation or re-imaging a device that...
Handling Defender for Business false positives
## Overview False positives waste analyst time and train users to ignore alerts. This article stand...
Application allowlisting with Windows Defender ASR rules
## Overview Attack Surface Reduction (ASR) rules reduce exploit surface by constraining Office macr...