What Palo Alto Networks Browser Isolation Actually Does
Palo Alto Networks sells browser isolation in two shapes: Remote Browser Isolation inside Prisma Access, which renders pages in an air-gapped cloud container so malicious content never executes on the endpoint, and Prisma Browser, a secure browser for managed devices. For browser isolation Palo Alto buyers, three things decide whether it works: the license you hold, the connection method and decryption in front of it, and the documented limits users will hit.
📌 TL;DR Executive Summary
- Core Takeaway: Palo Alto RBI runs the page in an air-gapped container inside Prisma Access and streams the rendered result back. It requires Prisma Access 5.0 Innovation with Mobile User or Remote Networks, plus a separate RBI license.
- Key Risk/Challenge: Isolation depends on SSL decryption, and the release notes list real gaps — 32-bit browsers, read-aloud accessibility, page-touching extensions and sites that cannot be decrypted.
- Recommended Solution: Confirm license, connection method and decryption before you build an isolation profile. If you only need separate sessions for accounts you are authorised to manage, a browser profile manager is the lighter tool.
Browser Isolation in Palo Alto Networks: The Definition
Remote browser isolation moves rendering off the endpoint. Your laptop stops executing the page’s JavaScript; a container in the cloud does that work, and the local browser receives only the rendered result while clicks and keystrokes travel back. If the page carries an exploit, it detonates against the container instead of your device.
Palo Alto Networks ships this as Remote Browser Isolation inside Prisma Access, its SASE platform. The RBI administration documentation is specific about the session: it runs in a protected air-gapped environment that still supports JavaScript, HTML5, video and audio, and the URL in the address bar stays the original one. Users keep working in something that looks like a normal tab, which is what makes adoption survivable.
Scope matters before you shortlist anything. Browser isolation Palo Alto style starts with Prisma Access, not with a per-seat browser licence, so the pilot and the budget both follow your existing SASE footprint rather than a standalone purchase.
RBI, Prisma Browser and Prisma Browser for Business are three different products
Mix them up and you get the licensing answer wrong. Keep them apart:
- Prisma Access RBI is a service. Traffic passing through Prisma Access is matched by policy, and matching requests are isolated; isolation profiles control which browser actions the session may perform.
- Prisma Browser is a browser product for managed devices. Palo Alto unveiled an evolution of it on 23 March 2026, marketed as a secure browser built for the Agentic AI era, and launch coverage describes pages executing in an isolated cloud container.
- Prisma Browser for Business is the SMB edition announced the same day, 23 March 2026, with per-user monthly or annual billing, a free 14-day trial, and prepackaged use cases: finance and banking apps, healthcare records and HIPAA workflows, developer source code and Gen AI tools, and legal matter data.
So when a page implies browser isolation comes bundled with Prisma Access, check which of the three it means. For RBI specifically, it does not.
How Palo Alto RBI Works Under the Hood
Every remote browser isolation product answers one question: how much of the page is rebuilt on the server, and how much is sent to the client? Palo Alto’s own explainer sets out three classic approaches and their trade-offs.
| Rendering approach | How it works | Strength | Weakness |
|---|---|---|---|
| Pixel pushing | The server renders the page and streams it to the client as images | Strong containment — only pixels reach the endpoint | High bandwidth, heavy on content-rich pages |
| DOM reconstruction | The server rebuilds the page structure and the local browser re-renders it | Faster and lighter than pixel pushing | A malicious file can pass through to the endpoint |
| SKIA | The third method in Palo Alto’s comparison | Not detailed in that comparison | Palo Alto’s explainer notes it lacks versatility |
Production deployments rarely settle on a single method, so what you plan around is the traffic path, which is documented and predictable.
The request path, step by step
- The device reaches Prisma Access through GlobalProtect, Explicit Proxy or Remote Networks.
- SSL decryption makes the HTTPS request readable, so policy acts on the real URL and content type rather than a hostname.
- A security policy rule decides whether that request is isolated, allowed or blocked.
- The isolation profile attached to the rule sets permitted browser actions such as downloads and clipboard use, the visual theme, and which site categories are isolated.
- The page loads inside the air-gapped container, and its cookies and user data stay in that session rather than on the device.
- The rendered result streams back. Managed users who arrived through one of the three connection methods browse in isolation with no extra authentication step.
Because RBI is native to Prisma Access, your existing security profiles apply to isolated traffic instead of being rebuilt, and deployment health, usage and license information stay visible in Strata Cloud Manager or Panorama.
In practice, browser isolation Palo Alto rollouts stand or fall on steps two and three rather than on the rendering method. If decryption and the policy rule are wrong, the container never sees the request.
Running the browser somewhere other than the desk is the same architectural choice behind a cloud browser with UI mode, where the design question is how much of the live session a person can actually see and steer.
Who Feels Browser Isolation Most: Users, Tickets and Budget
Palo Alto cites that 74% of data breaches involve the human element. Isolation is the control that assumes a click will eventually land on something hostile and removes the consequence: isolated sessions, cookies and user data, safe PDF previews inside the session, and credential-phishing protection achieved by disabling the keyboard in an isolation profile so a fake login page never receives typed characters.
The people affected are not only the security architects writing the policy. Four groups feel the change first:
- Finance and banking users, whose apps are the high-value targets isolation exists for.
- Healthcare teams inside HIPAA-bound record systems, where a malicious redirect becomes a reportable event.
- Developers pulling source code and working with Gen AI tools, where copy, paste and download behaviour is the job.
- Legal teams handling matter data that must not leak through a clipboard.
The costs you should budget for
Palo Alto’s explainer is candid about the downsides: latency on content-rich pages, rendering failures on complex sites, and substantial bandwidth demand. The release notes sharpen the picture. 32-bit browsers are unsupported. Accessibility functions such as read-aloud do not work in an isolated session. Extensions that interact with page content — ad blockers are the named example — are ignored, while extensions that never touch the page still run.
None of that is a reason to skip isolation. It is a reason to pilot with a defined group before you redirect an entire workforce through a container and then explain the helpdesk queue.
RBI vs Prisma Browser: What You Are Actually Buying
Buyers conflate these because the marketing pages sit under the same SASE navigation. The commercial shapes differ, and so does the deployment model.
| Prisma Access RBI | Prisma Browser (enterprise) | Prisma Browser for Business | |
|---|---|---|---|
| What it is | An isolation service inside Prisma Access SASE | A secure enterprise browser for managed devices | An SMB-focused secure browser |
| Where pages run | Air-gapped container in the Prisma Access cloud | Isolated cloud container, per launch coverage | Not specified on the product page |
| Licensing | Prisma Access 5.0 Innovation with Mobile User or Remote Networks, plus a separate RBI license | Enterprise agreements; no public list price | Per-user monthly or annual billing |
| Trial | Not published | Not published | Free 14-day trial, per the product page |
| Best fit | Organisations already routing traffic through Prisma Access | Large estates standardising on one managed browser | Small teams handling finance, healthcare, developer or legal data |
One practical consequence: RBI only applies to you if you already run Prisma Access at the required version with a Mobile User or Remote Networks subscription. Prisma Browser for Business is the only one of the three with published per-user pricing and a free trial.
Cost is the other open question. Palo Alto does not publish list prices for Prisma Access, RBI or GlobalProtect; all three are quote-only, and browser isolation Palo Alto quotes land on the same commercial path. A third-party estimate puts full Prisma Access total cost of ownership at roughly $15–$30 per user per month with advanced security modules — a planning figure from an outside analyst, not a quote. The same source lists GlobalProtect at 4.4 out of 5 from 73 G2 reviews as of October 2026, which tells you about user sentiment, not about your bill.
If part of your case for isolation is that endpoints leak more identity than they should, it helps to know what your browser already exposes. A two-minute test answers whether your fingerprint is unique before you buy another control layer.
The RBI Setup Checklist: License, Connection, Decryption, Profile
Palo Alto publishes a cheat sheet for RBI for a reason: teams get the order wrong. The browser isolation Palo Alto sequence is fixed, and skipping a step leaves you with policy that looks correct and sessions that never isolate. Work through these steps in order.
- Confirm the license covers RBI. Prisma Access must be on version 5.0 Innovation with a Mobile User or Remote Networks subscription, and the separate RBI license must be present.
- Configure at least one connection method. GlobalProtect, Explicit Proxy or Remote Networks. Without one of the three, no user traffic reaches the isolation engine.
- Enable SSL decryption. Isolation decisions need to see inside TLS. Skip it and policy can only act on what little remains visible.
- Build the isolation profile. Set the theme, decide which browser actions are permitted during isolated sessions, and choose the site categories to isolate.
- Attach the profile to policy. Apply existing security profiles to the same traffic rather than duplicating them.
- Pilot one category with one group. Two weeks surfaces the latency complaints, the rendering failures and the sites that break.
- Monitor in Strata Cloud Manager or Panorama. Check deployment health, usage, license consumption and per-user troubleshooting from the console you already run.
Common Mistakes and Documented Limitations
Most failed rollouts trace back to a short list of avoidable errors, and browser isolation Palo Alto deployments are no exception. These are the ones the documentation keeps surfacing.
- Isolating before decryption is verified. Policy looks correct and the sessions simply never isolate.
- Forgetting allow rules for subresources. Documented behaviour: non-isolated pages can fail to load when their subresources match an isolation rule unless those URLs are allowed in the URL access profile. The page is fine; the third-party script inside it is not.
- Expecting ad blockers to work. Local extensions that interact with a page are ignored in isolated sessions. Say so before users discover it themselves.
- Rolling out to 32-bit browsers. Unsupported, with no workaround short of upgrading the endpoint.
- Assuming accessibility carries over. Read-aloud and similar browser accessibility functions do not work in isolation.
- Reading download progress literally. When the Content-Length header is missing from the request or response, the reported percentage is wrong. The file still arrives; the bar lies.
- Isolating everything at once. Content-rich sites render slowly, complex sites break, bandwidth climbs.
- Treating RBI as a patch substitute. Ransomware crews were still targeting a months-old high-severity Palo Alto VPN vulnerability in October 2026, five months after a patch shipped. Isolation protects the browser session, not an unpatched edge appliance.
Run Browser Isolation Palo Alto in the Cloud With Send.win
Send.win’s cloud browser runs isolated browser profiles on a server in the EU — open a clean session from any device without installing anything:
- Instant cloud sessions – launch an isolated browser in seconds, no local install
- Isolated profiles – separate cookies, storage and fingerprint settings per session
- Cloud sync & profile sharing – pick up the same profiles on the desktop app (Windows, macOS, Linux) or share them with your team
- Residential proxies included – on Pro and Team, with timezone and locale matched to the proxy
You can try it right now: the Send.win demo browser opens an isolated cloud session directly in this browser tab. Paid plans start at $19/month, with a 7-day money-back guarantee on your first card purchase — see pricing.
One more that rarely makes a checklist: inspection depends on seeing traffic clearly, and unusual egress paths change what your policy can evaluate — the same mechanics behind how sites flag a proxy IP apply to any traffic that leaves through an unexpected route.
When Full SASE Isolation Is More Than You Need
RBI answers one question: can this web page be trusted to touch this device? Plenty of teams carry a different question — which of several authorised accounts is this tab signed into, and can a colleague pick it up tomorrow? A container per page does not answer that one.
That gap is where a browser profile manager fits. Send.win gives each profile its own cookies, storage, sessions, fingerprint settings and proxy, so an agency running client ad accounts, a seller with several storefronts, a support team testing as different users or a QA group reproducing a region-specific bug can keep those sessions apart on one machine.
The two delivery models matter here. The Sendwin Browser desktop app installs locally on Windows 10/11 (64-bit), macOS 12+ and Linux, built on Chromium. The cloud browser runs profiles on Send.win’s server in Helsinki, Finland, from any device with nothing to install: a three-minute preview needs no signup, and a free account gets 10 minutes a day. Per-profile fingerprint protection covers canvas, WebGL, audio, fonts and hardware inside the browser engine, so profiles do not share one browser identity. Residential proxies are included on Pro and Team with metered bandwidth, bring-your-own HTTP/SOCKS5 works, timezone, locale, WebRTC and geolocation follow the proxy’s exit IP, and up to 50 profiles can be open at once on either plan.
Two boundaries are worth stating plainly. Send.win does not contain a zero-day exploit — that is isolation’s job. And it has no API, SDK, headless mode or automation interface, so nothing about it is scriptable. It is licensed only for accounts you own or are authorised to manage; where a platform restricts multiple accounts, use its official route, such as Amazon’s approval process for an additional seller account or Business Manager roles for agencies on Meta.
| Your requirement | Right control |
|---|---|
| Untrusted web content must not execute on the endpoint | Remote browser isolation (Prisma Access RBI) |
| Several authorised accounts need separate sessions on shared machines | Browser profile manager (Send.win) |
| A teammate must pick up an already signed-in client profile | Shared profiles with paid seats (Send.win) |
| Every user must leave through one inspected egress | SASE with SSL decryption (Prisma Access) |
Teams comparing both tend to score them on the same criteria, which is why a rundown of enterprise browser fingerprinting solutions is a useful companion to any SASE shortlist.
🏆 Send.win Verdict
Palo Alto RBI and Send.win sit at different layers, and confusing them wastes money. RBI stops hostile web content from reaching a trusted device; it needs Prisma Access, decryption and a separate license. Send.win lets a person or team run several separate browser identities for accounts they are authorised to manage — own cookies, own storage, own fingerprint settings, own proxy, shareable with paid teammates. If your problem is malicious pages, buy isolation. If your problem is twenty client logins across four laptops, buy profile separation.
See Send.win plans — Pro at $19/mo or $83.88/yr ($6.99/mo) with 150 profiles and 5 GB of proxy bandwidth, Team at $49/mo or $251.88/yr ($20.99/mo) with 500 profiles and 16 seats, or start with the free cloud demo.
Frequently Asked Questions
What is browser isolation in Palo Alto Networks?
It is a control inside Prisma Access called Remote Browser Isolation. Pages load in an air-gapped cloud container and the user’s browser receives the rendered result, so JavaScript and any exploit inside it run away from the endpoint. Sessions keep their own cookies and user data, and the original URL stays in the address bar.
Does Palo Alto RBI require a separate license?
Yes. You need Prisma Access 5.0 Innovation with a Mobile User or Remote Networks subscription, plus a separate RBI license on top. Deployment health, usage and license consumption are monitored in Strata Cloud Manager or Panorama.
How does Palo Alto RBI differ from Prisma Browser?
RBI is a service that isolates traffic flowing through Prisma Access, triggered by policy after decryption. Prisma Browser is a browser product for managed devices, and Prisma Browser for Business is its SMB edition, announced on 23 March 2026 with per-user billing and a 14-day trial. They solve adjacent problems with different contracts.
Which browsers and features does RBI not support?
32-bit browsers are unsupported. Accessibility functions such as read-aloud do not work in isolated sessions. Extensions that interact with page content — ad blockers, for example — are ignored, while extensions that never touch the page still run.
What is the correct setup order for Prisma Access RBI?
Confirm the RBI license and version requirement, configure at least one connection method (GlobalProtect, Explicit Proxy or Remote Networks), enable SSL decryption, then set the isolation theme, permitted browser actions and isolated site categories. Pilot a single category before widening the rule.
How much does Prisma Access cost?
Palo Alto does not publish list prices for Prisma Access, RBI or GlobalProtect; all are quote-based. A third-party estimate puts full Prisma Access total cost of ownership at roughly $15–$30 per user per month with advanced security modules, which is a planning figure rather than a quote.
How does browser isolation affect performance?
Palo Alto notes latency on content-rich pages, rendering failures on complex sites and substantial bandwidth demand. Impact depends on the rendering approach and on how much traffic you isolate, so isolating narrow categories keeps the experience workable.
What are the alternatives for small teams?
Small teams that need separate sessions for accounts they own or are authorised to manage usually do not need per-page containment. A browser profile manager such as Send.win gives each profile its own cookies, storage, fingerprint settings and proxy, on desktop or in the cloud, from $19/mo. Teams that must stop malicious web content from reaching the endpoint still need an isolation or SASE control.