NPSS cache consistency limits during policy revocation

The Network Policy Security Service (NPSS) utilizes local caching at the enforcement points to minimize latency in high-frequency request environments. While this architecture optimizes performance, it relies on a Time-To-Live (TTL) mechanism for policy synchronization across distributed nodes.

A challenge arises when a critical policy update or revocation occurs in the central repository. Because the current implementation prioritizes periodic polling over immediate event-driven push notifications, there is a documented window where revoked permissions may still be honored by an edge node until the local cache expires or the next polling cycle completes.

What is the maximum guaranteed latency window between a central policy update and edge-node enforcement? Can the cache invalidation granularity be adjusted to support strict consistency without causing an unsustainable load on the policy management server?