Why CHERI
Frequently asked questions
CHERI adds protected capabilities to processor architectures so hardware can check pointer validity, bounds and permissions and support fine-grained compartments.
Why it matters
The most common questions concern compatibility, Rust, performance, platform availability and the security outcomes CHERI can legitimately support.
In brief
CHERI adds protected capabilities to processor architectures so hardware can check pointer validity, bounds and permissions and support fine-grained compartments. It is a defence-in-depth technology for memory access and authority, not a claim that software will contain no bugs.
Key considerations
1. Will existing code run?
Much C and C++ source can be adapted and recompiled, but ABIs, dependencies and unsafe assumptions require testing and sometimes changes.
2. Does it replace Rust?
No. Memory-safe languages prevent errors; CHERI adds hardware enforcement across mixed and legacy systems.
3. Is it available?
Research, development and commercial options exist across several platform classes; verify the exact current product and software status.
Evidence and caveats
Short answers omit architecture and implementation detail. Follow the linked pages before making a technical or procurement decision.
Use evidence from a named system or source and keep claims proportionate. CHERI is one layer in a broader secure-design strategy.