How entitlements are used in the AppGate ZTNA system
Policies assign entitlements to users. Each entitlement token issued defines the entitlements available to a specific user or device for a specific Site.
The main elements of an entitlement are:
Client app shortcuts
Actions, which define the protected hosts and the rule to apply. The default rule is
<ALLOW>, but actions can also use<BLOCK>,<ALERT>, or<EXCLUDE>.Access controls applied by Gateways to the actions.
<Always Allow Action>is the default.<Risk Based Access>applies access controls without using conditions.<Condition Based Access>supports more complex configurations based on access criteria expressions or scripts.
For example, an entitlement for Site net1 might allow TCP traffic to 10.0.0.1 on port 80 using <ALLOW>, but only between 09:00 and 17:00.
Key elements in entitlements
Before you create an entitlement, review these areas so you can take full advantage of the AppGate ZTNA system:
AppGate ZTNA entitlement actions use host definitions to specify which firewall rules to apply. Unlike traditional firewall rules, the source (or destination for down rules) is assumed to be the user or device. With one less parameter to manage, host definitions can go beyond the limits of IP addresses and hostnames.
Entitlements can also include access controls. You can use Always Allow Action(s), or you can base access on the risk model or conditions. Risk- and condition-based controls let you decide when actions are allowed, for example, based on the user’s current risk score.
Design guidance: using multiple entitlements
To allow access to protected hosts on a Site, create at least one entitlement for that Site and add it to a policy. You can group many hosts into one action or many actions into one entitlement, but AppGate ZTNA is designed to provide granular, per-user access. In most cases, use multiple entitlements.
Use different policies (each can include multiple entitlements) to organize access for different user groups. This can reduce complex, overlapping entitlements.
Use the entitlement’s Notes field to document how the entitlement is used.
Set access controls per entitlement. User interactions (such as prompts) apply to all actions in that entitlement.
Use audit logs generated by entitlements to support audit trails.
Account for metadata. Many entitlements with large amounts of metadata can increase Gateway memory usage.