Cerbos’s guide on replacing jump-box privileged access with policy-based authorization at the API gateway argues that the privilege decision is being made in the wrong place. A jump box approves a person onto a machine, and the approval “said nothing about which records they would touch, how many, or for how long.” The post proposes routing privileged work through the gateway instead and checking every call against a grant with four bounds: time, endpoint, object and volume. The example policy fits each check on one line of CEL: the clock against the grant’s expiry, the resource ID against the approved accounts, and requests used against the quota. The post’s own summary of the pattern is short: “Approve the request, not the session.”
The strongest number isn’t Cerbos’s. A January 2026 study of 500 US practitioners found that 91% report at least half of their privileged access is always-on, and only 1% have fully implemented just-in-time access. The post leans on CyberArk’s relaunch as Idira under Palo Alto Networks as evidence that the incumbents agree. Cerbos is careful about what it doesn’t claim. It says the pattern is “not a case for retiring your PAM platform,” because vaulting, session brokering and secret rotation still belong there. That restraint makes the rest of the argument more credible.
Everything the post describes maps to a page on the Cerbos provider page. The per-request decision is the Cerbos Check API, with the standards-shaped version on the Cerbos AuthZEN API. The grant attributes fetched at decision time come from Cerbos Synapse. The decision log the post calls “the business case” is collected by the Cerbos Hub API and exposed by the Cerbos Admin Audit API. The catalog records 13 API pages, and the agentic-access profile counts 22 operations, 12 acting and 1 that needs a human in the loop.
On the Kin Score, Cerbos measures 49.9, in the developing band. Developer ergonomics carries it at 68.3. Contract governance is 13.6, and contract quality is 42.2. Agent Readiness is 22.8, rated agent-aware, with error semantics, idempotency, reversibility documented and the MCP server dimension all unlit. The post closes on “Prove every decision,” and the decision log really does do that for its customers’ APIs. The catalog can’t yet say the same about the contract behind Cerbos’s own API.