Relationship-based access control grants access by evaluating paths through relationships between subjects, resources, and intermediary objects. It is useful when permissions depend on how things are connected rather than on simple roles alone, but its runtime cost depends heavily on graph shape and traversal strategy.
How ReBAC Works
Relationship-based access control decides access by following graph edges: who is connected to what, through which intermediaries, and along which permitted paths. That makes it a strong fit for organisations where access is shaped by ownership, membership, delegation, or hierarchy rather than by static roles alone.
In practice, ReBAC externalises authorisation logic into a relationship graph or policy engine, so the decision point can evaluate context at request time instead of relying on a simple role list. NHIMG’s Authorisation Models Guide compares RBAC, ABAC, ReBAC and policy-based access control for people, workloads and AI agents.
Why ReBAC Is Used
ReBAC is useful when access depends on business relationships that are too specific, dynamic, or nested for clean role design. Common examples include shared documents, tenant-scoped resources, delegated administration, partner access, and applications where the same user may gain access through different paths.
It also helps avoid role explosion and overbroad entitlements, because the policy can express “can access if connected through this relationship” instead of creating many narrow roles. For many teams, that makes access rules easier to reason about, audit, and evolve as the organisation changes.
Where ReBAC Becomes Hard
The main engineering challenge is that graph traversal cost can rise quickly as the relationship structure grows. Deep chains, high fan-out, cyclic relationships, and poorly bounded queries can make decisions slower and harder to predict, especially when every request must be authorised in real time.
ReBAC also depends on the correctness of relationship data. If tuples, memberships, ownership records, or delegated links drift out of date, the authorisation result can be technically consistent with the graph but operationally wrong for the business.
ReBAC in Modern Authorisation Architectures
ReBAC is often implemented through a centralised authorisation service, a policy engine, or a graph-backed permissions system. In those designs, the application asks a decision point to evaluate relationships instead of hard-coding the access logic in every service.
That approach is especially important when the same permission model must work across web apps, APIs, internal tools, and distributed services. The Fine-Grained Authorisation Guide covers Zanzibar-style relation tuples, schema design, consistency, and safe rollout patterns, while the Externalised Authorisation Buyer's Guide focuses on policy engine capabilities, AuthZEN support, and latency testing.
When teams need a broader foundation, NHIMG’s IAM and IGA Basics explains how access models, governance, provisioning, and reviews fit together across people and machines.
Risk and Threat Considerations
ReBAC can create a large blast radius if the relationship graph is wrong, too permissive, or too easy to traverse. Because access is inferred from connected entities, a single bad edge, inherited permission, or unsafe relationship chain can expose more resources than intended.
Failure mechanism: Attackers and insiders benefit when the graph contains stale links, overbroad delegation, or weakly constrained traversal rules, because those defects can turn an apparently precise model into unintended access at scale.
Impact: The result can be broken authorisation, privilege expansion, or exposure of sensitive data and administrative paths, especially in systems where relationship data is reused across many applications or tenants.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST Zero Trust (SP 800-207) and OWASP ASVS set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-3 — Access Enforcement | ReBAC is an access-enforcement model that decides who may reach resources. |
| AC-6 — Least Privilege | ReBAC is often used to reduce broad standing access and over-privilege. | |
| AU-2 — Event Logging | ReBAC decisions need auditability for access grants, denials, and traversal outcomes. | |
| Recommendation — Apply AC-3 to enforce relationship-based decisions consistently at the authorization point. Use AC-6 to keep relationship grants narrowly scoped to the minimum needed access. Log authorization decisions and relationship changes so access paths can be reviewed later. | ||
| NIST Zero Trust (SP 800-207) | 3.2 — Policy Engine | ReBAC commonly relies on a policy engine to evaluate access dynamically. |
| Recommendation — Centralize relationship evaluation in the policy engine and keep applications out of the trust decision. | ||
| OWASP ASVS | V8 — Authorization | ReBAC is an authorization model for fine-grained access decisions in applications. |
| Recommendation — Verify that authorization rules are enforced server-side and cannot be bypassed by the client. | ||
Practitioner Guidance
What to watch for: Treat ReBAC as an authorisation system with real operational dependencies, not just a modelling exercise. The important question is whether relationship data, traversal depth, and consistency semantics are good enough to support the access decisions your applications actually make.
Practitioner takeaway: ReBAC works best when relationship schemas stay intentionally small, decision latency is measured under realistic graph shapes, and governance exists for who can create or change relationships.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org