{
  "id": "p_VTlEqdnpua5BlEjF",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_VTlEqdnpua5BlEjF",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "Picture it: you run security for a team that lets engineers onto a jump box when they need privileged access. Someone gets approved, logs in, and does their work. Later, an auditor asks which customer records that person touched, how many, and for how long. You open the approval. It says a person was approved onto a machine. It says nothing else.\n\nThat gap is what Cerbos is pointing at in its guide on replacing jump-box privileged access with policy-based authorization at the API gateway. The post argues the privilege decision is being made in the wrong place. A jump box approves a person onto a machine, and the approval, in the post's words, \"said nothing about which records they would touch, how many, or for how long.\"\n\nSo the guide proposes something different for you to consider. Route the privileged work through the gateway, and check every call against a grant that has four bounds: time, endpoint, object and volume. The example policy fits each check on one line of CEL. One line compares the clock against the grant's expiry. Another compares the resource ID against the approved accounts. A third checks requests used against the quota. The post sums the pattern up in five words: \"Approve the request, not the session.\"\n\nYou might wonder whether your always-on access is unusual. The strongest number in the post isn't Cerbos's own. 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 also leans on CyberArk's relaunch as Idira under Palo Alto Networks as evidence that the incumbents agree with the direction.\n\nNotice what the post does not ask of you. 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. You keep what you have. The change is where the decision about each call gets made. That restraint makes the rest of the argument more credible, and you should still remember that this is a vendor describing its own approach.\n\nIf you wanted to see what you would actually call, the APIs.io catalog maps everything the post describes to pages on the Cerbos provider page. The per-request decision is the Cerbos Check API, with a standards-shaped version on the Cerbos AuthZEN API. The grant attributes fetched at decision time come from Cerbos Synapse. The decision log, which the post calls \"the business case,\" is collected by the Cerbos Hub API and exposed by the Cerbos Admin Audit API. That last piece answers your auditor: every decision is on record.\n\nNow the turn, and it matters before you commit to anything. The catalog holds Cerbos to the same lens it applies to everyone. It 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.\n\nThe 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. So you hold two things at once. The argument for per-request grants is persuasive, backed by a number that isn't the vendor's. And the vendor's own published contract is thinner than the argument it makes.\n\nWhat you take away is practical. Ask of your own privileged access what the approval actually says about records, volume and duration. If the answer is nothing, the gap the post describes is yours too. Consider bounding grants by time, endpoint, object and volume, keep your PAM platform for vaulting, session brokering and secret rotation, and when you evaluate any provider for the job, read its contract as closely as its pitch.\n\nRead the original: https://apis.io/2026/11/17/cerbos-says-approve-the-request-not-the-session/",
  "title": "You approved the session. Cerbos says to approve the request",
  "topics": [
    "privileged-access",
    "authorization",
    "cerbos",
    "api-governance"
  ],
  "published_at": "2026-11-17T15:29:30.406Z",
  "expires_at": null,
  "policy_version": "2026.11.14-1"
}
