This sheet is past its review date. Deadlines or advice may have changed since 5 Nov 2026.
Browsers: which settings do you need to enforce?
This month, put Edge and Chrome under central management, force every update to apply within 72 hours and allow browser sign-in only with work accounts. Judge every other browser setting by whether it keeps stolen sessions, unmanaged devices or unapproved AI tools away from company data.
If you only do five things
Force updates to apply within 72 hours.
Updates apply only after a relaunch. Set RelaunchNotification to Required and RelaunchNotificationPeriod to 259200000 ms, the patching sheet's 72 hours for exploited flaws. RelaunchFastIfOutdated at 7 gives browsers over a week out of date 2 hours4.
Make malware and phishing warnings final.
Enable SmartScreen in Edge and block overrides with PreventSmartScreenPromptOverride and its ForFiles twin, which need domain-joined or MDM-enrolled devices6. In Chrome, set SafeBrowsingProtectionLevel and DisableSafeBrowsingProceedAnyway. In both, set DownloadRestrictions to 4 to block known malicious downloads47.
Let only managed devices reach company data.
Require a compliant device in Conditional Access. For personal Windows PCs, require an app protection policy: it admits Edge and blocks other browsers from Microsoft 36510.
Set up the browser baseline in this order
Find every browser and extension.
Chrome Enterprise Core reports each browser's version, extensions and policies2. Find other browsers, including AI browsers, in your device inventory.
Start from Microsoft's baseline.
Assign Intune's Edge security baseline, version 139 from April 202613, and match it in Chrome. Use Extended Stable, which moves every 8 weeks, only where testing needs it14.
Connect Chrome to Entra ID.
On Windows, set CloudAPAuthEnabled to 1. Chrome then signs users in to Microsoft sites with their Windows work account4 and can pass device checks in Conditional Access12.
Turn off developer tools for most staff.
Set DeveloperToolsAvailability to 2; the NCSC notes the console can aid social engineering8. Exempt developers by group, or allow internal sites with DeveloperToolsAvailabilityAllowlist4.
Then allowlist extensions.
Follow the endpoints and email sheet, and review AI extensions first. Microsoft found a malicious extension campaign with about 900,000 installs that harvested AI chat histories and prompts16.
Stolen session cookies: what each defense covers
- Software alone can't stop cookie theft. Google says no software-only method reliably stops it17; infostealers increasingly target session tokens16.
- App-bound encryption (Windows, version 127+). It forces malware to gain system rights or inject into the browser, so it helps most where users can't run downloads as admin20. Keep ApplicationBoundEncryptionEnabled on21.
- Remote debugging. Attackers turned to it to pull cookies, so Chrome 136 blocked it on the default data directory22. Set RemoteDebuggingAllowed to false outside developer groups4.
- Device Bound Session Credentials. On by default for Google Workspace accounts in Chrome 146+ on Windows with a TPM; require it per app with context-aware access18. Other sites must adopt it themselves17.
- Entra token protection in browsers. A preview covers the Azure portal and Entra and Intune admin centers in Edge or Chrome on Windows 11 or managed Macs, with Microsoft's Single Sign On extension; it blocks other web apps that use Azure Resource Manager19.
Profiles, sync and passwords
- Decide on personal browsing. Edge for Business keeps a personal window apart from the work one, with its own cache and storage and no shared passwords, and still applies your security and update policies, but the sign-in restriction above removes it23; choose per user group. On Google Workspace, set Chrome's ProfileSeparationSettings to Enforced4.
- Limit what syncs. Exclude types such as passwords with SyncTypesListDisabled4. The BSI's federal standard requires turning off cloud sync of credentials, cookies and history9.
- Keep passwords in one place. The BSI advises external password managers because built-in ones usually fall short9; the NCSC accepts built-in ones8. With a business password manager (SSO, shared vaults, offboarding), set PasswordManagerEnabled to false and have staff move saved passwords, which keep working4. Without one, keep the built-in manager and its sync in work profiles.
AI features and AI browsers
- Assume they are in use. Microsoft saw AI browsers in daily use at over 40% of organizations in its data16. For agent risks, see the agentic AI and AI input security sheets.
- Copilot in Edge. EdgeEntraCopilotPageContext decides whether Copilot reads pages and history in work profiles; unset, it's off in the EU but users can turn it on24. Its browsing agent is a preview closed to EEA tenants25.
- Gemini in Chrome. Not offered in the EU yet. GeminiSettings turns it off. If you allow it, set GeminiActOnWebSettings to 1: Google calls auto browse off by default for managed users26, but the policy list says unset allows it4.
- Other AI browsers. Block them with application control until you've checked which of your policies they honor.
What changed in 2026
- Major releases every two weeks. Edge 152 on 27 August and Chrome 153 on 8 September moved Stable to a two-week cycle; Extended Stable keeps eight weeks1415.
- Session binding shipped. DBSC became publicly available in Chrome 146 on Windows in April17. Entra token protection gained a browser preview for Azure admin portals19.
- Browser agents arrived. Google says Chrome's auto browse is off by default for managed users26; Edge's browsing with Copilot needs an admin's allow list25.
What you can skip
- Buying an enterprise browser first. Edge management and Chrome Enterprise Core already handle policies and extensions12. Buy Chrome Enterprise Premium only for gaps such as DLP or context-aware access3.
- Disabling JavaScript or password autofill. The NCSC says using the web reliably and securely can be very difficult without them8.
- Copying the BSI's federal standard line by line. Written for federal networks with a central blocklist, it advises turning off protection that checks sites with external services9, which would cost you SmartScreen and Safe Browsing.
Mistakes that cost the most
- Counting a downloaded update as installed. Without RelaunchNotification, only a subtle menu change asks for the relaunch4.
- Turning off app-bound encryption for roaming profiles. It doesn't work where profiles roam20, but disabling it lets other apps retrieve the browser's keys21. Fix the roaming setup instead.
- Setting one policy in two consoles. Group Policy and MDM override the Edge management service1, so cloud settings can silently lose.
- Resetting only the password after an infostealer. Invalidate sessions in every SaaS the browser used and check what the attacker reached16.
What this looks like at your size
Small team, no security staff
- Standardize on Edge, manage it in Intune and assign the Edge security baseline.
- Set the relaunch deadline, sign-in restriction and SmartScreen overrides from the five things.
- Block unmanaged devices, or give them SharePoint's limited web-only access11.
Growing, with IT or security staff
- Enroll Chrome in Chrome Enterprise Core with the same settings.
- Require Intune app protection for Edge on personal Windows PCs.
- Pilot token protection in the Azure portal for admins.
Enterprise or regulated
- Enforce token protection for admins and, on Google Workspace, DBSC through context-aware access.
- Add browser DLP for AI sites and other unmanaged cloud apps, as the DLP sheet describes.
- Report weekly on browsers past the 72-hour deadline and extensions off the allowlist.