--- title: "Zero trust-based" slug: "zero-trust-based-v7-0" description: "AppGate ZTNA offers a secure Zero Trust Network Access model, ensuring real-time, context-aware control through the six-layer model." tags: ["Zero Trust Access", "Software Defined Perimeter"] updated: 2026-09-10T00:59:14Z published: 2026-09-10T00:59:14Z canonical: "support.appgate.com/zero-trust-based-v7-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.appgate.com/llms.txt > Use this file to discover all available pages before exploring further. # Zero trust-based ## AppGate ZTNA Overview AppGate ZTNA uses a Zero Trust Network Access (ZTNA) model that hides systems from unauthorized users and requires detailed contextual information to establish trust before granting network access. The software-defined perimeter (SDP) implements ZTNA through appliances using Single Packet Authorization (SPA). Port 443 connections are blocked unless the appliance receives a pre-agreed, cryptographically signed SPA packet first. - Clients and appliances use SPA before establishing any TLS connection. - Controllers authenticate and authorize new user and device sessions, then provide the necessary tokens to the Gateway. - Gateways hide protected networks from unauthorized users and grant access through individual micro-firewall instances, with rules defined by the token payload. **Trust establishment with the six-layer model** AppGate ZTNA uses a multi-layer authorization model for real-time, context-aware access control. The following steps correspond to the process layers in the accompanying diagram. 1. Single Packet Authorization (SPA) hides the system so that only clients with the pre-shared key can establish a communication channel. The system accepts one or more SPA keys included in the [client profile](/v1/docs/client-profiles-v7-0). 2. [MFA at sign-in](/v1/docs/mfa-providers-v7-0) registers a user device as a second trusted authentication factor, blocking authentication attempts that use stolen credentials. Once a device is registered, the user does not need to complete MFA at every sign-in. 3. [Authentication](/v1/docs/identity-authentication-and-device-trust-v7-0) verifies user or device credentials against trusted sources such as a local database or LDAP. 4. [Authorization](/v1/docs/policies-v7-0) evaluates user or device claims data to assign specific entitlements. 5. [Access controls](/v1/docs/access-management-v7-0) monitor entitlements in real time to determine whether additional access criteria are required before granting access. The Gateway dynamically manages access rights based on defined actions. 6. [Alert actions](/v1/docs/using-entitlements-v7-0) trigger system responses to unauthorized behaviors, such as port scans. ![Illustration of the six-layer trust model for secure application access.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/appgate-six-layer-trust-model.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A49%3A36Z&se=2026-11-21T22%3A49%3A36Z&sr=b&sp=r&sig=bCstzHsO4BLmql2l74KZqD8yivQxeRaqpB3rNsYVAHU%3D) After the client receives the profile link and the device is onboarded, the user can select *Keep me signed in*. This makes the six-layer model transparent and requires fewer interactions than a standard VPN. Additional user interaction occurs only when a specific condition requires it.