Real-time reevaluations

Prev Next

The AppGate ZTNA system is designed to reevaluate access rights in real time. Examples of events that can trigger a reevaluation include:

  • A user's situation changes (moves networks).

  • Resources in a protected network change (name resolver).

  • A device claim changes (firewall turned off).

  • An administrator creates and pushes a new policy (token renewal).

For steps to configure the reevaluation of access rights, see Configuring conditions.


Real-time control of access

The access criteria set in a condition define when the AppGate ZTNA system enables an entitlement for a user. The system evaluates access criteria whenever a user attempts to access a resource. After access is granted, the system can automatically reevaluate access criteria at the appropriate times (for example, after a network change). Because these triggers are event-driven, the exact reevaluation times are not predictable. In general, more complex access criteria are reevaluated more often. With very simple access criteria, the first reevaluation might not occur until the user’s tokens expire.

In many cases, the system requires no additional time-based reevaluation settings. However, some scenarios do require them.

Setting reevaluation times

In most deployments, you do not need to set reevaluation times. You might set them in the following situations:

  • You use an access criteria script that returns values that change frequently.

  • You create a condition that depends on an absolute time.

  • You want to ensure that MFA and password conditions (which specify how long a user response claim is considered true) are enforced.

The system already includes many automatic reevaluation triggers (shown across the top of the diagram below). If you add explicit reevaluation times, balance time accuracy against Gateway load and the intent of the security policy you want to enforce. Reevaluation is compute-intensive; short, frequent reevaluation periods can add significant load on Gateways. For example, avoid configuring a condition such as “after 17:00” and then setting periodic reevaluation every five minutes to check it.

Flowchart illustrating access evaluation criteria and user interaction processes.

Before you set reevaluation times, understand how user interactions and their related user response claims (Provided MFA, Retyped Password) work. When a user completes a user interaction, the system timestamps the user response claim at the next quarter hour. For example, if a user enters a password at 14:32, the claim timestamp is 14:45. As a result, setting periodic reevaluation to 12 times per hour is not useful for these claims.

To help prevent users from being disconnected when a reevaluation determines that a claim has expired, the system provides a five-minute warning window. The Gateway checks whether the condition will still pass five minutes later and, during that window, triggers the user interaction again (before the condition fails). This helps prevent the user’s session from being lost due to firewall rule changes.

Time of day for reevaluation (UTC)

The Gateway reevaluates a user’s claims at the specified times. This is required if the access criteria includes a temporal element, such as “only after 17:00.”

Example: The condition includes time-based access criteria between 8:30 and 17:00. Set a specific reevaluation time for 17:01 so the condition fails at that time and access is no longer available. You might also use a specific time when an external access criteria script must run at a particular time.

User actions and criteria for backup scheduling in UTC format displayed on the screen.

Periodic reevaluation (UTC)

The Gateway reevaluates a user’s claims on a set schedule relative to when they log in. This is mainly required when you use password and MFA user interactions to check whether the related claims are still valid.

Periodic reevaluation can also be useful when you use an external access criteria script and the returned values are known to change frequently.

Example: The condition includes “Provided MFA within 60 minutes.” Set a periodic reevaluation time to so the condition eventually fails (unless another user interaction is performed) and access is no longer available. Periodic reevaluations are based on UTC according to when the user logged in, not on when the user performed a user interaction. This means the next evaluation can occur any time from a second or two later to almost an hour later, depending on when the initial evaluation took place. For example, if a password is required every 60 minutes and it was entered at 14:32, the setting triggers the next user interaction at 15:32. If the user responds at that time, the new claim timestamp is 16:32, and the next user interaction occurs at that time.

User actions for MFA and reevaluation settings in a security configuration interface.

Because user response claims are always timestamped at the next quarter hour, 4 times per hour is the best setting for shorter periods (up to every six hours). For longer periods, use Once per hour.

The 12 times per hour option is typically required only when you use external criteria scripts.

When Risk based access is used, periodic reevaluation defaults to 4 times per hour.


Reevaluation triggers

To detect these changes, you can configure parts of the system to manually or automatically update a user’s access rules without user intervention. The following table lists reevaluation triggers and the effects of each reevaluation.

Trigger

When (default)

Policies
(Controller)

Claims
token updated

Entitlement
token updated

Entitlement script run

Firewall rules (Gateway)

Client sign-in (to Controller)

By user/device

y

y

y

n/a

n/a

Client connects to Gateway

By client

n

n

n

y if conditions = true

Session added

Access event trigger

User access or not (OTP)

n

y for OTP and password

n

y if conditions = true

y

Device claims checked

Every 5 minutes (fixed)

n

n

n

y if change reported & new condition = true

y if change reported

Periodic reevaluation times

0/5/15/60 minutes

n

n

n

y if conditions = true

y

Specific reevaluation times

@time (17.00)

n

n

n

y if conditions = true

y

Claims token expire/update

Every 24 hours or ??

y

y

n

y if conditions = true

y

Entitlement token expire/update

Every 24 hours or ??

y

n

y

y if conditions = true

y

Host API (name resolver) checked

Every 60 seconds or ??

n

n

n

y if change reported & condition = true

y if change reported

Alert triggered

By behavior

n

n

n

y if conditions = true

y

Token renewed

By admin (admin can choose)

y

y

y

y if conditions = true

y

Client reconnect

Sleep/HA

n

n

n

y if conditions = true

y

Client reconnect

Roaming (IP change)

y

n

y

y if conditions = true

y

Client sign-out

By user/device

n

n

n

n

Session removed

  • Follow the links to the sections where you configure trigger parameters.