Remote Browser Isolation Limitations
Focus
Focus
Remote Browser Isolation

Remote Browser Isolation Limitations

Table of Contents

Remote Browser Isolation Limitations

Review the known limitations for Remote Browser Isolation.
Where Can I Use This?What Do I Need?
  • Prisma Access (Managed by Strata Cloud Manager)
  • Prisma Access (Managed by Panorama)
Remote Browser Isolation (RBI) has the following limitations.
Issue IDDescription
PANG-273156
On Prisma Access 5.2.1 Innovation (dataplane 11.2.4), if you select Action for sites that cannot be decrypted (technical or policy reason)Block for RBI and select DeviceSSL Decryption SettingsSend handshake messages to CTD for inspection in Panorama, isolated browsing won't work correctly.
Workaround: Set Action for sites that cannot be decrypted (technical or policy reason) to Allow.
ARBI-5433
RBI supports only 64-bit web browsers. 32-bit web browsers are not supported.
ARBI-5427
Accessibility functions provided by web browsers, such as the read aloud function, are not supported in RBI.
ARBI-3372
When navigating to a nonisolated URL, the webpage won't load correctly if the subresources on the webpage match a security rule with isolation. As a workaround, you need to configure your security rules to allow subresource URLs. To do this, update your URL access Management Profile to set the site access for the subresource URL to Allow.
DOCS-4303
Depending on their implementation, some browser extensions on an end user's local browser that interact with a loaded page will be ignored (won't take effect) during remote isolated browsing. For example, ad blockers installed on a local browser don't take effect during local browsing. Extensions that don't interact with a webpage will still work in isolated browsing.
ARBI-4139
While downloading content during isolated browsing, if RBI does not receive the Content-Length header in an HTTP request or response, the download percentages won’t display accurately.