Effective steps to cyber exercise creation

Document preview5 pages
Cover of Effective steps to cyber exercise creation
Page 1 of 5

Download this document free

Get this document with your free trial. Choose from the full Complyzard library.

Try 1 month free30 days free, then $19/month. Trial terms apply. Card required. Cancel anytime.
Document information

The following tips can help organisations create their own cyber incident response exercises.

Adapted edition

Document type
Reference Guide
Format
DOCX
Pages
5
Language
English
Version
1.0
Updated
2026-09-16
Description

The following tips can help organisations create their own cyber incident response exercises for organisational planning, review and training. NCSC guidance is advisory and should be applied to the organisation's own risks and obligations.

Contents
  • Why conduct cyber incident exercises?
  • Step 1: Be clear on what you want to exercise, and why
  • Step 2: Secure senior level endorsement
  • Step 3: Select the most effective approach/format
  • Step 4: Create an exercise development team and agree exercise participants
  • Step 5: Create and agree exercise metrics
  • Step 6: Create and develop the exercise scenario
  • Step 7: Create and develop exercise injects
  • Step 8: Develop guidance for the delivery team and participants
  • Step 9: Capture evidence and feedback, and identify lessons in a post exercise report
  • Source links
Source and licence
Effective steps to cyber exercise creation

National Cyber Security Centre

AttributionNational Cyber Security Centre, “Effective steps to cyber exercise creation” (3 February 2020), reused under the Open Government Licence v3.0.

ChangesAdapted 16 September 2026: converted the official HTML article into neutral text-only DOCX and PDF editions. Preserved article headings, paragraphs, lists and plain-text source-link destinations; normalized web whitespace and typographic punctuation; omitted site navigation, topic and download cards, images, logos, scripts, styles and page furniture.

Version history
  • v1.016/09/2026
Report this document