← Graph

Fine-Grained Authorization

concept 9 connections

Fine-Grained Authorization (FGA), also called Relationship-Based Access Control (ReBAC). Based on Google's Zanzibar paper. Authorization data is stored as tuples (subject, relation, object) — e.g. 'user A editor project X' — which form a graph whose nodes are entities and whose edges are relations. Permissions are then expressed as rules over this graph: checking a permission is equivalent to asking whether a path exists from the user to the resource under the given rules. Enables schema-level dependency analysis, id-only traversal (no intermediate object loading), result caching with dependency-aware invalidation, audit paths explaining why access was granted, and reverse lookups (list users with permission X on resource Y).

aliases
FGA; ReBAC; Relationship-Based Access Control
category
architecture
about
Fine-Grained Authorization concept
Central proposal of the talk: FGA / relationship-based access control.
Mid-step of the recommendation: introduce FGA.
about
Fine-Grained Authorization concept
Insight describes how FGA frames permission checks.
about
Fine-Grained Authorization concept
General property of FGA implementations.
about
Fine-Grained Authorization concept
About modeling special-case rules in an FGA schema.
about
Fine-Grained Authorization concept
About the operational cost of maintaining an FGA tuple store.
about
Fine-Grained Authorization concept
Discusses what ReBAC gives (and doesn't give) for collection filtering.
concept Fine-Grained Authorization
related_to
Google Zanzibar resource
FGA/ReBAC is based on the Google Zanzibar paper.
tool granity
related_to
Fine-Grained Authorization concept
granity implements FGA/ReBAC for Rails.

Provenance

Read by
1 extraction