Capability-based security enables the concise composition of powerful patterns of cooperation without vulnerability.
In 3 minutes:
In 15 minutes:
Or for a detailed explanation: What Are Capabilities? 2017 by Morningstar.
JavaScript
SES is "hardened JavaScript. SES stands for fearless cooperation. ... SES safely executes third-party JavaScript 'strict' mode programs in compartments that have no excess authority in their global scope. SES runs atop an ES6-compliant platform, enabling safe interaction of mutually-suspicious code, using object-capability-style programming. See https://github.com/Agoric/Jessie to see how SES fits into the various flavors of confined JavaScript execution. And visit https://ses-demo.agoric.app/demos/ for a demo. "
6190052
9385d44
Capper is a web application server built on Node.js/Express using the Waterken webkey protocol for object capability security.
LavaMoat/LavaMoat: tools for sandboxing your dependency graph
cloudflare/workerd: The JavaScript / Wasm runtime that powers Cloudflare Workers
C++
Scheme (racket)
COAST is COmputAtional State Transfer, An Architectural Style for Secure Decentralized Systems. The sole means of interaction among computations is the asynchronous messaging. Motile is a single-assignment, functional, and mobile code language based on Scheme
Shill: Shill is a shell scripting language designed to make it easy to follow the Principle of Least Privilege. It runs on FreeBSD and is developed in Racket.
Scala
rust
go
python
nim
Pony is an open-source, object-oriented, actor-model, capabilities-secure, high performance programming language.
Austral - a systems language with linear types and capability security
Newspeak is an object-capability programming platform that lets you develop code in your web browser. Like Self, Newspeak is message-based; all names are dynamically bound. However, like Smalltalk, Newspeak uses classes rather than prototypes. The current version of Newspeak runs on top of WASM.
Monte is a nascent dynamic programming language reminiscent of Python and E. It is based upon The Principle of Least Authority (POLA), which governs interactions between objects, and a capability-based object model, which grants certain essential safety guarantees to all objects.
Cadence is a smart contract language with resources (linear types) and capability security. Its static type system has direct support for object-capability security. For example, the facade pattern is natively supported, and the type system has special down-casting rules to express access control patterns.
genode is a novel OS architecture that is able to master the complexity of code and policy -- the most fundamental security problem shared by modern general-purpose operating systems -- by applying a strict organizational structure to all software components including device drivers, system services, and applications.
we’re collaborating with Genode Labs to ship Genode for Reform.
Most of the many improvements of version 17.11 are geared towards the practical use of Genode as day-to-day OS. They include a reworked GUI stack, new user-input features, and the packaging of many components. The new version also revises the boot concept on x86, updates the seL4 kernel, and enhances Genode's user-level networking facilities.
Fuchsia is a real-time operating system in development by Google since Aug 2016. It's based on a microkernel, Zircon, with a capability security model.
seL4 is the world's first operating-system kernel with an end-to-end proof of implementation correctness and security enforcement; it is available as open source.
fc25cae
Integrate WasmEdge with seL4Abstract. We prove the enforcement of two high-level access control properties in the seL4 microkernel: integrity and authority confinement. Integrity provides an upper bound on write operations. Authority con- finement provides an upper bound on how authority may change. Apart from being a desirable security property in its own right, integrity can be used as a general framing property for the verification of user-level system composition. The proof is machine checked in Isabelle/HOL and the results hold via refinement for the C implementation of the kernel.
Capsicum Capsicum is a lightweight OS capability and sandbox framework that extends the POSIX API, providing several new OS primitives to support object-capability security on UNIX-like operating systems
2019-10 Capsicum Update 2019 by Mariusz Zaborski in FreeBSD Journal: Security
2017-07-19 Capsicum Go support Ben Laurie
Watson, R. N. M. 2013 Capsicum year in review. Light Blue Touchpaper, 20 December, 2013. Robert Watson reviews Capsicum events from 2013: work funded by the FreeBSD Foundation and Google on FreeBSD 10.0, Casper in FreeBSD 11, David Drysdale's port of Capsicum to Linux at Google, Summer of Code students, joint work with the University of Wisconsin on Capsicum, and future funded Capsicum work.
KataOS - embeded platform that runs on top of seL4
CHERI (Capability Hardware Enhanced RISC Instructions) extends conventional processor Instruction-Set Architectures (ISAs) with architectural capabilities to enable fine-grained memory protection and highly scalable software compartmentalization. CHERI’s hybrid capability-system approach allows architectural capabilities to be integrated cleanly with contemporary RISC architectures and microarchitectures, as well as with MMU-based C/C++- language software stacks.
CHERI’s capabilities are unforgeable tokens of authority, which can be used to implement both explicit pointers (those declared in the language) and implied pointers (those used by the runtime and generated code) in C and C++. When used for C/C++ memory protection, CHERI directly mitigates a broad range of known vulnerability types and exploit techniques. Support for more scalable software compartmentalization facilitates software mitigation techniques such as sandboxing, which also defend against future (currently unknown) vulnerability classes and exploit techniques.
We have developed, evaluated, and demonstrated this approach through hardware-software prototypes, including multiple CPU prototypes, and a full software stack. This stack includes an adapted version of the Clang/LLVM compiler suite with support for capability-based C/C++, and a full UNIX-style OS (CheriBSD, based on FreeBSD) implementing spatial, referential, and (currently for userspace) non-stack temporal memory safety. Formal modeling and verification allow us to make strong claims about the security properties of CHERI-enabled architectures.
This report is a high-level introduction to CHERI. The report describes our architectural approach, CHERI’s key microarchitectural implications, our approach to formal modeling and proof, the CHERI software model, our software-stack prototypes, further reading, and potential areas of future research.
2021-05: Attested TEEs for Transactional Workloads :: Sid Hussmann PADSEC 2021. We present a generic TEE toolkit applicable for many use-cases in finance, healthcare, and government. Gapfruit TEE embodies a microkernel operating system with capability-based security.
2020-12: Navigating the Attack Surface to achieve a *multiplicative* reduction in risk Mark Miller. 15min
2019-12: Making 'npm install' Safe - QCon New York "Kate Sills on security issues using NPM packages, the EventStream incident, and SES" as possible solutions to npm supply-chain risks.
2019-06: Higher-order Smart Contracts across Chains Agoric + Protocol Labs // - Mark Miller
2019-02-28: Delegation: The Missing Piece of Authorization talk by Tristan Slominski at the Austin Node.js meetup
2018-10: Opening Statement on SOSP 50th Anniversary Panel Mark Miller
2017-02: Designing with Capabilities - Scott Wlaschin at Domain-Driven Design Europe Conference
2016-06 Learn Object Capabilities by Douglas Crockford, part of Good Parts of JavaScript and the Web. Using the principle of least authority, Doug explains how the “actor model” can be applied to object oriented programming to create more secure software. He calls this application Object Capabilities.
CloudABI - Pure capability-based security for UNIX
Ed Schouten, 32nd Chaos Communication Congress (32C3), Dec 2015
Secure Distributed Programming with Object-capabilities in JavaScript
2012-03: Belay Demo 5min. Mark Lentczner, Security Team, Google
Passwords or Webkeys: Which is More Secure?
video by Marc Stiegler Feb 2012
Barth, Adam, Joel Weinberger, and Dawn Song.
Cross-Origin JavaScript Capability Leaks: Detection, Exploitation, and Defense. USENIX
security symposium. 2009.
Sargent, Will Security in Scala: Refined Types and Object Capabilities Scaladays NYC 2018.
2010-03 The Lazy Programmer's Guide to Secure Computing Google TechTalk by Marc Stiegler
2007-08 From Desktops to Donuts: Object-Caps Across Scales Google TechTalk by Marc Stiegler
2004 A PictureBook of Secure Cooperation Marc Stiegler
2002-05 Immunity from Viruses, Safety from Geeks Bearing Gifts Mark S. Miller
"This talk is centered on a demo of CapDesk, our capability-based distributed desktop and application installation/launching framework. CapDesk uses no passwords, no user group lists, no firewalls, yet supplies a computing world invulnerable to viruses and Trojan horses."
2018-11 POLA Would Have Prevented the Event-Stream Incident
Kate Sills, Agoric
2017-06 Capability-Based Network Communication for Capsicum/CloudABI April–June 2017 FreeBSD status report.
2017-05 What Are Capabilities?
by Chip Morningstar (Hacker News discussion Jan 7, 2018)
2016-08 Welcoming all Python enthusiasts: CPython 3.6 for CloudABI! August 1, 2016 by Ed Schouten
2015-11 Objects as Secure Capabilities Joe Duffy
2009-03 Not One Click for Security Karp, Alan H.; Stiegler, Marc; Close, Tyler, HP Laboratories, HPL-2009-53 Conventional wisdom holds that security must negatively affect usability. We have developed SCoopFS (Simple Cooperative File Sharing) as a demonstration that need not be so. SCoopFS addresses the problem of sharing files, both with others and with ourselves across machines. Although SCoopFS provides server authentication, client authorization, and end-to-end encryption, the user never sees any of that. The user interface and underlying infrastructure are designed so that normal user acts of designation provide all the information needed to make the desired security decisions. While SCoopFS is a useful tool, it may be more important as a demonstration of the usability that comes from designing the infrastructure and user interaction together.
2009-02 ACLs don't Tyler Close, HP Laboratories The ACL model is unable to make correct access decisions for interactions involving more than two principals, since required information is not retained across message sends. Though this deficiency has long been documented in the published literature, it is not widely understood. This logic error in the ACL model is exploited by both the clickjacking and Cross-Site Request Forgery attacks that affect many Web applications
See also Usable Security and Capabilities bibliography.
D. Devriese, Birkedal, and Piessens
Reasoning about Object Capabilities with Logical Relations and Effect Parametricity
1st IEEE European Symposium on Security and Privacy, Congress Center Saar, Saarbrücken, GERMANY, 2016.
Gerwin Klein, June Andronick, Kevin Elphinstone, Toby Murray, Thomas Sewell, Rafal Kolanski and Gernot Heiser
Comprehensive formal verification of an OS microkernel
ACM Transactions on Computer Systems, Volume 32, Number 1, pp. 2:1-2:70, February, 2014
S. Clebsch and S. Drossopoulou
Fully concurrent garbage collection of actors on many-core machines
OOPSLA 2013
Mark S. Miller, Tom Van Cutsem, Bill Tulloh
Distributed Electronic Rights in JavaScript
ESOP'13 22nd European Symposium on Programming, Springer (2013)
Maffeis, Sergio, John C. Mitchell, and Ankur Taly. Object capabilities and isolation of untrusted web applications. In 2010 IEEE Symposium on Security and Privacy, pp. 125-140. IEEE, 2010.
Barth, Adam, Joel Weinberger, and Dawn Song.
Cross-Origin JavaScript Capability Leaks: Detection, Exploitation, and Defense. USENIX
security symposium. 2009.
Close, T.: Web-key: Mashing with permission. In: W2SP’08. (2008)
Miller MS
Robust composition: towards a unified approach to access control and concurrency control
Ph.D. Thesis, Johns Hopkins University; 2006.
When separately written programs are composed so that they may cooperate, they may instead destructively interfere in unanticipated ways. These hazards limit the scale and functionality of the software systems we can successfully compose. This dissertation presents a framework for enabling those interactions between components needed for the cooperation we intend, while minimizing the hazards of destructive interference.
Great progress on the composition problem has been made within the object paradigm, chiefly in the context of sequential, single-machine programming among benign components. We show how to extend this success to support robust composition of concurrent and potentially malicious components distributed over potentially malicious machines. We present E, a distributed, persistent, secure programming language, and CapDesk, a virus-safe desktop built in E, as embodiments of the techniques we explain.
Miller, Mark S., E. Dean Tribble, and Jonathan Shapiro. Concurrency among strangers. TGC. Vol. 5. 2005.
Mark S. Miller, Chip Morningstar, Bill Frantz
Capability-based Financial Instruments
Proc. Financial Cryptography 2000, Springer-Verlag, Anguila, BWI,
pp. 349-378.
Every novel cooperative arrangement of mutually suspicious parties interacting electronically — every smart contract — effectively requires a new cryptographic protocol. However, if every new contract requires new cryptographic protocol design, our dreams of cryptographically enabled electronic commerce would be unreachable. Cryptographic protocol design is too hard and expensive, given our unlimited need for new contracts. Just as the digital logic gate abstraction allows digital circuit designers to create large analog circuits without doing analog circuit design, we present cryptographic capabilities as an abstraction allowing a similar economy of engineering effort in creating smart contracts. We explain the E system, which embodies these principles, and show a covered-call-option as a smart contract written in a simple security formalism independent of cryptography, but automatically implemented as a cryptographic protocol coordinating five mutually suspicious parties