PLATFORM / INTEGRATION CENTER

Your network has a history.
Build on it.

Keep the systems that own identity, devices, applications, and evidence. Add the access and inspection boundaries where they belong, with a staged path from pilot to operations.

CHOOSE YOUR STARTING POINT

Choose the capability you are deploying.

Remote Browser Isolation

Introduce isolation for a defined browsing cohort. Preserve the identity provider, decide the session entry point, and apply data controls to the browser workflows people actually use.

The integration sequence

01Federate identity
Map the pilot users and authentication policy.
02Choose entry
Select browser launch, redirect, or managed access.
03Apply controls
Set upload, download, and clipboard policy.
04Validate experience
Test input, application tasks, and session evidence.

ACCEPTANCE WORKSTREAMS

✓ Identity redirects and multi-tab sessions
✓ Origin egress and private application reachability
✓ Keyboard, IME, zoom, and accessibility
✓ Data-transfer policy and audited outcomes

Read the complete integration guide

CLEAR OWNERSHIP. FEWER SURPRISES.

Five handoffs to get right.

Use the systems already responsible for each part of your environment. Confirm release-specific interfaces during the architecture review.

Existing system	Integration responsibility	Evidence before rollout
Identity provider	Federation, groups, user lifecycle, and step-up authentication.	Issuer/audience validation, signing rotation, and deprovisioning.
UEM / endpoint security	Client distribution, enrollment, device health, and managed configuration.	Supported OS/release matrix and freshness of device signals.
Private network / cloud	Connector placement, origin DNS, egress, and failure domains.	Approved destination map and failover results.
Enterprise PKI	Client/server issuance, root distribution, key custody, and revocation.	Validated chains, correct service identities, and renewal tests.
SIEM / SOC	Event delivery, identifiers, timestamps, retention, and investigation access.	Searchable evidence tied to a tenant, session, and policy.

LEAVE WITH AN OPERATING PLAN

Make the pilot reviewable.

Capture the owners, dependencies, test cases, and rollback criteria before expanding the deployment.

Remote Browser Isolation evaluation checklist

markdown

# Remote Browser Isolation: deployment evaluation

## Ownership
- Application owner:
- Identity owner:
- Network / endpoint owner:
- SOC owner:

## Scope
- Pilot users and devices:
- Application dependencies:
- Client / gateway release matrix:
- Data retention and evidence permissions:

## Acceptance
- [ ] Identity redirects and multi-tab sessions
- [ ] Origin egress and private application reachability
- [ ] Keyboard, IME, zoom, and accessibility
- [ ] Data-transfer policy and audited outcomes
- [ ] Failure and recovery behavior documented
- [ ] Rollback owner and trigger agreed
- [ ] Business task completion accepted

## Promotion
- Evidence links:
- Open exceptions and expiry:
- Approval record:

ARCHITECTURE TO OPERATIONS

Bring your evaluation to the team.

Discuss your environment