Skip to content
IAM Insights

Explainers · Glossary

ReBAC

relationship-based access control · Relationship-Based Access Control

Access control that decides by the relationships between a subject and an object (owner, member, parent folder) rather than by fixed roles; Google's Zanzibar and OpenFGA are built on it.

In our briefings

The claim each of the newest briefings on ReBAC would have you leave with.

  1. Drus sorts microservice authorization into five patterns, from his rework of OWASP's microservice security cheat sheet; the names are his own, and he says three were already in the sheet and two are new. Keeping the decision in a service's own code is fine, he says, when policy and data are local to that service. An external decision point such as Open Policy Agent or OpenFGA still leaves enforcement in the code. Classic edge authorization moves enforcement into the gateway, but business rules live in the APIs, so every API change means asking the gateway's owners: "it doesn't work, it doesn't scale". His modern edge pattern lets each team set the gateway's rules declaratively, and the gateway issues a signed internal token, which he calls an authorization contract, that the receiving service checks. He says a sidecar decision point can do the same, and that few tools support the modern edge approach yet. Which pattern fits depends, he says, on where the policy and its data live, and in practice the patterns are combined.

    Five places to put authorization in microservices, and why Drus says the classic gateway one does not scaleBI-FIND-2026-1487

  2. AAP puts narrowing on the authorization server. On every token exchange the server must reduce privileges "by one or more of" four means (dropping capabilities, tightening constraints, shortening the token's lifetime, or lowering the delegation limit) and must never grant a capability the parent token lacked. As written, a derived token that keeps every capability and only expires sooner meets that rule. Section 7.7 also tells the resource server to "ensure delegated tokens do not contain broader capabilities than the original agent token", yet about its parent a derived token carries only an identifier and an optional note of what was removed, and the draft does not say how the server learns what the original token held. The resource-server conformance checklist in Appendix D lists no such comparison; its delegation checks are counts, depth against max_depth and chain length against depth plus one.

    An OAuth profile for AI agents makes every hand-off cut privileges, but a shorter expiry alone counts as a cutBI-FIND-2026-0964

  3. Both of Bifrost's critical flaws came from its management API shipping with authentication off (governance.auth_config.is_enabled=false by default) and its official Docker image binding that API to 0.0.0.0. In CVE-2026-90898 (CVSS 9.8, disclosed by JFrog on 14 September 2026), one unauthenticated POST to /api/mcp/client registered a stdio MCP client, and the gateway started the named command at once, before any MCP handshake, as its own process user. CVE-2026-86242 (CVSS 8.1, 6 September) loaded a plugin from a URL, though JFrog says full code execution needs a dynamically linked build, which the Docker image is not. Version 2.1.0 requires a setup token before the first admin account and, per the maintainer, binds to 127.0.0.1 when no dashboard login is configured; the 1.6.x line was still unfixed at 1.6.11. The post's headline blames MCP's lack of client authentication, but its body concedes "there was no protocol gap to close": on a gateway that accepts local servers, "Registration and execution are the same event", and the admin surface where that happens is one the MCP specification does not describe.

    Registering an MCP server on Bifrost ran its command, and the admin API that allowed it shipped with no passwordBI-FIND-2026-0481

Cited in 4 briefings

Every briefing that discusses this term, newest first.

  1. Five places to put authorization in microservices, and why Drus says the classic gateway one does not scale

    Video · · OWASP Foundation · Uploaded October 21, 2026

  2. An OAuth profile for AI agents makes every hand-off cut privileges, but a shorter expiry alone counts as a cut

    Draft · · IETF Datatracker · Angel Cruz · Feb 7, 2026

  3. Registering an MCP server on Bifrost ran its command, and the admin API that allowed it shipped with no password

    Article · · WorkOS Blog · Maria Paktiti · Sep 29, 2026

  4. Huawei researchers add agent delegation to an existing permission model and prove each action traces to a human

    Paper · · arXiv · Amjad Ibrahim et al. · Jun 2, 2026

Related terms

What appears alongside ReBAC in the same briefings.

SpiceDBOpenFGACedarOpen Policy Agent