Browser Request Isolation
RBI evaluates each request to determine whether to isolate or
bypass it based on whether the request originates from a browser and whether it is a
top-level page or a sub-resource.
| Where Can I Use
This? | What Do I Need? |
|---|
|
|
Prisma Access
license with
the Mobile User, Remote Networks, or Explicit Proxy
license subscription
|
In a full isolation deployment, websites commonly load content from multiple
subdomains. Previously, you had to add each subdomain separately to the bypass list.
Remote Browser Isolation (RBI) reduces this overhead by automatically determining
whether a request originates from a browser and whether it is a top-level page or a
sub-resource, then applying the appropriate isolation or bypass action without
additional configuration.
RBI applies the following behavior based on the request origin
and type:
Browser request, top-level page—A top-level page request occurs when a
user navigates directly to a URL in a browser, such as by entering a URL in
the address bar or clicking a link. If the URL filtering action is
isolate, RBI isolates the page and
its sub-resources.
Browser request, sub-resource—RBI automatically
bypasses isolation for same-domain sub-resources that a browser loads as
part of rendering a top-level page, such as images, scripts, and
stylesheets. This is irrespective of the URL filtering action configured for
the sub-resources. Sub-resources served from a different domain, such as
those from a third-party content delivery network, are not automatically
bypassed and require explicit bypass rules.
Non-browser request—Requests originating from applications or
non-browser clients are not isolated even if the URL filtering action is set
to isolate.
