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.

Antara ZTNA

Move one application first. Federate the existing identity source, place redundant connectors near the origin, and publish only the required resource scope.

The integration sequence

01Map resource
Name the application, owner, ports, and dependencies.
02Connect origin
Register redundant outbound connectors.
03Bind identity
Map groups, device context, and access conditions.
04Prove scope
Test allowed, denied, and changed-context cases.

ACCEPTANCE WORKSTREAMS

✓ Federation and user deprovisioning
✓ Origin DNS, ports, and dependency mapping
✓ Device-signal freshness and unknown states
✓ Connector failover and session reevaluation

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.

Antara ZTNA evaluation checklist

markdown

# Antara ZTNA: 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
- [ ] Federation and user deprovisioning
- [ ] Origin DNS, ports, and dependency mapping
- [ ] Device-signal freshness and unknown states
- [ ] Connector failover and session reevaluation
- [ ] 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