Contact the Alliance

Help us route your message

Use a clear subject and include the relevant detail:

• Membership: include the organisation, location, interest in CHERI, and intended participation.
• Working group: include the topic, relevant experience, and the contribution or question.
• CHERI Enabled: include the product name, version, organisation, and intended application timing.
• Events or speakers: include the audience, format, date, location, topic, and expected attendance.
• Media: include the publication, deadline, question, and requested spokesperson or area of expertise.
• Trademark or brand: include the mark, material, territory, intended use, and publication date.
• Technical resource: include the platform, software version, goal, and resources already consulted.

Do not send passwords, private keys, export-controlled material, vulnerability details, or other sensitive information in an initial general enquiry. Ask for an appropriate handling route first.

For a potential security vulnerability in a particular product or project, follow that vendor’s or project’s published security-reporting process. The Alliance does not maintain every CHERI implementation.

Policy documents and programme pages may already answer formal questions. Linking the page you consulted will help the team identify whether clarification or an update is needed.