Business & Policy
Case studies
A useful CHERI case study explains a real system boundary, the baseline architecture, the change made, the evidence collected and the limitations of the result.
Why it matters
Case studies reduce uncertainty when the reader can compare workloads, software dependencies, maturity and assurance needs with their own product.
In brief
A useful CHERI case study explains a real system boundary, the baseline architecture, the change made, the evidence collected and the limitations of the result. It helps another organisation judge transferability rather than simply presenting a success story.
Key considerations
1. Context
Name the sector, product type, architecture, software stack, threat model and reason CHERI was evaluated.
2. Intervention
Describe the platform, ABI, porting work, compartment design and engineering resources used.
3. Result
Report security findings, performance, compatibility, effort and unresolved risks with measurement methods and dates.
Evidence and caveats
A demonstrator proves what happened in that configuration. It does not establish commercial readiness, fleet-wide savings or the same outcome for a different workload.
Show assumptions, ranges, dates and owners for economic or policy claims. Recheck legislation, guidance, product status and prices at the decision date.