Control which users and devices can reach protected resources, what they can reach, and when. AppGate ZTNA builds access from three layered components: policies assign entitlements, entitlements define the protected resources, and conditions set the criteria that users must meet before access is allowed. Ringfence rules separately control traffic on the client device itself.

Use the following topics to configure access:
Policies. Define who gets access by assigning entitlements, admin roles, device controls, and DNS settings to users or devices after sign-in. Claims-based assignment expressions determine which policies apply. Stop policies block a user or device from authenticating.
Entitlements. Define what users can reach on a given Site. Each entitlement uses actions to specify the protected hosts and how to handle their traffic, and applies an access control: always allow, risk-based access, or condition-based access.
Conditions. Define when access is allowed. Conditions use claims-based access criteria, such as an office IP address or time of day, that must evaluate to true before an entitlement’s actions apply. Add a user interaction, such as a multifactor authentication prompt, so users can meet the criteria and unblock access themselves.
Ringfence rules. Control local inbound and outbound connections on client devices to reduce the risk of malware spreading on public networks, while still allowing tunnel traffic to Gateways. Device policies assign ringfence rules to clients.
NOTE
Ringfence rules can’t use conditions.