Approved apps in the browser
Publish scoped web applications behind identity-aware access policies.
BROWSER-BASED PRIVATE ACCESS
Their device. Your security policy.
A browser-based path for partners, contractors, and unmanaged devices to reach approved applications without installing Secure Access. The same Antara Admin policies govern this approved clientless entry.
THE CLIENTLESS ACCESS FLOW
01Authenticate the external user
02Authorize an approved application
03Launch a controlled browser session
04Revoke or expire access centrally
Consistent policy at every decision point.
INSIDE CLIENTLESS ACCESSDesigned as an architecture.
Designed as an architecture.
Understood in practice.
Explore the integrated capabilities, then use
the lab to see the underlying decisions.
Remote browser isolation
Model a remote session that separates enterprise application execution from the unmanaged endpoint.
Session-level data controls
Govern downloads, uploads, clipboard transfer, and session duration where the isolation platform supports enforcement.
A controlled partner experience
Use time-bound access, passkey or MFA authentication, and explicit resource entitlements.
Application access and browser isolation.
Clientless Access
Determines which private application a user can reach through a browser. The access layer authenticates the user and publishes the approved resource.
Clientless Access capability detailsRemote Browser Isolation
Determines where web content executes and how session data moves. A remote browser runs the page while the user interacts with a delivered view.
Browser Isolation capability detailsThese capabilities can work together. Browser-based application publishing does not automatically provide remote execution or isolation.
- Confirm application compatibility with browser-based publishing.
- Use a native client when full network transport or device-level controls are required.
- Validate isolation service behavior and supported data controls.