The Zanzibar paper describes its own ancestry in §5 Related Work. It cites Multics, UNIX, POSIX ACLs, VMS and Taos for the data model; RBAC for roles; the IAM systems of Amazon, Google and Microsoft for the idea of one ACL store behind an RPC API; Facebook’s TAO as a system of similar scale; and Lamport clocks, Spanner, Chubby and ZooKeeper for the consistency question. This page follows the same threads in time order.
How the ideas lead to Zanzibar
The first multi-user systems had to decide who could touch what. In 1966 Dennis and Van Horn gave each computation a list of capabilities, unforgeable tokens that name an object and grant rights to it (Dennis and Van Horn). Lampson’s 1971 access matrix showed that capabilities and access control lists are two ways of storing the same table, by row or by column (Lampson). Multics took the column view: every segment and directory carried an ACL (Saltzer). Zanzibar is on the ACL side too: it answers “who can touch this object?”.
Operating systems then made the lists cheaper and coarser, and later richer again. The paper traces this itself: in the first edition of UNIX, file flags say “whether owner and non-owner can read or write the file”; by the fourth edition there are read, write and execute bits “for owner, group, and others”; POSIX ACLs add “an arbitrary list of users and groups”; VMS “supports ACL inheritance for files created within a directory tree” (§5). Those four words, permissions, users, groups and inheritance, are what Zanzibar’s data model sets out to support.
From the 1970s, models moved away from per-object lists. Bell–LaPadula and Biba let the system, not the owner, decide by labels; Zanzibar is discretionary, so they are contrast rather than ancestry. Role-based access control (1992) put roles between users and permissions; the paper says roles “are similar to Zanzibar relations” (§5). Attribute-based control, defined in NIST’s 2014 guide SP 800-162, computes decisions from attributes at request time. Relationship-based control, named by Gates in 2007 and formalised by Fong in 2011, decides from relationships such as “member of” or “parent folder of”, which compose (Fong). The paper never uses the word ReBAC, but its relation tuples are such a graph.
What was new at Google was scale and consistency. The paper says Zanzibar “has been in production use for more than 5 years” (§4) as of the July 2019 paper, so it was running by 2014 at the latest; no public source gives a start year. It serves Calendar, Cloud, Drive, Maps, Photos and YouTube (§1). TAO, which the paper compares it with, offers “eventual global consistency”, while Zanzibar provides “external consistency and snapshot reads with bounded staleness” so that it protects against the “new enemy” problem (§5). Lamport clocks were ruled out because they “require explicit participation of all “processes””, and some of Zanzibar’s are “external clients or even human users”. Chubby does not support “high volumes of data, efficient range reads, or reads at a client-specified snapshot with bounded staleness”, and ZooKeeper offers neither external consistency across nodes nor bounded-staleness snapshot reads (§5). Spanner and its TrueTime clock supplied the guarantee (Spanner, OSDI ’12).
After the paper, others rebuilt the design in the open. Ory Keto was rewritten around it in 2021, and SpiceDB, OpenFGA, Permify and Topaz followed within about eighteen months. At the same time policy engines in the ABAC line, OPA and Cedar, matured, and the OpenID Foundation’s AuthZEN working group, formed in 2023, standardised how an application asks an authorization engine for a decision: its Authorization API 1.0 became an OpenID Final Specification in January 2026. The details of each system are on the ecosystem pages.
Timeline
Operating systems
- 1966
Capability lists
Dennis and Van Horn describe a computation's "sphere of protection" as its list of capabilities, the C-list. Capabilities answer "what can this subject touch?".
Source - 1971
UNIX First Edition: owner and non-owner bits
chmod has six mode bits: read and write for owner and for non-owner, executable, set-user-ID. No group class. (Date from an archive copy; the original manual was not checked.)
Source - 1973
UNIX Fourth Edition: group bits
The chmod page dated 8/5/73 adds set-group-ID and read, write, execute bits for owner, group and others.
Source - 1973–1974
Multics ACLs, described by Saltzer
An ACL on every segment and directory. Presented at SOSP in October 1973, published in CACM in July 1974; Multics itself ran earlier. Zanzibar reference [23].
Source - 1997–1998
POSIX.1e ACLs: draft 17, then withdrawn
Draft 17 (October 1997) became the basis of Linux ACLs; sponsorship for 1003.1e was withdrawn in January 1998.
Source
Models and standards
- 1971
Lampson, "Protection": the access matrix
Rows are domains (subjects), columns are objects, cells are access attributes. An ACL is one column, attached to the object; capabilities are a domain's entries.
Source - 1973
Bell–LaPadula
Mandatory confidentiality: no read up, no write down. MITRE MTR-2547 Vol. I (March 1973); the *-property (no write down) arrives in Vol. II (May 1973). Cited from Bell's own retrospective.
Source - 1975–1977
Biba integrity model
The integrity dual of Bell–LaPadula. MITRE MTR-3153 (June 1975); the revised report, MTR-3153 Rev. 1, was issued as ESD-TR-76-372 in April 1977 (DTIC AD-A039324).
Source - 1992
Role-based access control
Ferraiolo and Kuhn, 15th National Computer Security Conference. Zanzibar reference [17].
Source - 1996
- 2003
XACML 1.0, OASIS Standard
An XML policy language that separates the enforcement point from the decision point. The exact approval day in February 2003 varies by source.
Source - 2004
ANSI INCITS 359-2004 (RBAC)
The unified NIST RBAC model becomes an ANSI standard on 11 February 2004; revised as INCITS 359-2012.
Source - 2007
"Relationship-Based Access Control" coined
Carrie Gates, W2SP 2007, as credited in Fong's 2011 paper (abstract and reference [18]). Gates's paper itself was not checked.
Source - 2011
Fong: a ReBAC protection model
Decisions based on the relationship between owner and accessor in a social network; relations compose, unlike roles.
Source - 2013
- 2014
NIST SP 800-162 (ABAC)
Attribute-based access control defined; published January 2014, updated 2 August 2019.
Source
Planet scale
- 2012
Spanner
Google's globally distributed database, with TrueTime and external consistency. Zanzibar stores its tuples in it (reference [15]).
Source - by 2014
Zanzibar in production
The paper says it "has been in production use for more than 5 years" (§4). That puts the start before mid-2014; no public source gives the year.
Source - 2019
The Zanzibar paper, USENIX ATC '19
Pang et al., presented in Renton, WA, in July 2019. The paper this site translates.
Source
Open source and standards
- 2016
Open Policy Agent v0.1.0
A general-purpose policy engine with the Rego language; first GitHub release on 14 July 2016.
Source - 2021
- 2021
- 2021
- 2022
OpenFGA first release
10 June 2022. Developed by Okta employees; a CNCF Incubating project since 28 October 2025, announced in the CNCF blog on 11 November 2025.
Source - 2022
- 2022
- 2023
- 2023
Amazon Verified Permissions GA
A managed service that evaluates Cedar policies, generally available on 13 June 2023.
Source - 2023
OpenID AuthZEN working group
Announced 20 October 2023, to define "standard mechanisms, protocols and formats for communication between authorization components".
Source - 2026
AuthZEN Authorization API 1.0 Final
Approved as an OpenID Final Specification, announced 12 January 2026 (81 approve, 1 object, 25 abstain). The API lets policy enforcement points (PEPs) ask policy decision points (PDPs) for decisions.
Source
What Zanzibar took from where
The paper is careful about the difference between building on something and resembling it. It runs on Spanner and Leopard; it supports the features of earlier ACL systems; and it calls RBAC roles similar to its relations and the “blessings” of Abadi et al. similar to its tuples (§5).
Which earlier work shows up in which part of Zanzibar?
Notice the split. The data model on the top half is a recombination of old ideas; the paper’s own claim is the unification, modelling with tuples “allows us to unify the concepts of ACLs and groups” (§2.1), where Abadi et al. kept them separate (§5). The bottom half is what made it work at Google’s scale: Spanner for “external consistency and snapshot reads with bounded staleness” (§5), and Leopard, “an indexing system used to optimize operations on large and deeply nested sets” (§3), for groups that pointer chasing cannot serve fast enough (§3.2.4).
Sources
- Ruoming Pang et al., “Zanzibar: Google’s Consistent, Global Authorization System”, USENIX ATC ’19, usenix.org/conference/atc19/presentation/pang
- J. B. Dennis and E. C. Van Horn, “Programming Semantics for Multiprogrammed Computations”, CACM 9(3), 1966, doi.org/10.1145/365230.365252; earlier version MIT Project MAC TR-23, December 1965, dspace.mit.edu
- B. W. Lampson, “Protection”, 1971; reprinted in ACM SIGOPS OSR 8(1), 1974, PDF
- UNIX First Edition sys-chmod(2), archive copy, man.cat-v.org/unix-1st/2/sys-chmod
- UNIX Fourth Edition chmod(2), Unix history repository, github.com/dspinellis/unix-history-repo
- J. H. Saltzer, “Protection and the Control of Information Sharing in Multics”, CACM 17(7), 1974, dl.acm.org/doi/10.1145/361011.361067
- A. Grünbacher, “POSIX Access Control Lists on Linux”, USENIX ATC 2003 FREENIX, usenix.org
- D. E. Bell, “Looking Back at the Bell-La Padula Model”, ACSAC 2005, PDF
- K. J. Biba, “Integrity Considerations for Secure Computer Systems”, MTR-3153 Rev. 1 / ESD-TR-76-372, April 1977, DTIC AD-A039324
- UC Davis Computer Security Lab history archive (Biba), seclab.cs.ucdavis.edu/projects/history/CD
- NIST, Role Based Access Control project, csrc.nist.gov/projects/role-based-access-control
- OASIS, XACML 3.0 core specification, docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html
- NIST SP 800-162, csrc.nist.gov/pubs/sp/800/162/upd2/final
- P. W. L. Fong, “Relationship-Based Access Control: Protection Model and Policy Language”, CODASPY ’11, dl.acm.org/doi/10.1145/1943513.1943539, PDF
- J. C. Corbett et al., “Spanner: Google’s Globally-Distributed Database”, OSDI ’12, PDF
- Open Policy Agent releases, github.com/open-policy-agent/opa/releases; CNCF graduation announcement, cncf.io
- Ory Keto v0.6.0-alpha.1, github.com/ory/keto/releases/tag/v0.6.0-alpha.1
- SpiceDB, github.com/authzed/spicedb
- OpenFGA, github.com/openfga/openfga
- Permify, github.com/Permify/permify
- Topaz, github.com/aserto-dev/topaz
- AWS, Cedar open-source announcement, aws.amazon.com; Amazon Verified Permissions GA, aws.amazon.com
- CNCF, OpenFGA becomes a CNCF incubating project, 11 November 2025, cncf.io
- OpenID Foundation, AuthZEN working group announcement, openid.net/announcing-authzen-working-group; Authorization API 1.0 Final, openid.net/authorization-api-1-0-final-specification-approved; the specification, openid.net/specs/authorization-api-1_0.html