FROST: how a regular website can use your SSD as a side channel to infer activity

The simplest mental model is this: the attacker’s website does not ask “which website is open?”. Instead, it repeatedly asks the SSD a tiny question: “how fast are you responding right now?”.

In media coverage, 89% can quickly become a fear headline. For a technical assessment, the important parts are the metric, the scenario, and the limits of the experiment.

Closed-world means the model chooses from a known set of classes. If the test contains the top 50 websites, the prediction is roughly asking: “which of these 50 profiles does this trace look most like?”. On the open internet, the number of candidates, background activity, SSD model, operating system, browser, extensions, power mode, and user behavior all add noise.

That does not make the result weak. Quite the opposite: the impressive part of FROST is that it brings an SSD side channel into the browser without installing native malware. But a responsible reading of the paper should explain the threat model instead of selling a panic headline.

Understanding the threat correctly helps avoid two opposite mistakes: dismissing the research too quickly, or describing it as science-fiction spyware.

A cookie blocker works against storage-based tracking, where a site directly stores or reads an identifier. Incognito mode reduces persistence between sessions. FROST belongs to a different class: the site measures the behavior of a hardware resource during the current session.

Think of it as the difference between “someone wrote your number in a notebook” and “someone is listening to noise through a wall to infer what is happening”. In the second case, deleting the notebook does not remove the sensor.

That is why privacy engineering for the modern web must include more than consent and storage policy. It also needs side-channel thinking: timers, shared resources, storage pressure, cache behavior, the rendering pipeline, GPU/CPU/SSD contention, and cross-origin isolation.

For everyday users, FROST is currently a research-grade threat rather than a mass exploit kit. But for browser platforms and products that make privacy claims, it is already a practical signal.

Even if FROST never becomes a mass attack in this exact form, it clearly shows where the modern web risk surface is heading.

For landing pages and content-heavy websites, we keep the code static-first by default: less client runtime, fewer third-party scripts, and less unnecessary local storage. That does not make a website “immune to side channels”, but it removes many unnecessary moving parts that often appear without a real business reason.

For SaaS products and internal dashboards, the approach is different: storage APIs, auth flows, analytics, session handling, embedded widgets, and permissions need a dedicated security review. That is especially important for products handling financial, medical, legal, or corporate data.

The main claims about FROST in this article come from the authors’ primary source paper. OPFS documentation is used to explain the API, not to evaluate the attack results.