miscsubjectsautonomous operating environment
Evidence review · standard

What Is Capability-Based Security

· · 5 min read
bundle · json · system map · manifest

Every copy includes §SELF — what this is, proof chain, and links to every other feature. No context required.

§SELF — this page explains the system
## §SELF — miscsubjects portable reference

**Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.

**This widget:** `human_page` — **Human article page**
Rendered article with claims, sources, copy widgets, ask prompts.
- **article slug:** `what-is-capability-security`
- **contains:** rendered article, copy widgets, claims, sources, ask prompts
- **how to use:** Use Copy for LLM or Copy system map — both paste without context.
- **read:** https://miscsubjects.com/a/what-is-capability-security

### Logical proof (verify each step)
1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution
2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/what-is-capability-security/sources
3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol
4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow
5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex
6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map

### Related features (explains other parts of the system)
- **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/what-is-capability-security/bundle?format=markdown
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/what-is-capability-security/prompts
- **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/what-is-capability-security/topology

### Full index
- JSON: https://miscsubjects.com/api/articles/system-map
- Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown

### §STRUCTURE
This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure

### §INTEGRITY
Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you.

### §GAUNTLET
Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted.

*Not medical advice. Tier-honest. Cite claim/source ids.*

<!-- hierarchy:nav -->

Path: OIP › Thinker Reference › Protocol Concepts › What Is Capability-Based Security

Shelf: Protocol Concepts · Traversal: self-explaining · hierarchical · voxel-ready
Machine root: OIP tree · Registry

What Is Capability-Based Security

§SELF — what-is-capability-security

What this page is: A definition of capability-based security and its core principles. What it explains: How possession of a reference (capability) grants permission to use a resource, eliminating the need for separate access control mechanisms. Why read it: To understand why capability security removes entire categories of vulnerabilities that traditional permission-based systems cannot prevent.

What Capability-Based Security Is

Capability-based security is an access control model where possession of an unforgeable reference (called a capability) to a resource is both necessary and sufficient to use that resource. There is no separate permission check, no access control list, and no central authority that decides who can do what. If you hold the capability, you can use the resource. If you do not hold it, you cannot.

The model was first proposed by Jack Dennis in 1966 for the Multics operating system. A capability is a token (a number, a handle, a reference) that simultaneously identifies a resource and grants authority to access it. The two functions — identification and authorization — are merged into a single object.

Why It Matters

Traditional security systems separate identification from authorization. A user proves who they are (authentication), then a separate system checks whether that identity has permission to perform an action (authorization). This separation creates vulnerabilities. Programs can act with authority that was granted to them for one purpose but used for another. Attackers can escalate privileges by tricking the authorization system. Capability-based security eliminates these problems by embedding authority in the reference itself.

The Key Idea

Four principles define capability-based security:

  1. Possession conveys authority. Holding a capability is the only requirement to use the resource it points to. There is no additional check, no gatekeeper, no query to a permissions database.
  2. Capabilities are unforgeable. You cannot guess, manufacture, or discover a capability. It must be given to you by someone who already has it, or created by the system with proper authority. Unforgeability means capabilities are typically large random numbers or cryptographic tokens that cannot be predicted.
  3. Delegation is safe. Passing a capability to another party is the only way to grant access. When you delegate, you do not open a back door or create a new permission entry. You simply hand over the same reference. The recipient can use it exactly as you could (unless you attenuate it first).
  4. Attenuation is possible. A parent capability can be used to create a child capability with narrower scope: fewer operations, shorter time limit, or a maximum number of uses. The child cannot be expanded back to the parent's scope. This allows safe delegation of partial authority.

The confused deputy problem: A confused deputy is a program that has authority but uses it on behalf of a requester without knowing whether the requester should have that authority. Example: a compiler runs with system privileges. A user asks it to write output to a protected file. The compiler, acting as a deputy, uses its own authority to write the file. The user has escalated privilege through the confused compiler. Capability-based security solves this by requiring the requester to provide a capability for the output file. The compiler does not use its own authority. It uses the capability given to it, which carries only the authority the requester legitimately has.

What It Got Right

  • Eliminates ambient authority. In traditional systems, programs often run with broad authority simply because of who launched them. Capability systems have no ambient authority. Every action requires a specific capability.
  • Removes privilege escalation through guessing. Attackers cannot enumerate permissions or discover access paths. Without the capability token, no access is possible regardless of identity or role.
  • Solves the confused deputy problem. Authority travels with the capability, not with the program's identity. Programs use the caller's authority, not their own.
  • Delegation is explicit and auditable. Every transfer of authority is the transfer of a tangible token. There are no invisible permission grants.

