GCRI · Cybersecurity and Digital Resilience
Events and technical dialogues
Confirmed events in Cybersecurity and Digital Resilience, each with its date, organiser, format and terms. Only scheduled, confirmed activities are listed.
Events and technical dialogues in four parts.
Events and technical dialogues in Cybersecurity and Digital Resilience.
- Each entry shows its scope, host or owner, and terms.
- Participation follows published rules, applied equally.
- Taking part gives no authority or influence over findings.
Technical dialogues that suit cyber questions.
Tabletop exercises on cyber incidents with physical consequences are the main event type, run with operators and authorities and recorded without attribution.
- Tabletop exercises on cyber-physical incidents.
- Dependency mapping workshops.
- Cryptographic migration clinics.
How the process runs.
Process
Events and technical dialogues: Convening from idea to record
A governed convening passes intake, design and public-safe review before moderation; its record is made, outputs are classified, and a competent actor decides.
01 Prepare
- 01Intake and scopingStepA forum idea enters intake and is classified by purpose, audience, sensitivity, domain, public-safe implications and review.
- 03DesignRecordA forum has a defined scope, format, participant logic, moderation plan, records plan, output plan, public-safe posture and follow-up route.
- 04Invitation and briefingStepInvitations set expectations. Weak invitations create wrong expectations.
02 Review
- 05Public-safe reviewGatePublic-safe review is the gate before convening. The convening is held with moderation, after review only.
03 Convene
- 06Moderated conveningExerciseModeration helps protect the architecture from drift during live exchange. It prevents discussion from becoming false consensus.
04 Record and route
- 02Corrections return through public-safe reviewRecordCorrections to the record return through public-safe review.
- 07Make the recordRecordRecords state what the event was and was not, what was discussed, concluded and left unresolved, and the next steps.
- 08Classify the outputsStepAfter the forum, outputs are classified. A transcript is not a decision, and a recommendation is not adoption.
- 09Route the outputsStepClassified outputs follow four routes.
- 10A competent actor decidesDecision · The competent actorAfter a handoff, a competent actor takes the decision under its own authority. Decisions stay with competent actors.
Operations: ForumOutline of a convening design from a page marked Draft, not a record of operation or of any event. The forum layer is not The Global Risks Forum and not Universe. Every programme is at service level R0.
Register your interest.
Write to the contact form. The acknowledgement gives a reference and names the next step.
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
When are entries added?
Bring a method, a dataset or a question.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.