ReBAC
Relationship-Based Access Control (ReBAC) is an access control model derived from the design philosophy of Google Zanzibar. It centers on a graph of relationships between entities and models permissions as the propagation of those relationships, making it well-suited for hierarchical and shared-resource scenarios.
Timeline (last 90 days)
ReBAC (Relationship-Based Access Control) excels at modeling collaborative relationships, but it cannot express the specific task an agent is executing and lacks the fine-grained control required for dynamic tool interactions.
TBAC (Task-Based Access Control) does not replace RBAC/ABAC/ReBAC but is a capability layer added on top of them, progressively narrowing permissions: from broad intent, to the systems and APIs that need to be reached, to precise and auditable transactions.
ReBAC (Relationship-Based Access Control) originates from the design philosophy of Google Zanzibar, with a relationship graph between entities at its core, where permissions propagate along relationships
The appropriate authorization approach for Agent systems is layered composition: use RBAC or ReBAC to define resource boundaries, supplement with ABAC for contextual conditions, and then use an intent layer for dynamic narrowing
All Facts (4)
ReBAC (Relationship-Based Access Control) excels at modeling collaborative relationships, but it cannot express the specific task an agent is executing and lacks the fine-grained control required for dynamic tool interactions.
50%UnverifiedTBAC (Task-Based Access Control) does not replace RBAC/ABAC/ReBAC but is a capability layer added on top of them, progressively narrowing permissions: from broad intent, to the systems and APIs that need to be reached, to precise and auditable transactions.
50%UnverifiedReBAC (Relationship-Based Access Control) originates from the design philosophy of Google Zanzibar, with a relationship graph between entities at its core, where permissions propagate along relationships
50%UnverifiedThe appropriate authorization approach for Agent systems is layered composition: use RBAC or ReBAC to define resource boundaries, supplement with ABAC for contextual conditions, and then use an intent layer for dynamic narrowing
50%