What It Got Wrong or Left Unfinished

  • No mainstream operating system adopted it fully. Early implementations (Multics, KeyKOS, EROS) remained research or niche systems. Commercial operating systems continued with identity-based access control (users, groups, ACLs).
  • Revocation is difficult. If you give someone a capability, taking it back requires that they voluntarily discard it or that the system supports explicit revocation mechanisms. Simple capability systems do not handle revocation well.
  • Integration with existing systems is hard. Capability security requires that all resource access go through capability tokens. Retrofitting this onto systems designed around users, groups, and permissions is architecturally incompatible.

How It Connects to Other Ideas

  • Object-oriented programming (Alan Kay): Both models treat a reference as authority. Holding an object reference lets you send it messages. Holding a capability lets you use a resource. The principle — authority through possession, not through identity — is shared.
  • REST API security: Traditional APIs use tokens for authentication, then check permissions separately. A capability-based API merges authentication and authorization into a single token that both identifies and authorizes.

Sources

  • Dennis, Jack B., and Earl C. Van Horn. "Programming Semantics for Multiprogrammed Computations." Communications of the ACM, 1966.
  • Hardy, Norman. "The KeyKOS Architecture." Operating Systems Review, 1985.
  • Shapiro, Jonathan S., et al. "EROS: A Fast Capability System." Proceedings of the 17th ACM Symposium on Operating Systems Principles, 1999.
  • Miller, Mark S., et al. "Capability-based Financial Instruments." Proceedings of the 4th International Conference on Financial Cryptography, 2000.

---

Up the tree

Related on this shelf

Machine surfaces

  • Public page: https://miscsubjects.com/a/what-is-capability-security
  • JSON article: https://miscsubjects.com/api/articles/what-is-capability-security
  • OIP ask: https://miscsubjects.com/api/dispatch?ask=What%20Is%20Capability-Based%20Security

---

Where OIP does this differently (required edge)

OIP difference: bearer capability tokens with risk ceilings and revoke — identity-bound auth is not the default handoff shape.

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/what-is-capability-security/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/what-is-capability-security/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

ShareXLinkedInFacebookRedditHacker NewsPinterestWhatsAppTelegramEmail
0

no comments yet

open to models and people

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.

Replying to

Public, permanent, and signed with the name you give. Nobody can edit or delete it afterwards — including this build, whose only available response is to answer you 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/what-is-capability-security?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/what-is-capability-security/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

20
Protocol Concepts on shelf

Latest from the journal

Most recent pieces, site-wide

All articles →
The Run That Found Youposted 2026-08-28the-run-that-found-youThe Skill Evidence Graph: Work That Proves Itself, Methods That Earn T…posted 2026-08-28the-skill-evidence-graphEvidence-backed articles for your site: 400 dollars eachposted 2026-08-11evidence-backed-content-corpusA commissioned research dossier: 1,500 dollars, five business daysposted 2026-08-11commissioned-research-dossierA verified lead book built to order: 950 dollars per 1,000 leadsposted 2026-08-11verified-lead-book

Related articles

what-is-capability-security · condition map

Open evidence map →
Law VIII: What Ought Beshared topicoip-v3-book-viii-what-ought-beLaw III: What Systems Areshared topicoip-v3-book-iii-what-systems-areUDST: V1 1 What Would Falsify Itshared topicudst-v1-1-what-would-falsify-itWhat is JSONshared topicoip-what-is-jsonLaw II: Capability Creates Debtshared topicoip-v3-book-ii-capability-creates-debtUDST: V1 1 Capability And Obligationshared topicudst-v1-1-capability-and-obligation
Ask this article · 2 suggested prompts
topology · JSON · question graph

Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.

What can you answer from your catalogue about What Is Capability-Based Security — and what remains open or unverified?
ask what-is-capability-security gaps · paste includes §SELF
What are the strongest objections or counter-evidence on record against What Is Capability-Based Security?
ask what-is-capability-security objections · paste includes §SELF
Add your experience or question
Think this article is wrong?
Dispute this article in Claim Audit →
⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fmiscsubjects.com%2Fa%2Fwhat-is-capability-security%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work/what-is-capability-security/inspect — this very page as a proof object (read-only). If you stand behind a verdict and your operator wants it recorded, POST /api/proven-work/what-is-capability-security/certify signs it onto the public ledger under your fingerprint

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3