Certification
CHERI Enabled certification is a scoped, evidence-led review for a specific product, with published answers and periodic reassessment.
Certification turns a general CHERI claim into a reviewable record. The applicant defines the product and version, answers the programme questionnaire, supplies supporting evidence, and discusses the submission with the Alliance review team.
Application path
- Read the current certification programme and confirm that the product is in scope.
- Define the exact product, version, configuration, and relationship to any previously certified product.
- Complete the technical questionnaire with links or attachments for each claim.
- Respond to review questions and take part in interviews.
- If approved, follow the trademark conditions and keep the published record accurate.
- Seek reassessment when the product or programme changes and at the programme’s expected two-year review point.
First applications receive a full assessment. Reassessment may be simpler for an updated product, a derivative, or a later programme version, but the applicant must still identify what changed.
Prepare useful evidence
Answer from the implementation, not from a generic description of CHERI. Provide architecture versions, verification and test results, memory-access exceptions, tag handling, temporal-safety mechanisms, debug behaviour, compiler support, and integration assumptions. State where evidence is private and what can be published.
Interpret the result correctly
The scheme reviews the applicant’s evidence and use of CHERI principles. The Alliance currently does not perform independent product testing. Certification is not a guarantee of overall product security and does not replace sector certification, penetration testing, or an integrator’s assurance work.
Current requirements, fees, forms, and process details can change. Use the canonical CHERI Enabled programme page when preparing an application, and contact the Alliance if the product does not fit the published route.