--- title: "Policies" slug: "policies-v7-0" description: "Learn how policies in the AppGate ZTNA system assign user rights, evaluate claims, and enhance security with five distinct policy types." tags: ["Access Management", "Policies"] updated: 2026-09-18T21:29:27Z published: 2026-09-18T21:29:31Z canonical: "support.appgate.com/policies-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. # Policies ## How policies are used in the AppGate ZTNA system Policies are the entry point to the AppGate ZTNA system and assign rights to users or devices after a successful sign-in. There are five policy types: - **Access** through Gateways based on entitlements and any related conditions that apply - **Admin** rights for one or more administrative roles, including the admin UI and APIs - **Device** controls pushed to the client, such as ringfence rules or client profile settings - **DNS** settings comprising match-domain DNS settings and the required entitlements for specified DNS servers - **Stop** assigning policies and do not authenticate the user or device Policies are assigned on a per-user basis using claims-based assignment expressions. The resulting settings and entitlements are then passed to the client. After sign-in, the system evaluates policies to determine which policies to apply to the user or device: - Stop policies are evaluated first. If a stop policy matches, only that policy is applied and the evaluation process ends. Because evaluation stops on the first match, only the first matching stop policy is applied. - If no stop policy matches, the other four policy classes are evaluated. When a policy matches, it is applied and evaluation continues. All matching policies are applied. Because all other classes of policies are evaluated, consider the total number of policies and the complexity of assignment expressions. More policies and more complex expressions can increase sign-in time by about `(policy_count/15)mS`. For example, 1,500 policies can add about 100 ms to a typical sign-in. ## Policy assignment Claims-based assignment expressions define which users and devices a policy applies to. The Controller evaluates these expressions immediately after sign-in and when tokens are renewed. Use static claims that are unlikely to change during the day (for example, directory group membership or email address). Each policy can include one or more criteria expressions. You can also add access control to an entitlement to control whether the entitlement is allowed when the user or device attempts to send traffic to a protected host. Policy assignment criteria are evaluated after sign-in; entitlement access control is evaluated when traffic is attempted. Criteria expressions have three different combining modes: - ****: A logical `AND`. All criteria must be true. - ****: A logical `OR`. At least one criterion must be true. - ****: A Boolean expression that references multiple criteria. These modes provide a powerful way to control when a policy is assigned. If you need logic that the modes do not support, use an assignment criteria script. For example, you can assign a policy only after a future date: `var today = new Date();var futureDate = new Date('2030-12-31');return today > futureDate;` ### Assignment criteria sScripts The AppGate ZTNA system evaluates claims through assignment criteria expressions to make policy assignment decisions. In most cases, you can configure criteria in the policy by using the assignment options and the claims drop-down list; the UI generates the underlying JavaScript expression. In those cases, you do not need to write a separate script. For more information, see [Criteria scripts](/v1/docs/criteria-scripts-v7-0). ## Policy elements Five policy types can be provisioned to different user and device groups. The table below describes key elements of each policy type: | Policy type | Elements | | --- | --- | | ***Access Policy*** | **Entitlements** Predefine the entitlements to include in the policy. Selected entitlements by name or tag. Include only the entitlements users need for their roles, and avoid wide-ranging, “catch-all” entitlements. Within a single policy, you can combine entitlements with different access control requirements, for example: - Allow always-on access to essential network resources, such as email. - Require conditional access (for example, multifactor authentication) for higher-risk actions, such as access to a customer database. **Override Site** Each entitlement must specify a Site. The Site tells AppGate ZTNA where to find the resource. Within a policy, entitlements are grouped by Site and used to create one entitlement token per Site. When you configure a policy, you can set an [override Site](/v1/docs/configuring-policies-v7-0) to replace the Site specified in the entitlement. All entitlements in the policy are grouped together and issued a single entitlement token for the override Site. An override Site can be useful in these situations: - *Override from the list*. Use an override Site as a stopgap while migrating from a classic VPN topology to an SDP model. This can provide a single point of entry into the corporate network, with traffic routed to other Sites over the WAN. - *Override using a claim*. Use a claim that returns the UUID of the Site to use. Typically, a [user claim script](/v1/docs/user-claim-scripts-v7-0) sets this claim. This option can help you route users to a specific Site in a global Collective during an outage or failover. - *Override with the nearest Site*. Provide [geolocated Site access](/v1/docs/tunnel-architectures-v7-0) based on the user’s nearest Site, which can help reduce latency. If multiple policies specify an override site and include the same entitlement, the entitlement is assigned only through the policy whose name is closest to the beginning of the alphabet. | | ***Admin Policy*** | **Administrative Roles** Use an admin policy to assign administrative privileges. In the policy criteria, identify the administrator users, then select the predefined admin roles to assign. For details, see [Admin user access](/v1/docs/admin-user-access-v7-0). | | ***Device Policy*** | Assign only one device policy whenever possible. If multiple device policies are assigned, they can include conflicting requirements (for example, two different proxy PAC files). To ensure a deterministic result, if conflicting controls are assigned, the system uses the policy whose name is closest to the beginning of the alphabet. For details about what you can configure with a device policy, see [Device and client controls](/v1/docs/device-and-client-controls-v7-0). | | ***DNS Policy*** | **DNS Configuration** The client uses the DNS servers and match domains in a DNS policy to configure DNS on the local operating system. A typical configuration includes a match domain and internal DNS server(s) that can resolve protected hosts. If no DNS policy is assigned, the client uses the DNS settings from the identity provider. If multiple DNS policies are assigned with the same match domain, they can conflict. To ensure a deterministic result, the system uses the policy whose name is closest to the beginning of the alphabet. For details about hostname resolution, see [DNS and name resolution](/v1/docs/dns-and-name-resolution-v7-0). | | ***Stop Policy*** | Stop policies are evaluated first. On the first match, the system stops evaluating policies. This makes stop policies fast to evaluate and can significantly reduce Controller load. Stop policies are typically used for these scenarios: - **Security**. Normally, SPA prevents unwanted access to Controllers. If your SPA key is widely distributed, you can add a stop policy for criteria you never want to allow. Examples: block all Mac devices (os.family = macOS), or block connections from Africa (geoIp.continentCode = AF). - **Stop specific users or devices**. Use a stop policy to block users or devices you no longer want to allow. For example, use *All Criteria below must be true* mode, then add one or more `ag.distinguishedName` claims. If you remove the client profile, you can prevent future connection attempts.. - **Temporary load reduction**. Temporarily stop specific user groups when Controllers cannot handle the volume of inbound requests, for example, due to a misconfiguration (a headless client with no policy) or an external event (such as a network outage). |