Home▸Cybersecurity▸Browser Site Isolation: Process-per-Origin vs Cross-Origin Probe

Browser Site Isolation: Process-per-Origin vs Cross-Origin Probe

Open several origins in one browser and send a Spectre-style timing probe from a compromised tab at a bank tab's secret. Switch Site Isolation on and off to compare the exact chance of reading the secret, the attempts needed, the bytes exposed and the memory cost of one process per origin. Process frames, tabs and padlock modelled in Blender, with numerical checks built in.

Cybersecurity3DModerate60 FPS📱 Mobile-adapted🟠 Blender⇄ 2D version
Browser Site Isolation: Process-per-Origin vs Cross-Origin Probe ↗ Open standalone

Modern browsers run each open tab's page as untrusted code, so the question that decides whether a bug or timing side channel can steal your data is architectural, not just about patching: does the malicious page's renderer share memory with the page that holds your session cookie? This simulator renders each open origin as a process box in 3D. With Site Isolation off, every origin is packed into one shared process, so a probe fired from the malicious tab can walk across memory and read another origin's data. Switch Site Isolation on and each origin gets its own process — the same probe hits a hard process boundary and returns nothing. Adjust the number of open origins and the attack's strength, then launch probes and watch the leaked-bytes and blocked-probes counters to see exactly what process-per-origin sandboxing buys you.

⚙ Under the hood

Open several origins in one browser and send a Spectre-style timing probe from a compromised tab at a bank tab's secret. Switch Site Isolation on and off to compare the exact chance of reading the secret, the attempts needed, the bytes exposed and the memory cost of one process per origin. Process frames, tabs and padlock modelled in Blender, with numerical checks built in.

cybersecuritybrowser securitysite isolationsandboxingprocess isolationspectreweb securitySite IsolationBrowser SecuritySpectreProcess Sandboxing

3D · Three.js / WebGL renderer · 60 FPS target · runs fully client-side, no install

What did you find?

Add reproduction steps (optional)