AppGate ZTNA protects your environments with multi-stage authentication and authorization that you can configure on an as-needed basis. AppGate ZTNA offers true multi-stage authorization and complements this with a richer set of authentication options that you can deploy at different points in the usage cycle. This approach changes the traditional view of authentication from a fixed step in a process. Instead, it considers context, such as what the user has already done and what they will do next. For example, the user may have already used multifactor authentication (MFA) when they onboarded their device, removing the need to use it again.
This section provides an overview of multi-stage authorization security controls available from pre-authentication to authorization at time of use.
1. Single packet authorization: access to appliances (trusted connection)
The Controller automatically generates Single Packet Authorization (SPA) keys and uses them throughout the Collective for peer-to-peer connections. Separately, the Controller generates keys for client-to-Gateway SPA access uniquely for each Gateway and includes them in entitlement tokens. These parts of the SPA process are completely internal and require no admin or user interactions.
A client needs SPA keys to connect to the Controller. Create one or more client profiles for the Collective. These profiles include the SPA key. Distribute them as a special profile link, a QR code, an email template, or an embedded onboarding web page. In multi-tenant environments, each tenant receives its own key through a separate profile. When a client connects, the Controller ties only the keys for the client profiles listed in the admin UI.
2. Device registration (trusted device)
Registering new devices prevents one of the most common forms of breach: someone using stolen credentials to sign in to a system from a new device. At sign-in, the Controller and client create and save a cookie to present at subsequent connection attempts. This allows the Controller to perform additional checks at sign-in using this information. On the first attempt, the Controller checks the device count and denies access if it exceeds the set limit. If this check passes, you can require MFA at sign-in: once, to register a new device, or every time, for new and registered devices.
3. Gather claims and authenticate (trusted user)
When a user signs in using the client, it passes up to four claims (key-value pairs) to the Controller for authentication:
DeviceID
IdentityProvider
Username (not required for SAML)
Password (not required for SAML)
The Controller first checks the credentials against the system’s denylist, then against a defined identity provider (IdP). If the user is authenticated, the next step establishes their rights.
4. Policy assignment criteria: authorization (trust through context)
After authenticating the user, the Controller uses the claims information to parse the policy assignment criteria in all policies. It then assigns the policies that are valid for the user.
The Controller creates a claims token and entitlement tokens listing all valid entitlements, creating one entitlement token for each Site identified in the entitlements. It sends these tokens to the client, which forwards them to the Gateways. If the user's claims do not match any assignment criteria in any policies, the user does not receive any entitlements.
You can set a token's lifetime so the Controller re-authorizes the user every x minutes. An administrator can also renew tokens when required. For more details on the token flow, see the System operation section.
5. Conditions, claims, and user interactions (elevating trust level)
Checking claims using conditions
On receipt of the claims token and entitlement token, the Gateway translates entitlement actions into firewall rules. These rules authorize traffic from the client depending on whether conditions are True or False.
The Controller provides the entitlement token to the client based on policy assignment criteria. Each token includes the list of Gateways for that Site. The client selects and connects to a Gateway, then forwards the token to establish firewall rules.
When a token is about to expire, the Gateway automatically notifies the client, and the client asks the Controller for a new token. The Controller renews the entitlement token, which then contains the most up-to-date entitlement and condition information.
You can link each entitlement to a condition, and the system checks that condition at time of use. If the entitlement does not include alternative conditions, it defaults to always available. A condition can include a user interaction that triggers if other access criteria are false. If the user interaction requires a response before granting access, the connection to the target host stays invisible until the user provides a response that satisfies the condition.
The Controller regularly reevaluates claims and reconfigures firewall rules in response to real-time changes.
Performing user interactions
User interactions allow the user to gain access to an entitlement that is currently blocked due to conditions. They satisfy alternative access criteria, such as performing MFA.
When an entitlement is blocked and a condition includes a user interaction, the Gateway sends a user interaction to the client. If the client determines the user's response is appropriate, the Controller updates the claims token. The Gateway then reevaluates the conditions in the entitlement to produce new firewall rules.
The types of user interactions available are:
Display Message. Displays a message to the user, such as '“please use the wired network for access”.
Require MFA. Prompts the user to perform MFA for access.
Provide Reason. Prompts the user to enter text before continuing.
Password. Prompts the user to enter or reenter their password.
For more information, refer to the user interactions section.
