Skip to content
Cyber security incidents
ASD ISMISM-1784

ASD ISM 1784 Annual testing of cyber incident response plan

What it says

The cyber security incident management policy, including the associated cyber security incident response plan, is exercised at least annually.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

The organisation tests its cyber incident response plan every year to ensure it's effective.

This control means your organisation needs to test its plan for handling cyber incidents every year. It's important because if you don't check your response plan, you might be unprepared when a data breach or cyber attack happens, which could result in lost data, downtime for your business, and damage to your reputation.

Why it matters

An untested incident response plan may lead to prolonged downtime and chaos during real cyber attacks, increasing recovery costs and reputational damage.

How to implement

  1. The IT team should schedule an annual test of the incident response plan.

    This involves running a simulation of a cyber attack to check if everyone knows their role and if the plan works smoothly. Collect feedback afterward to update and improve the plan.

  2. Ensure the management team reviews the updated incident response plan after every test.

    This involves looking at what went well and what didn't during the simulation, and then making decisions on any necessary changes. Document these reviews to track improvements over time.

  3. Assign a project manager to coordinate with all departments involved in the incident response.

    They should ensure everyone participates in the testing and understands their responsibilities. Use team meetings and follow-up emails to confirm everyone's clear on their tasks.

  4. Have the HR team include cyber incident response training in the annual staff training schedule.

    Educate employees on recognising cyber threats and understanding the response process. Use simple examples and interactive sessions to reinforce learning.

  5. The finance department should assess the costs associated with testing and improving the cyber incident response plan.

    This includes estimating resources, training, and updates required after the annual test. Regular budgeting meetings can help allocate the right funds.

Keep it running

Exercise the incident response plan at least annually; capture lessons learned, update playbooks and contacts, and confirm each role is understood.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The test schedule and log: Request documentation showing the annual testing schedule for the response plans.

    Look at

    The dates and details of past tests.

    Good evidence

    Is a yearly record with clear dates, participants, and outcomes.

  2. Check 2 of 5What an auditor asks for

    Look at

    Sections detailing what was done well and what needs improvement. Good reports identify specific changes made to the plan based on test results.

  3. Check 3 of 5What an auditor asks for

    Ask for

    To see the current version of the incident response plan post-testing.

    Look at

    Dates and notes that indicate revisions were made after testing.

    Good evidence

    Is a recent update with clear revisions reflecting test findings.

  4. Check 4 of 5What an auditor asks for

    Look at

    Attendance records and training materials used.

    Good evidence

    Would show that all relevant personnel received up-to-date training, supported by attendance logs.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Budget documentation linked to testing and updating the incident response plan.

    Look at

    How funds are allocated and used for these activities.

    Good evidence

    Includes detailed financial records showing planned and actual spending on these processes.

Mappings

Closest match in ISO/IEC 27001: A.5.24, Information security incident management planning and preparation, which partially overlaps with this control.

ISO 27001

ISO/IEC 27001: 2 mappings

Essential Eight

ASD Essential Eight: 1 mapping

ASD Essentials

ASD Essentials for enterprise IT: 3 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.