Short answer
Remote browser isolation (RBI) opens risky or uncategorised websites in an isolated session away from the user's device, so potentially malicious code never runs on the endpoint. Users can still view the content, which means security teams can reduce risk without blocking large categories of websites outright.
In detail
Why organisations use RBI:
- It closes the gap between allowing and blocking: risky or uncategorised sites can be viewed safely instead of being blocked
- It reduces over-blocking and the user frustration that comes with it
- It adds protection for high-risk users, such as executives, who are frequent targets
In Netskope, RBI is part of the same platform as the secure web gateway, CASB and DLP, so isolation policies use the same console and policy engine. FirstNet tunes RBI triggers after go-live, alongside DLP policies and SaaS findings, so isolation applies where it adds protection without getting in the way of everyday work.
Customers often add RBI after a secure web gateway refresh. FirstNet also delivers Cloudflare Browser Isolation, which renders risky sites remotely and sends only pixels to the device.
Source: FirstNet Secure Access & SSE service page →
Didn’t answer your question?