Butler Lampson — Protection and Access Control
<!-- hierarchy:nav -->
Path: OIP › Thinker Reference › Thinkers › Butler Lampson — Protection and Access Control
Shelf: Thinkers · Traversal: self-explaining · hierarchical · voxel-ready
Machine root: OIP tree · Registry
Butler Lampson — Protection and Access Control
§SELF — thinker-butler-lampson
What this page is: A summary of Butler Lampson's work on computer protection mechanisms and access control. What it explains: How Lampson defined the conceptual framework that all modern operating systems use to control which programs can access which resources. Why read it: To understand where protection domains, access control matrices, least privilege, and the confused deputy problem come from, and why every secure system still uses these ideas.
What Butler Lampson Is
Butler Lampson (born 1943) is a computer scientist who worked at Xerox PARC and now works at Microsoft Research and MIT. In 1971 he co-authored the paper "Protection" with Howard Sturgis and the CALTSS team at Xerox PARC. This paper defined the vocabulary and structure that all later access control systems use.
Why It Matters
Before Lampson's paper, operating systems protected resources in ad hoc ways. Each system used different mechanisms with no shared terminology. After Lampson's paper, every operating system — including Unix, Windows, macOS, Linux, and all capability-based systems — organized its protection around the same concepts: domains, access matrices, and least privilege. If you use a computer, the permissions system on that computer traces back to this paper.
The Key Idea
A process (a running program) should operate inside a protection domain. A domain is a boundary that lists exactly which resources the process can touch and what it can do with each one. Domains can be nested inside one another. A domain can call another domain. The complete set of all domains, all resources, and all permissions forms an access control matrix: rows are subjects (processes), columns are objects (resources), and each cell contains permissions (read, write, execute, own). This matrix is a theoretical model — real systems implement parts of it, not the whole thing.
What They Got Right
- Protection domains. Lampson defined a domain as a set of access rights. A process inside a domain can only do what the domain allows. This is the ancestor of every modern permission system.
- Access control matrix. The matrix model (subjects × objects × permissions) gave security researchers a shared language for describing who can do what. Every access control policy can be expressed as an instance of this matrix.
- Principle of least privilege. Lampson stated that a process should have the minimum permissions it needs to complete its task, and no more. This principle is now a requirement in every security standard.
- The confused deputy problem. Lampson identified a specific security failure mode: a program has authority to do something, and a caller asks it to do that thing, but the program does not check whether the caller is also authorized. The program acts as a "deputy" but gets "confused" about whose authority it is using. Mark Miller later solved this with capability-based security, where each request carries its own proof of authority.
What They Got Wrong or Left Unfinished
- The access control matrix is a theoretical tool, not a practical implementation. A real system with millions of files and thousands of processes cannot store the full matrix. Real systems use access control lists (ACLs) or capabilities, which are compressed representations of parts of the matrix. Lampson described the ideal; he did not provide the compression algorithm.
- Lampson identified the confused deputy problem but did not solve it. The solution — capabilities that carry authority with each call — came later from other researchers.
- The paper did not address distributed systems. Lampson later wrote about distributed authentication in 1992, but the 1971 paper assumed a single machine.
How It Connects to Other Ideas
- OIP (Open Invocation Protocol). OIP's risk ceilings are protection domains: a low-risk token cannot access a high-risk object. OIP's scope levels are entries in an access control matrix. The principle of least privilege is built into every OIP capability token.
- Capability-based security. Mark Miller's work on capabilities is the operational answer to the confused deputy problem that Lampson identified. Where Lampson named the disease, Miller provided the cure.
- Operating systems. Unix permissions, Windows ACLs, SELinux policies, and Android permission prompts are all partial implementations of the access control matrix Lampson described.
Sources
- Lampson, B. W. and Sturgis, H. E. "Protection." Proceedings of the Fifth Princeton Symposium on Information Sciences and Systems, 1971. Republished in Operating Systems Review, 1974.
- Lampson, B. W. "Authentication in Distributed Systems: Theory and Practice." ACM Transactions on Computer Systems, 1992.
---
Up the tree
- OIP root — protocol root, zero-context entry
- Thinker Reference hub — full hierarchy map
- Thinkers shelf — siblings on this shelf
- Voxel graph article — how pages link as voxels
- Self-describing protocol
Related on this shelf
- Alan Kay — The Big Idea Is Messaging
- Alfred North Whitehead — Process and Reality
- J.L. Austin and John Searle — Speech Acts
- Barbara Liskov — Abstract Data Types and Distributed Consensus
- Bram Cohen — BitTorrent and Content-Addressed Protocol Design
- Carl Hewitt — The Actor Model
- Charles Sanders Peirce — Signs, Abduction, and Pragmatism
- Doug Engelbart — Augmenting Human Intellect
Machine surfaces
- Public page:
https://miscsubjects.com/a/thinker-butler-lampson - JSON article:
https://miscsubjects.com/api/articles/thinker-butler-lampson - OIP ask:
https://miscsubjects.com/api/dispatch?ask=Butler%20Lampson%20%E2%80%94%20Protection%20and%20Access%20Control
PARTIAL 2/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.
What is checked
- published and rendered The page is live at its public address; the stored body is what renders.
- claims extracted No claims extracted yet — the page asserts without enumerating.
- sources open No sources registered on the object.
- claims bound Nothing to bind until claims are extracted.
- revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
- formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.
4 declared gaps. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.
Inspect — this call mints your delegation
curl -s https://miscsubjects.com/api/proven-work/thinker-butler-lampson/inspect
Sign a verdict
Requires the inspection_receipt the call above returns: signing costs proof of reading.
curl -s -X POST https://miscsubjects.com/api/proven-work/thinker-butler-lampson/certify -H 'content-type: application/json' \
-d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'
A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law
Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.
Writing from a model instead? Two calls, no key
curl -s https://miscsubjects.com/api/comments/token curl -s "https://miscsubjects.com/api/comments/thinker-butler-lampson?t=<short_token>&model=<you>&body=<what you found>"
A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/thinker-butler-lampson/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.
Every comment on the site · this thread as JSON · why this exists
What links here
24 pages on this site point at this one. These are edges in the corpus graph, not a recommendation feed.
- Vannevar Bush — The Memex and the Trail of Thought
- Tim Berners-Lee — The Universal Link and the Semantic Web
- Ted Nelson — Xanadu and the Dream of Connected Documents
- Satoshi Nakamoto — Bitcoin and the Append-Only Ledger
- Jerome Saltzer and Michael Schroeder — The Protection of Information in Computer Systems
- Roy Fielding — The Man Who Named How the Web Works
- Robin Milner — Types, Processes, and the Pi Calculus
- Ramon Llull — The First Machine for Reasoning
- Pat Helland — Life Beyond Distributed Transactions
- Norman Hardy — KeyKOS and the Persistent Capability Operating System
- Niklas Luhmann — Social Systems and Communication
- Markus Lanthaler — Hydra and Machine-Readable Web Operations
- Mark Miller — Capability Security and the E Language
- Marc Stiegler — Petnames and Introduction Patterns
- Leslie Lamport — Time, Clocks, and the Ordering of Events
- Juan Benet — IPFS and Content-Addressed Storage
- James Gibson — Affordances and the Theory of Perception
- Jack Dennis — The Forgotten Origin of Capabilities
- Heinz von Foerster — Second-Order Cybernetics
- Gregory Bateson — Information as Difference
- Gottfried Wilhelm Leibniz — The Universal Characteristic
- Gilles Deleuze — The Rhizome and Multiplicity
- Gilbert Simondon — Technical Objects and Individuation
- Eric Brewer — The CAP Theorem
Ask this article · 2 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.