For a SaaS-first company the browser is the operating system. A practical guide to session theft, infostealers, extensions, AI browser assistants, managed browser policies and when thin clients make sense.

Browser security is the set of controls that protect what happens inside the browser: the sessions it holds, the extensions it runs, the AI assistants that read page content, and the data users move between tabs. For a company whose systems all live in SaaS, it covers the same ground that endpoint security covered when work lived on the desktop.
Every few weeks we get a version of the same call. A 70-person SaaS company finds that someone logged into its cloud console from another country, with no failed password attempts and no MFA prompt. The password was never stolen. A contractor's personal laptop picked up infostealer malware from a cracked game download, the malware copied every cookie in the browser, and the attacker replayed a live session. The company had MFA everywhere. MFA had already been satisfied. (This is a composite of several engagements, not one client.)
When we first published this post in 2023, the question was whether the browser would replace the operating system. For the companies we work with, that is settled. Email, code, payroll, CRM and the cloud console all run in tabs.
On a traditional desktop, the security boundary was the device. In a SaaS-first company the valuable thing is not on the device at all. It is the session token in the browser's cookie store, which grants the same access as password plus MFA, often for days.
The latest data backs this up. The Verizon 2026 Data Breach Investigations Report found that vulnerability exploitation overtook stolen credentials as the top initial access vector for the first time, at 31%. The full report adds that credential abuse still appears somewhere in 39% of breaches, and that third parties are involved in 48%. The full DBIR also found that 67% of users access AI services on corporate devices with non-corporate accounts, which is almost always a browser tab.
IBM's 2026 Cost of a Data Breach study puts the global average breach at $4.99 million, a figure skewed by large enterprises.
MITRE tracks this as Steal Web Session Cookie (T1539). There are three routes we see in practice.
Commodity malware, usually delivered through fake downloads, cracked tools or malicious ads, copies saved passwords and session cookies from every browser profile on the machine. The logs are sold in bulk. Verizon notes that ransomware operators increasingly buy this harvested access rather than breaking in themselves. The infected device is rarely a managed laptop. It is a contractor's machine or a personal laptop someone used "just once" for work.
A phishing page proxies the real login page, the user completes MFA, and the attacker keeps the resulting session cookie. App-based push and SMS codes do not stop this. Phishing-resistant authentication does, because a passkey or security key will not sign a login for the wrong domain. CISA's fact sheet on phishing-resistant MFA is blunt: FIDO/WebAuthn is the only widely available phishing-resistant option. Our phishing scams guide covers the reporting habits that go with it.
An extension with permission to "read and change all your data on all websites" can lift cookies and page content from every tab. In late December 2024, attackers phished the developers of dozens of Chrome extensions, including one published by a security company, and pushed malicious updates through the official store. MITRE lists this under Browser Extensions (T1176.001).
One encouraging change: in April 2026 Chrome on Windows made Device Bound Session Credentials generally available, tying a session to a key that cannot leave the machine. It only protects sites that adopt it, so plan as if most of your stack has not.
This is the newest version of the extension problem. AI sidebars and summarizers read the full page you are on, including the customer record or the contract, and send it to a model. Agentic browsers go further: they click, fill forms and navigate while logged in as you.
Two risks follow. First, data leaves through a channel nobody approved, which is classic shadow AI. Second, the page can talk back. OWASP's LLM01:2025 Prompt Injection describes indirect prompt injection, where instructions hidden in a web page or file are obeyed by the model even though the human never sees them. An agent with your session and a poisoned page is an attacker with your session. IBM's 2026 study found 92% of organizations that had an AI-related breach lacked proper AI access controls.
Our position: allow AI assistants only through approved, company-account tools, and keep agentic browsing out of admin consoles and finance. Our guide to securing AI agents covers the permission model.
Vendors will tell you the answer is a new browser. Sometimes it is. Usually it is the browser you already run, with policies you have not switched on yet.
Option | What you get | What it costs you | Our opinion |
|---|---|---|---|
Unmanaged consumer browser | Defaults only; any extension, personal profiles synced | No license cost, high hidden risk | Not acceptable once you hold customer data or face a SOC 2 audit. |
Managed policies on your current browser | Extension allowlist, forced updates, blocked password saving, separated work profiles, sign-in restrictions, all pushed from your device management or identity console | Usually included in licenses you already pay for; a few days of setup | Do this first. It closes most of the gap for most companies under 200 people. |
Dedicated enterprise browser product | Data controls such as copy, paste, print and upload limits per app, session recording, access from unmanaged devices | Per-user subscription, another vendor in your supply chain, user friction | Worth it when contractors or BYOD users must reach sensitive data. Overkill if every user has a managed laptop. |
Remote browser isolation | Pages render remotely, so local malware never touches the session | Latency, cost, breaks some apps | Niche. Useful for high-risk roles, rarely company-wide. |
Thin client or virtual desktop | The whole workspace lives off the device | Highest cost and admin effort | Right for specific roles (see below), wrong as a blanket answer. |
None of these replaces identity controls. A locked-down browser still hands over a valid session if the user approves a push prompt on a phishing page.
Thin clients make sense when the device itself cannot be trusted. In our experience that means four situations: contractors who need production data; shared frontline workstations such as support centers; roles handling regulated data such as health records under HIPAA or sensitive information under Quebec Law 25; and short-term staff where shipping laptops is impractical.
They make less sense for engineers and anyone who needs local compute, and they do not remove the need for a managed endpoint underneath. Our endpoint security guide covers that layer.
It does not fix a SaaS app that is misconfigured, such as a public file share or an over-permissioned integration. That is a SaaS posture problem.
It does not stop exploitation of an internet-facing system, which is now the top initial access vector in the DBIR.
It does not protect a personal device you never manage. Either control the work browser profile on contractor machines or accept the risk in writing.
A company of ten people on managed laptops, using a single identity provider with passkeys, does not need an enterprise browser product. Turn on the policies and move on.
Move admins, finance and engineering to passkeys or security keys on your identity provider.
Shorten session lifetimes for admin consoles and require re-authentication for sensitive actions.
Inventory installed extensions across managed browsers and remove anything with all-sites access that nobody can justify.
Push browser policies from your device management or identity console: extension allowlist, forced updates, no saved passwords, work profile only for company accounts.
Publish a short approved list of AI assistants and block the rest by policy.
Decide in writing how contractors and BYOD users reach company data.
Run a tabletop on a stolen-session scenario using our incident response plan for small businesses, including how fast you can revoke every session for one user.
Map the policies to SOC 2 and ISO 27001 controls for your next audit.
Only now evaluate whether a dedicated enterprise browser or thin clients fill a remaining gap.
If you want a second pair of eyes, our Cybersecurity Baseline Assessment checks these controls against your actual stack. For ongoing ownership, a virtual CISO engagement starts from $2,000 a month; tiers are on our pricing page.
Technically no; it still runs on Windows, macOS, ChromeOS or Linux. Practically, it is where the work, the data and the sessions live, so it deserves the attention the operating system used to get.
Not by itself. Session theft happens after MFA is completed. Phishing-resistant MFA blocks the phishing route; short sessions and fast revocation limit the infostealer route.
It depends on what the attacker accessed. In Canada, PIPEDA requires reporting to the Office of the Privacy Commissioner when a breach creates a real risk of significant harm, and Quebec Law 25 has its own regime. In the US, every state has a breach notification law, and HIPAA applies if health data was exposed. Our data security and privacy team handles this assessment.
With the Canadian Centre for Cyber Security's web browser security overview: standardize on one browser, keep the number of extensions small, review permissions and avoid saving passwords in the browser. Then work through the 30-day list above, or book a call and we will walk through it with you.
Our diverse industry experience and expertise in AI, Cybersecurity & Information Risk Management, Data Governance, Privacy and Data Protection Regulatory Compliance is endorsed by leading educational and industry certifications for the quality, value and cost-effective products and services we deliver to our clients.