Cybersecurity

Browser extensions: how a handy add-on can read your company’s data

That screenshot tool or grammar checker may be able to read every page you open, including customer emails and HR records. Here is how to decide what to allow.

By the CNS team · · 6 min read

Illustration of a browser window with a warning icon, joined by a dashed line to a puzzle-piece extension

Key takeaways

  • An extension with the right permissions can read what you see after signing in, including webmail and customer systems.
  • Check the publisher, the permissions and what data the tool sends away before approving it for work.
  • Review what is already installed, remove what is not needed and restrict site access where the browser allows it.
  • Agree who staff ask when they want a new tool, and manage approved extensions in every browser your team uses.

You have found an extension that looks useful for work. Perhaps it captures a whole page in one screenshot, or checks an email before you send it. You are about to install it when the browser asks for permission to “read and change data on the websites you visit”.

If you also use that browser to read customer emails or open employee records, the extension’s access could include those pages. An extension that can read a page can read what you see after signing in.

What extensions can see

Extensions add features to browsers such as Chrome, Edge and Firefox. To do their job, some need permission to work with the sites you open. That access can be limited to particular sites or cover almost all of them. With the right permissions an extension can read and change page content, and Mozilla notes that this can include information you type into a page, such as usernames and passwords.

Website access does not by itself let an extension open files on your computer, and lots of extensions need access for a good reason. A password manager has to recognise sign-in pages to fill in your details, and some ad blockers inspect page content to hide ads. If the reason is not clear from the store listing, your IT provider can ask the developer before you approve the tool.

Who published it, and what do they do with your data

If you are adding an extension for software you already use, start from that software company’s own website and follow its link to the store listing. Then check the publisher’s name, so you do not pick a lookalike with a similar name or logo.

Stores run checks. Mozilla, for example, reviews submissions for common problems and may have a person look at them, but it says those checks do not guarantee an extension is safe.

Then think about the information. If a tool checks your email, you would expect it to read that email. You also want to know whether it sends a copy to its provider and what happens to the text. The privacy policy should say what the company collects, how it uses it and how long it keeps it. A useful question to put to a provider: “If our staff use this while replying to a customer, what information will your company receive?” If the answer is vague, do not use the tool on confidential emails until IT has checked it. You might be happy using one on public product descriptions and not on client correspondence.

What is already installed

An extension added for one project often stays in the browser long after the work ends. Ask your IT provider to list what is installed in each browser used for work, with the publisher and permissions, plus who uses each one and why.

Be careful with removal. If an employee says, “Customers send me files I cannot open, so I use this converter,” they need another way to open those files. Check whether approved software already does the job, or have IT review a replacement first. Mozilla suggests reviewing installed extensions regularly and removing the ones you do not use, but check unfamiliar names with IT, because an extension you do not recognise may be something they installed for security or another business reason.

Limit where an extension can read

Say you use an extension to check text on your company website. IT can test whether it still works when limited to that site, which keeps it off pages such as your accounting system. Chrome lets you choose when and where an extension can read and change site data. Depending on the extension, that can be “when you click it” or only on sites you name, instead of on all sites.

Have IT try the change with the staff who use those tools before rolling it out. Include everyday tasks such as signing in with the approved password manager, so you can see whether the restriction stops something people need. An extension that controls VPN or proxy settings needs its own network-access check, because Google notes that changing website permissions does not restrict that.

Decide what staff may install

On browsers your IT provider manages, Chrome and Microsoft Edge both support rules that allow approved extensions and block the rest. The rules must cover every browser your staff use for work: an Edge policy does not apply to Chrome.

Staff need to know who to ask. A simple route works: send the store link to a named person and say what job it is for. IT reviews the permissions and data collection, then says whether the tool is fine, or suggests an approved alternative. An extension needed by one department does not have to be installed for everyone.

Updates change permissions

An update can bring a feature that needs more access to your data. Chrome can disable an extension after an update that adds a permission that triggers a warning, and it stays off until the user accepts it. Before anyone accepts, IT should check what changed and whether the business needs it.

An extension can also change how it uses permissions you have already granted, without asking for anything new. That is why reviews should cover how a tool handles data as well as new permission prompts. Keep browsers and approved extensions updated, and include them in later reviews.

When the browser raises an alert

If your browser warns you about an extension, including a warning from Chrome’s Safety Check about a potentially harmful extension, send IT a screenshot and the extension’s name. If the browser has already blocked it, leave it blocked while IT checks. The store link and an approximate install date help.

Your provider can check what permissions the tool had, look for it on other work computers and assess what it could have accessed. Uninstalling does not take back information the extension has already sent elsewhere, so IT may need to secure accounts whose passwords were exposed. If customer or employee information was copied, you need to assess what was involved. In Cayman, a personal data breach has to be reported to the Ombudsman, and to the people affected, within five days. See our Data Protection Act checklist.

Common questions

Are all free browser extensions unsafe?

No. Free and paid extensions need the same checks on publisher, permissions and handling of data.

Can an extension read information behind a login?

Yes, if it has the necessary access to the page you open after signing in. That can include webmail or a customer system.

Why does our password manager need access to websites?

It needs to recognise sign-in pages and fill in your details. Make sure you have the password manager’s official extension, not another tool with a similar name.

Should we ban every browser extension?

Not necessarily. You can keep the tools your team needs and limit new installs to ones the business has approved.

How CNS can help

We can review the extensions installed across your team’s browsers, explain what access each one has and set up approved-extension rules in Chrome and Edge as part of managed IT. If you do not have an IT provider, book a free network assessment or call (345) 945-2755 and we will take a look.

Sources

Questions about your own setup?

Talk to a Cayman IT expert. No obligation, no jargon.

Get in touch (345) 945-2755