A browser can be the front door to a finance portal, customer records, webmail and cloud applications. All on the same device. Yet while many UK SMEs have processes for approving business software, browser extensions can slip through with little oversight.
The issue is not that every extension is dangerous. It is that each one is software, with its own publisher, permissions and update path. A free add-on installed to make one task easier may have far broader access than the task requires, and the organisation may not know it is there.
For a consultancy-first business, this is an endpoint governance question, not simply a browser setting. The Fractal IT Director approach starts with the business risk and decides what controls, ownership and oversight are needed. Technical services should then support that strategy.
Why an extension can see more than expected
Extensions can add useful functions, from accessibility tools to workflow helpers. But depending on the browser and the extension, installation may request permissions to read or change data on websites, access downloads or use clipboard information.
That matters when staff are signed in to business services. Information entered into a finance portal, CRM or webmail may be sensitive. A permission to access website data can be much broader than “help me complete this one task”. The exact scope depends on the extension and its configuration, so permissions should be understood before approval, not accepted on autopilot.
The NCSC’s guidance on managing web browser security makes the central point: extensions can read or change data on websites a user visits, potentially including sensitive or personal data. They also increase the browser’s potential attack surface.

Approval is not a lifetime guarantee
An extension that was appropriate when installed may not remain appropriate indefinitely. Its publisher could change, its permissions could expand, or an update could alter how it works. Browser extension stores have also hosted malicious or hijacked extensions; a previously trusted add-on is not automatically safe just because it came from a recognised store or worked as expected last year.
This does not mean every update is suspicious. It means approval needs to be maintained. A useful control is to review significant changes (particularly new permissions, a publisher change or a change in the extension’s purpose) rather than treating the original approval as permanent.
The practical question is not simply, “Was this extension safe when someone installed it?” It is: “Is it still necessary, proportionate and supported for the way we use it now?”
How unmanaged extensions accumulate
On a shared or long-used machine, extensions can build up one small convenience at a time. A user might try an add-on for a particular project, forget about it, then move on. The extension remains in the browser, potentially with access it no longer needs.
Browser profiles add another dimension. When a user signs in to a browser with a personal account and synchronisation is enabled, settings and extensions may follow that profile to other devices. Depending on the browser’s configuration, saved passwords and other browser data may also synchronise. That can blur the boundary between a managed work device and a personal account.
These are easy gaps to miss because the browser still appears to work normally. A tidy desktop and a functioning antivirus tool do not tell you which extensions are installed, what permissions they have or where the user’s browser profile is syncing.

A practical policy for UK SMEs
A proportionate policy does not need to ban every extension. It needs to make installation deliberate and manageable.
Start with a browser and extension inventory. Record the browsers in use and identify installed extensions on business devices. For approved extensions, note the business purpose, publisher, extension identifier, permissions, owner and review date. The aim is a working record, not a spreadsheet that nobody maintains.
Choose a default. For many organisations, a managed allow-list is a sensible starting point: only approved extensions can be installed, with exceptions reviewed through a clear process. Where that level of control is not practical, define which users can install extensions and how they request approval. Blocking access to an extension store alone may not prevent every installation route, so test the controls on the browsers and devices actually in use.
Use browser management or MDM where available. Enterprise browser policies can help enforce which extensions are allowed or blocked. The NCSC recommends developing a policy for third-party extensions and using mobile device management where possible. Its guidance also recommends managing browser sign-in to cloud synchronisation accounts if work data syncing to personal accounts is a concern.
Review permissions and changes. Before approving an extension, check whether the requested access fits its business purpose. Review the approval if permissions, publisher or functionality change materially. Remove extensions that are no longer needed, and ensure updates are managed.
Tidy the endpoint as well. Browser governance is stronger when it sits within a standard device build. Remove unused software, limit local administrator rights and make sure devices have a consistent, supported configuration. That reduces the chance that a browser policy is the only carefully managed part of an otherwise unmanaged endpoint.

The Cyber Essentials connection
Cyber Essentials defines software broadly, including extensions. Its Requirements for IT Infrastructure require software in scope to be licensed and supported, with unsupported software removed or handled according to the scheme’s requirements. They also set security update requirements for applicable software.
That makes extensions relevant to endpoint hygiene and certification preparation. If an extension is installed on an in-scope device, it should not be overlooked simply because it lives inside a browser. A reliable inventory and approval process help an SME understand what is present and whether it remains supported and appropriate.
For businesses with specialist desktop access, including terminal-emulation access to IBM i estates, browser and endpoint decisions should also account for the systems and workflows staff rely on. Security controls should protect access without disrupting legitimate business operations.
Make browser control part of the IT strategy
The right policy depends on how your organisation works, which browsers it uses and what data staff access. David’s role as the expert IT Consultant is to set that strategic direction as a Fractal IT Director: define the acceptable risk, choose proportionate controls and establish how they will be reviewed. Execution then supports the strategy.
That execution may include Managed IT Services, Helpdesk Support and Network Solutions, alongside Cloud Solutions, Voice and Connectivity or Disaster Recovery where they fit the wider plan. These are supporting services, not substitutes for deciding what the business needs and why.
A useful first step is a short review: identify the browsers in use, find the extensions installed, check how profiles are managed and decide which add-ons genuinely support business work. The result is a clearer view of a small but often overlooked part of the endpoint, and fewer surprises hiding behind the browser toolbar.
For an overview of the Evestaff group’s services, visit evestaff.co.uk.
SEO keywords:
Cloud Solutions
Disaster Recovery
Dynamics 365 Jump Start
Helpdesk Support
IBM i Management
Managed IT Services
Network Solutions
Technology Expense Management
Voice and Connectivity
Join The Discussion