BrowserBox vs Citrix Remote Browser Isolation

BrowserBox has no write-up on Specifiction yet; its figures are above.

Citrix Remote Browser Isolation separates web browsing from a user’s device to protect corporate networks from browser-based attacks and provide access to internet-hosted web applications. Users open web apps in a configured browser, while browsing data does not transfer directly between the website and the device. Published browsers support shared-passcode, authenticated, and unauthenticated external web apps. Administrators can set URL allow lists, control clipboard use, printing, kiosk mode, region failover, and client drive mapping, then monitor or disconnect active sessions. Optional activity logging records visited host names, access times, user identifiers, and allowlist status in the customer’s Azure Storage Account; uploads occur hourly rather than in real time. Cloud browsers run on VDAs, with Citrix Cloud managing security and patching. Session history and HTTP-request cache are deleted when sessions end, according to Citrix. Access requires an HTML5-compatible browser, with no downloadable client. Traffic uses TLS 1.2 only. Self-hosted workloads require a customer Azure subscription and specified Citrix and DaaS entitlements.