Manual Chapter : About per-request policies

Applies To:

Show Versions Show Versions


  • 15.0.0
Manual Chapter

About per-request policies

APM executes per-session policies when a client attempts to connect to the enterprise. After a session starts, a
per-request policy
runs each time the client makes an HTTP or HTTPS request. Because of this behavior, a per-request policy is particularly useful in the context of a Secure Web Gateway or Zero Trust scenario, where the client requires re-verification on every request, or changes based on gating criteria.
A per-request policy can include a subroutine, which starts a subsession. Multiple subsessions can exist at one time.
You can use nearly all of the same agents in per-request policies that you can use in per-session policies. However, most of the agents (including authentication agents) have to be used in a subroutine in per-request policies.