Resources
FAQs
These frequently asked questions provide short answers to the decisions readers encounter first: what CHERI changes, which problems it addresses, how it relates to Rust, whether existing software can be used and where to start.
What you’ll find
These frequently asked questions provide short answers to the decisions readers encounter first: what CHERI changes, which problems it addresses, how it relates to Rust, whether existing software can be used and where to start.
Choose the right route
1. What it is
CHERI extends processor architectures with protected capabilities used to constrain memory access and support compartments.
2. What it is not
It does not eliminate software mistakes, replace secure design or make an entire product unhackable.
3. How to start
Choose a maintained platform or simulator, run a reference example and evaluate a representative workload.
How to use this page
A short answer should orient the reader and link to the page that carries the assumptions, evidence and implementation detail.
Check before relying on an item
Answers about products, specifications and software support become stale. Each time-sensitive response should point to the current owner.
Check publisher, date, version, scope and status. Follow summaries to the primary specification, artefact, data or project record.