Should we make ad blocking part of our browser security policy?

November 16, 2026 5 answers
Asked by u.368!marbleclip

I'm considering an ad blocker for managed browsers alongside an approved-extensions policy. What security benefits and trade-offs should we assess, and how should we explain the proposal to nontechnical leadership?

Answers

_a73!ferryquartz.6

It can be a reasonable security control. Blocking ads can reduce exposure to malicious advertising, but it won't stop every malicious site or extension. I'd present it as one layer, not a replacement for browser updates, web filtering, or other endpoint controls.

Start with a pilot across the browsers and sites people actually use. Check which blocker is supported on each browser, how it can be managed centrally, and whether an allowlist can be maintained when a legitimate site breaks. Also decide who can approve an exception and how users report a problem.

u.368!marbleclip:

Would you let users turn it off when a site breaks?

9m!plumferrule_752:

That depends on the risk and support workload. A managed site exception gives you more control, while a user toggle may resolve problems faster but makes enforcement less predictable.

Reply to this answer
_k71~clampstencil.2

Don't skip the extension risk assessment. A blocker with broad access to webpages may be able to see sensitive page content, so review its permissions, publisher, maintenance, update process, and any history of security issues or ownership changes.

For a regulated organization, involve whoever handles security and compliance before deployment. Whether an extension is acceptable depends on the applicable requirements and the product, not on a blanket rule that all blockers pass or fail an audit.

Reply to this answer
5p~funnelkite_384

Network filtering is another option, particularly for devices where browser extensions are awkward to manage. DNS or proxy controls can block known advertising destinations without adding another extension to each browser.

They don't do exactly the same job, though. DNS filtering can't selectively block an ad served from the same domain as content you need. Browser-level tools can act on page content, so using both may provide broader coverage if the added management and extension risk are acceptable.

Reply to this answer
7w!plaidspindle_419

Make this part of the wider extension policy rather than just pushing one add-on. Specify which browsers are supported, restrict installation to approved extensions, and review those approvals over time. Browser extension capabilities differ, so check the actual product and version on each browser instead of assuming they all behave alike.

Reply to this answer
3h!gizmofern_462

For leadership, keep the pitch practical: fewer opportunities for malicious ads, possible disruption to legitimate sites, and a new software component that needs review and maintenance. Ask for a pilot and a decision on who owns exceptions. If legality is a concern, have legal or compliance review the proposed policy rather than promising there are no issues.

Talk to marketing too. Blocking ads can affect how they test campaigns and view websites, so they may need a controlled exception or a separate testing setup.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions