Remote Browser Execution
Execute web content in a remote controlled environment rather than directly on the endpoint.
Remote Browser Execution • Threat Containment • Data Control
JupitoSecure Browser Isolation moves browser execution into a controlled remote environment so that higher-risk web workloads do not execute directly on the endpoint.
Normal browsing can remain in the Enterprise Browser. Higher-risk destinations can be moved into an isolated execution boundary according to risk.
Higher-risk web activity executes remotely while users receive a controlled browsing experience.
Modern organizations cannot treat every website as equally trusted. JupitoSecure Browser Isolation provides a separate execution boundary for websites, content and browsing activity that require stronger containment.
Managed browsing for normal enterprise web activity.
Remote execution for destinations and workflows requiring stronger containment.
Controlled workspace browsing for workloads requiring a stronger execution boundary.
Secure access to private resources without extending the browsing boundary.
Governed web-enabled AI workflows under enterprise policy.
The security boundary can be selected according to the risk of the activity rather than applying the same control to every browsing session.
Execute web content in a remote controlled environment rather than directly on the endpoint.
Create isolated sessions with defined lifecycle and policy controls.
Reduce direct endpoint exposure to potentially malicious or untrusted web content.
Control movement of information between the isolated environment and the endpoint.
Apply user and group identity to isolated browsing policies.
Monitor sessions, security events and access activity.
Generate audit trails and security events for operational and security visibility.
Core capabilities include remote execution, session lifecycle, threat containment, download/upload controls, clipboard controls, policy-controlled sessions and audit/SIEM integration.
A remotely executed browser environment designed for higher-risk web activity.
Shared services for identity, policy, session management, DLP, data controls, monitoring, audit, security events and SIEM integration.
The Remote Ephemeral Browser provides an isolated execution environment for browsing activity that requires a stronger security boundary.
The isolated session can be created for the required activity and managed according to organizational policy.
Browser-based threats can originate from websites, downloads, scripts, advertisements, documents and other external content. Browser Isolation moves higher-risk execution away from the endpoint and provides an additional execution boundary.
The underlying security model combines Zero Trust, DLP, encryption, policy and audit.
Moving browser execution remotely is only one part of the security model. JupitoSecure Browser Isolation also controls how information moves between the isolated browser and the endpoint.
Apply policy before information leaves the isolated environment.
Control information entering the isolated browsing environment.
Control clipboard-based transfer paths.
Apply policy to information exchanged through the session.
Control how information moves between the isolated environment and endpoint.
Browser Isolation can be deployed across cloud, VM, on-premises and existing infrastructure. It can be integrated with existing JupitoSecure platforms and infrastructure rather than requiring an organization to redesign its entire browsing environment.
Isolate access to unknown or higher-risk websites.
Interact with external content through a remote execution environment.
Provide controlled browsing for investigation and analysis.
Provide external users with isolated browser environments.
Reduce direct endpoint exposure to browser-based threats.
Control how information moves between the isolated environment and endpoint.
High-Risk Browsing • Untrusted Content • Third Parties • Security Research • Threat Reduction
Start with managed browsing through Enterprise Browser and introduce isolation for destinations or workflows requiring an additional execution boundary.
The goal is not to isolate everything. Use the appropriate execution boundary for the risk of the activity.
Add a stronger execution boundary for higher-risk browsing without changing the way users work.