compromised originvictim originprobeprocess wall
Couldn't start the 3D scene.

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

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.

Made with ๐ŸŸ  Blender ยท Three.js