The bibliographic entry was discovered and compiled by a machine, and published without a person checking it against the publication. The publication itself is the authors' own work — this badge says nothing about it.

Capability Hardware Enhanced RISC Instructions: CHERI Instruction-Set Architecture (Version 7)

Where it appeared

Published inCL Technical Reports

Identifiers

DOI10.48456/tr-927
OpenAlexW7213316036

From OpenAlex, which stores abstracts as an index of words and their positions: what is shown is rebuilt from that, and reads fluently whether or not it is what the author wrote.

Abstract

This technical report describes CHERI ISAv7, the seventh version of the Capability Hardware Enhanced RISC Instructions (CHERI) Instruction-Set Architecture (ISA) being developed by SRI International and the University of Cambridge. This design captures nine years of research, development, experimentation, refinement, formal analysis, and validation through hardware and software implementation. CHERI ISAv7 is a substantial enhancement to prior ISA versions. We differentiate an architecture-neutral protection model vs. architecture-specific instantiations in 64-bit MIPS, 64-bit RISC-V, and x86-64. We have defined a new CHERI Concentrate compression model. CHERI-RISC-V is more substantially elaborated. A new compartment-ID register assists in resisting microarchitectural side-channel attacks. Experimental features include linear capabilities, capability coloring, temporal memory safety, and 64-bit capabilities for 32-bit architectures. CHERI is a hybrid capability-system architecture that adds new capability-system primitives to commodity 64-bit RISC ISAs, enabling software to efficiently implement fine-grained memory protection and scalable software compartmentalization. Design goals include incremental adoptability within current ISAs and software stacks, low performance overhead for memory protection, significant performance improvements for software compartmentalization, formal grounding, and programmer-friendly underpinnings. We have focused on providing strong, non-probabilistic, efficient architectural foundations for the principles of least privilege and intentional use in the execution of software at multiple levels of abstraction, preventing and mitigating vulnerabilities. The CHERI system architecture purposefully addresses known performance and robustness gaps in commodity ISAs that hinder the adoption of more secure programming models centered around the principle of least privilege. To this end, CHERI blends traditional paged virtual memory with an in-address-space capability model that includes capability registers, capability instructions, and tagged memory. CHERI builds on the C-language fat-pointer literature: its capabilities can describe fine-grained regions of memory, and can be substituted for data or code pointers in generated code, protecting data and also improving control-flow robustness. Strong capability integrity and monotonicity properties allow the CHERI model to express a variety of protection properties, from enforcing valid C-language pointer provenance and bounds checking to implementing the isolation and controlled communication structures required for software compartmentalization. CHERI’s hybrid capability-system approach, inspired by the Capsicum security model, allows incremental adoption of capability-oriented design: software implementations that are more robust and resilient can be deployed where they are most needed, while leaving less critical software largely unmodified, but nevertheless suitably constrained to be incapable of having adverse effects. Potential deployment scenarios include low-level software Trusted Computing Bases (TCBs) such as separation kernels, hypervisors, and operating-system kernels, as well as userspace TCBs such as language runtimes and web browsers. We also see potential early-use scenarios around particularly high-risk software libraries (such as data compression, protocol parsing, and image processing), which are concentrations of both complex and historically vulnerability-prone code exposed to untrustworthy data sources, while leaving containing applications unchanged.

How it got here

How it got hereagent via openalex
Added2026-10-25 21:14 UTC
Not denied bya person 2026-10-29 17:12 UTC

Cite it as

@techreport{watson2019capability,
  title        = {Capability Hardware Enhanced RISC Instructions: CHERI Instruction-Set Architecture (Version 7)},
  author       = {Robert N. M. Watson and Peter G. Neumann and Jonathan Woodruff and Michael Roe and Hesham Almatary and Jonathan Anderson and John Baldwin and David Chisnall and Brooks Davis and Nathaniel Wesley Filardo and Alexandre Joannou and Ben Laurie and A. Theodore Markettos and Simon W. Moore and Steven J. Murdoch and Kyndylan Nienhuis and Robert Norton and Alexander Richardson and Peter Rugg and Peter Sewell and Stacey Son and Hongyan Xia},
  year         = {2019},
  journal      = {CL Technical Reports},
  doi          = {10.48456/tr-927},
}

This record lives at https://refs.drheap.org/watson2019capability/ and will keep doing so. It used to be called watson2021capabilityc, and those addresses still resolve to this one.