Business & Policy
Product-lifecycle benefits
CHERI can influence costs and risk across design, testing, incident response, maintenance and product retirement—not only block an invalid access at runtime.
Why it matters
Lifecycle value is greatest for products that run complex native code, remain deployed for years, accept untrusted input or are difficult to update.
In brief
CHERI’s potential benefits extend beyond blocking an invalid access at runtime. Earlier fault detection, clearer authority boundaries and stronger component isolation can change debugging, maintenance, assurance and incident impact over a product’s useful life.
Key considerations
1. Development
Capability-aware tools and faults can expose pointer and authority assumptions during porting and testing.
2. Operation
Hardware checks may prevent some invalid operations and compartments can restrict what a compromised component can reach.
3. Maintenance
Reduced exploitability and clearer boundaries may lower some response and assurance effort, while new platform and skills costs must still be carried.
Evidence and caveats
Benefits vary by software, ABI, compartment design and product operations. Measure them in a representative workload rather than assuming they follow from hardware presence.
Show assumptions, ranges, dates and owners for economic or policy claims. Recheck legislation, guidance, product status and prices at the decision date.