Spell-check for privacy
Blog
Safe AI adoption 8 min read

The browser became your biggest security blind spot

Almost all work now happens in the browser: AI tools, email, SaaS. That is where sensitive data leaves the organisation, not through your network or your files. But most security still watches logs, and by then the data is already gone.

Sensitive data leaves the organisation through the browser, not the network or files
Quick answer

Almost all work now happens in the browser: AI tools, email, SaaS. That is where sensitive data leaves the organisation, not through your network or your files. But most security still watches logs and network traffic, and by then the data is already gone. You get control by signalling in the browser, the moment someone pastes or types, before it is sent.

01

Around 85% of the workday is spent in the browser (Omdia, 2025)

02

77% of users paste data into GenAI tools, 82% of it via unmanaged accounts (LayerX)

03

GenAI is now the single largest channel for corporate-to-personal data leakage (LayerX)

04

Network DLP and logs miss a paste inside a browser tab, or see it only after the data is gone

05

Control happens in the browser, at the moment of typing, not afterwards in a log

The security team watches the dashboards. Network traffic, endpoint alerts, mail gateway, firewall: all green. No suspicious outbound connections, no blocked attachments. On paper, nothing is leaking.

Two floors up, an employee pastes a client file into ChatGPT, in a browser tab, on a personal account. Encrypted traffic to an ordinary website. No alert. No log that matters. The data is out the door, and the dashboards stayed green.

That is not a fault in your security. It is a blind spot in where you are looking.

You're watching the wrong place

Almost all work now happens in the browser: AI tools, email, CRM, documents, forms, ticketing. That is where sensitive data leaves the organisation. Not through your network, not through your file server, but through a text field in a tab. And that is precisely where most security does not look. Network DLP and logs do not see a copy-paste in a browser, or only once the data is long gone. You do not get control by logging better. You get it by being present the moment someone pastes or types.

Why the classic approach fails here

Classic data loss prevention was built for a world that is disappearing: files on a drive, email through a gateway, traffic over a network you control. DLP, proxies and endpoint tools are strong there.

But a prompt is not an attachment. A paste into a SaaS app is not a file transfer. It is encrypted traffic to an ordinary website, often through an account the organisation does not manage. Research by LayerX found that 82% of the data employees paste into GenAI tools goes through unmanaged accounts. That puts it outside the view of the tools you probably already have.

And even what you do log, you log after the fact. A log is a record of what already happened. By the time the line appears, the data has left. You can reconstruct an incident with it, but you cannot prevent one.

What is actually happening

The numbers show how far the centre of gravity has moved.

Omdia's State of Workforce Security found that around 85% of the workday is spent in the browser, in SaaS and web apps. The browser is no longer a window onto work. It is the workplace.

And that is where it goes wrong. LayerX found that 77% of users paste data into GenAI tools, and that GenAI is now the single largest channel through which corporate data leaks from a work environment into a personal one. Copy-paste, the most ordinary action there is, has become the biggest blind spot. Not through a sophisticated attack, but through Ctrl+C and Ctrl+V in a tab.

This is the pattern we see across the series: the risk appears at the human, at the moment of action, in the browser. And it is exactly where most organisations have no visibility.

The objection, taken seriously

The fair objection: "We have DLP, a CASB and a proxy. We do see what happens."

For some of it, true. For managed flows, known apps and corporate accounts, those tools do good work, and they remain necessary. This is not an argument against your existing stack.

But the most dangerous behaviour falls outside that stack: a paste into a free AI tool, on a personal account, in a browser. No data processing agreement, often no corporate identity. Your CASB sees the approved app, not the shadow tab next to it. And what your proxy logs, it logs after the event. The question is not whether you have tools, but whether they look where the work, and the leak, actually happen today.

What to do instead

Four shifts that bring visibility back to where the work is.

  1. Put detection in the browser. Where typing and pasting happen, not in a network layer that only sees the traffic pass by encrypted.
  2. Signal before send. Help the employee at the moment of action, so the leak never forms, instead of finding it later in a log.
  3. Cover the whole browser, not one app. AI, email, SaaS and forms: the risk is anywhere a text field sends data out.
  4. Measure in aggregate. Which data types, which tools, and whether the line falls after you change something, without tracking individuals.

That last shift turns a blind spot into a measurable picture. This is what that looks like:

Detections over timeLast 30 days
12,438+18% vs last month
Top sources
ChatGPT
8,124
Gmail
3,210
Gemini
812
BeeSensible dashboard: aggregated detections and top sources, without monitoring individuals.

Not loose log lines to pick through afterwards, but a trend: where does the risk appear, in which channels, and is what you changed working?

Where BeeSensible fits

You can bring visibility back to exactly where the work happens: the browser. BeeSensible runs as a browser extension and recognises sensitive information as someone types or pastes, across AI tools, email and other web apps. Through the desktop app, detection runs entirely on the device; for browser-only use it runs in working memory on a BeeSensible EU server. Either way the text is discarded after analysis and nothing is stored. What is in there, a name paired with an account number, an IBAN, a national ID, is marked before it is sent. The employee decides.

Here is what that looks like the moment someone pastes into a browser tab:

Outlook
New message
Todr.smith@clinic.co.uk
SubjectClient file: Jane Richards
Dear colleague, please find the file for client Jane Richards (BSN: 384920173). She can be reached at 06-12345678. See the attachment for the full care plan.
BeeSensible highlights sensitive details before send.

Your security is not weak because the dashboards are green. It is just watching a world that has shifted. The work moved into the browser, and the risk moved with it. To get control there, you have to stop waiting for the log line and be present at the moment of the paste. Not to block traffic, but to make what happens in a tab visible before it leaves the organisation. The blind spot does not disappear by looking harder at the network. It disappears by looking where people work.

FAQ

Common questions

Why is the browser a security blind spot?

Because almost all work happens there, while traditional security watches other places. Network DLP and endpoint tools are built for files and email gateways, not for a copy-paste in a browser tab into an AI tool or SaaS app. That happens over encrypted traffic and often through an unmanaged account, beyond their view.

Don't our DLP and logs see what employees paste into AI tools?

Usually not, or only afterwards. Research by LayerX shows 82% of data pasted into GenAI tools goes through unmanaged accounts, outside any corporate oversight. And even when something lands in a log, the data has already been sent. A log is a record of what happened, not a moment to intervene.

Isn't a browser extension too limited for serious security?

The browser is exactly where modern data sharing happens: AI, email, CRM, documents, forms. About 85% of the workday is spent there. Security that works in the browser sits precisely where the risk appears, before send rather than after.

What's the difference from monitoring logs afterwards?

Logs tell you what went wrong yesterday. Signalling in the browser tells the employee what is sensitive now, before it is sent, so the incident never forms. The difference is steering in advance versus cleaning up afterwards.

How does this help with GDPR?

Under GDPR you must report a breach within 72 hours and demonstrate appropriate measures. A leak you only find in the logs is already a breach. Signalling in the browser prevents the data from leaving at all, and produces aggregated proof that you have control.

See how BeeSensible works

Detect sensitive data before it leaves your team, in any app, in real time.