Enterprise security. Built for what’s next.
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 Secure Access

Use the existing endpoint-management and identity teams. Separate package installation, enrollment, and traffic-policy rollout so each stage can be tested independently.

The integration sequence
  1. 01Deploy package

    Use the approved signed client for each OS.

  2. 02Enroll device

    Bind tenant, credentials, and management context.

  3. 03Select traffic

    Agree routes, DNS, IPv6, and application scope.

  4. 04Test continuity

    Exercise roaming, renewal, and gateway recovery.

ACCEPTANCE WORKSTREAMS
  • UEM delivery and required OS permissions
  • Device-key custody and renewal
  • DNS, split routing, and overlapping networks
  • Sleep, captive portals, and user-facing recovery
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 systemIntegration responsibilityEvidence before rollout
Identity providerFederation, groups, user lifecycle, and step-up authentication.Issuer/audience validation, signing rotation, and deprovisioning.
UEM / endpoint securityClient distribution, enrollment, device health, and managed configuration.Supported OS/release matrix and freshness of device signals.
Private network / cloudConnector placement, origin DNS, egress, and failure domains.Approved destination map and failover results.
Enterprise PKIClient/server issuance, root distribution, key custody, and revocation.Validated chains, correct service identities, and renewal tests.
SIEM / SOCEvent 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 Secure Access evaluation checklist
markdown
# Antara Secure Access: 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
- [ ] UEM delivery and required OS permissions
- [ ] Device-key custody and renewal
- [ ] DNS, split routing, and overlapping networks
- [ ] Sleep, captive portals, and user-facing recovery
- [ ] 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