Does Chrome Enterprise Premium Cover Safari?

This question usually arrives after someone has already bought Chrome Enterprise Premium and is trying to work out what is left to solve. It deserves a straight answer, and it also deserves a fair one, because a good deal of the competitive material written about this product is wrong.

Does Chrome Enterprise Premium cover Safari?

No. Chrome Enterprise Premium governs Chrome, and its controls do not extend to Safari, Firefox, or any other browser. The boundary is the browser itself rather than a gap in the feature set, which is a different and more useful thing to understand.

Is Chrome Enterprise Premium actually any good?

Yes, and it is worth saying so plainly because several vendors imply otherwise. It lists at USD 6 per user per month (Source: Google, Chrome Enterprise Premium published pricing). That buys data loss prevention, the practice of detecting sensitive content before it leaves the organisation, along with malware and phishing protection and visibility into unsanctioned AI use.

The claim you will see in competitive decks is that Chrome Enterprise has no DLP and no AI governance. That is true of Chrome Enterprise Core, the free tier, and false of Premium. If a vendor puts that in front of you without drawing the distinction, treat the rest of their comparison table with the same caution.

So what is the real limitation?

The real limitation is reach, not capability. Chrome Enterprise Premium is enforced through Chrome policy on a managed device, so three populations sit outside it and each one is common.

• Staff using a different browser. Safari on a Mac fleet, Firefox in engineering teams, Edge where Windows defaults were never changed.
• Unmanaged devices. Contractors, agencies, partner staff and anyone working from a personal laptop. You cannot push Chrome policy to a device you do not enrol.
• Anything outside the browser. Desktop AI applications and AI enabled IDEs, the code editors developers work in, are not governed by a browser policy at all.

Can I just standardise everyone on Chrome?

You can try, and organisations do, but it converts a technical problem into a change management one. Safari is the default on every Mac and the browser most designers and executives already use. Forcing a migration to close a governance gap tends to produce a slow rollout and a population of exceptions that quietly becomes permanent.

There is also a category the migration does not fix. Contractors and partner staff work on their own devices under their own IT, so no browser standard of yours applies to them.

How do the other options compare?

Each of the main alternatives is stronger than its competitors admit, so here is the honest version.

• Microsoft Purview ships DLP browser extensions for Chrome and Firefox on Windows 10 and 11 (Source: Microsoft Learn, updated 15 June 2026). Purview Endpoint DLP does cover macOS without that extension, so the accurate limitation is narrower than usually claimed: three of the five site level actions are available in Edge only.
• CrowdStrike is not blind in the browser, whatever older comparisons say. Falcon AIDR reached general availability on 15 December 2025 with a browser collector extension for Chrome, Edge and Firefox that captures prompts and AI responses.
• Zscaler ships DLP inline, on the endpoint and across SaaS. Any table marking that cell empty is out of date.

The pattern worth noticing is that most of these products are good at what they observe. They differ in where they sit, and therefore in what they can see at all.

How do I work out whether the gap matters to my organisation?

Answer four questions before you look at another product. They take an afternoon and they usually settle the decision.

1. What proportion of your fleet is macOS, and what do those users actually browse in?
2. How many contractors, agency staff or partner users touch your systems on devices you do not manage?
3. Do your developers use AI inside their IDE, and is that inside or outside your current controls?
4. When staff use AI through a personal account rather than a corporate one, would anything you own today see it?

If the honest answers are "few", "none", "no" and "yes", Chrome Enterprise Premium is likely sufficient and you should spend the budget elsewhere. Most organisations we run this with do not get four such answers.

What covers the browsers Chrome policy cannot reach?

A control that installs into the browsers themselves rather than into one vendor's policy engine. Akamai Workforce Protector, formerly LayerX, is what we deploy for this: an extension covering Chrome, Edge, Firefox and Safari, with an optional endpoint agent when coverage needs to reach desktop AI applications and AI enabled IDEs.

Being precise about that split matters, because a security architect will test it. Browser coverage is agentless and installs through your existing device management with no proxy and no traffic redirection. Desktop applications and IDEs are not agentless and do require the endpoint agent. Any vendor claiming both at once has not thought about it hard enough.

It also handles the unmanaged device case differently, through read only sessions and watermarking for contractor and partner access, rather than requiring you to enrol a device you do not own.

How does David and Goliath help here?

We start by working out what your existing licences already cover, because organisations routinely buy a second product to solve something the first one does. If Chrome Enterprise Premium covers your fleet, we will tell you that and the engagement stops there.

Where a gap is real, we size it before recommending anything: which browsers your staff actually use, which populations sit outside managed device policy, and what is reaching AI tools through personal accounts today. That evidence is what makes the business case, and it is covered in how to find out what AI tools your staff are actually using.