2AYE
Guides, reference & supportCapability status
Remote access and VPN

Apply phishing-resistant identity and device policy before private-resource access.

2AYE models RADIUS and VPN integration as a planned adapter. This page provides the required control architecture, not a production connector claim.

  • Strong entry proof
  • Device health
  • Scoped resource access
What you can evaluate

Remote access built around identity, not network location.

01

Strong entry proof

Require passkeys for privileged or sensitive remote access.

02

Device health

Refuse unknown or noncompliant posture according to policy.

03

Scoped resource access

Assign users and groups only to required private resources.

04

Session response

Revoke or step up when identity or posture changes.

The enforcement path

Follow Remote access and VPN from identity to evidence.

Each consequential action moves through the same six control points. See where 2AYE evaluates authority, requests human review, and preserves the outcome.

  1. 01IdentityWho or what is acting
  2. 02IntentSigned purpose and limits
  3. 03PolicyDeterministic evaluation
  4. 04ApprovalA named human when required
  5. 05ExecutionSingle-use grant, redeemed at the resource
  6. 06EvidenceReceipt joined to the audit chain
Deterministic decisionsSingle-use, exact-action grantsHash-linked evidence

Your next move

Look beyond the connection.

Choose a step.
See what matters for your workflow.

Focus / 01

Map private resources

Assess a protected private-resource access path.

Explore the developer guide
Remote access and VPN

Interactive planning guide. Explore the steps without changing your setup.