Guides
Background for reading the paper: the access-control models it builds on, the history behind it, and its mechanisms drawn step by step.
Background
- ACL, RBAC, ABAC, ReBAC: four ways to say who may do whatOne access decision, "can Chen view doc:readme?", modelled as an access control list, as roles, as attribute rules and as a relationship graph, and where Zanzibar sits among them.
- From Multics to ZanzibarSixty years of access control, from capability lists and Multics ACLs through RBAC and ABAC to Zanzibar and the open-source systems that followed it, each step with its primary source.
How the paper works
- Relation tuples and usersetsHow Zanzibar stores every permission as a small fact, how a namespace config turns those facts into effective ACLs, and how Check walks the result as a graph.
- Consistency, snapshots and zookiesWhy an authorization system has to respect the order of ACL and content changes, and how Zanzibar does it with Spanner timestamps and zookies.
- Architecture, from one Check to SpannerThe servers and databases behind Zanzibar, followed through a single Check request and the Watch stream.
- Inside one CheckHow Zanzibar turns one Check into a tree of sub-problems, evaluates the leaves at the same time, stops early, caches what it learned at a snapshot, and what products add that the paper leaves out, such as depth limits.
- Leopard, the group indexHow Zanzibar answers membership in deeply nested groups with one set intersection, and what that costs on every write.
Applying it
- Listing what a user can seeWhy "every document Anne can see" is a different question from Check, what the paper offers for it, and the three approaches used in practice.
- Keeping tuples in step with your dataWhy the paper never discusses dual writes, what goes wrong when an application database and an authorization service disagree, and the patterns used to keep them in step.
- Modeling patterns: from rewrite rules to real permissionsEight common authorization requirements, each written as tuples, as a rule in the paper's namespace-config notation where it can be, and in SpiceDB's and OpenFGA's schema languages.
- When relationships are not enoughWhat the paper's tuples cannot express (time, network, amounts, expiry), and how SpiceDB caveats, OpenFGA conditions and contextual tuples, and Permify attributes add it back.
- Ordering without TrueTimeWhat a zookie needs from the database underneath, how Zanzibar-style products get it from CockroachDB, PostgreSQL, MySQL and Spanner, and what happens when nothing provides it.
- Changing and testing a schemaHow the paper keeps namespace config changes consistent inside one request, why removing a relation takes three steps in today's products, and how to test a model with assertion files in CI.
- Do you need a Zanzibar?A role table in your own database, a policy engine such as OPA or Cedar, a Zanzibar-style service, or a mix, compared on the same requirements, with the published critiques and replies.
Reference
- Common misconceptionsTwelve things people often get wrong about Zanzibar, from "it does login" to "you need atomic clocks", each corrected with the paper section or a primary source.
- GlossaryEvery term a reader meets in the Zanzibar paper, in plain words, with a pointer to the guide page and the paper section that explain it.