--- title: "Robust resilient architecture" slug: "robust-resilient-architecture-v7-0" description: "Explore AppGate ZTNA's token-based architecture for Software-Defined Perimeter, enhancing flexibility and resilience in user access and security management." updated: 2026-09-10T00:59:40Z published: 2026-09-10T00:59:40Z canonical: "support.appgate.com/robust-resilient-architecture-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. # Robust resilient architecture ## The software-defined perimeter (SDP) model The software-defined perimeter (SDP) model requires an architecture that allows users, appliances, and networks to be located flexibly, with a separation between the control plane and the data plane. AppGate ZTNA follows this model through its three key components: Controllers, clients, and Gateways. #### ![Flowchart illustrating device sign-in, token passing, and gateway conditions for access control.](https://cdn.us.document360.io/e7482ce5-acfa-4c3b-b76c-b6c32472644a/Images/Documentation/sdp_model_appgate.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A55%3A39Z&se=2026-11-21T22%3A55%3A39Z&sr=b&sp=r&sig=%2BB%2BjOhxQGKfOS2QDLBqv%2BEp0W3SjlqQNbRAfoiToloE%3D) Unlike other SDP implementations, AppGate ZTNA uses a token-based architecture that improves interaction among these components and provides greater flexibility and resilience. [Token flows](/v1/docs/system-operation-token-flow-v7-0) eliminate the need for real-time interaction among the principal components and allow for the separation of operations. Client devices can independently manage their connectivity and switch to an alternative Gateway at any time, even if the Controller is unavailable. Tokens from Controllers contain all the information needed to configure and enforce specific routes on the connecting device and to inform the Gateway about user access rules. ### Tokens Tokens transmit information from the Controller to the Gateway through the client. Each token contains all data required for authentication, authorization, and access control. - The Controller acts as the Certificate Authority and generates signed tokens, which it sends to clients. - Clients use claims and entitlement tokens as needed. - Gateways use tokens to configure firewall rules and manage access on a per-user basis. - Tokens are formatted as JSON Web Tokens (JWT) using key-value pairs. - All tokens have expiration dates. Administrators can revoke tokens at any time. ### Controller The Controller provides [centralized administration](/v1/docs/admin-user-access-v7-0) and control over security policies, user entitlements, administrator privileges, network configuration, logging, and monitoring through the admin UI or REST API. When the first Controller starts, it creates a [self-signed certificate](/v1/docs/internal-certificates-v7-0#certificate-authority) that establishes it as the trusted authority for all tokens, certificates, and TLS connections. ### Gateway The Gateway is the enforcement point for controlling user access to protected resources. After registering with the Controller, it operates as a stateless appliance that requires only the token revocation list from the Controller. The Gateway uses claims and entitlement tokens to manage firewall rules and provide real-time access control. ### Client Clients maintain operational control. With each new connection, the Gateway checks the claims token, initiates the firewall service, and establishes firewall rules based on the client entitlement token.