Skip to content
Cyber security incidents
ASD ISMISM-0576

ASD ISM 0576 Develop and maintain cyber security incident plans

What it says

A cyber security incident management policy, and associated cyber security incident response plan, is developed, implemented and maintained.

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

In plain English

Write a cyber security incident management policy and the incident response plan that goes with it, put both into practice and keep them up to date.

A cyber security incident management policy and its associated cyber security incident response plan must both be developed, implemented and maintained:

  • Developed: both exist in writing. The policy typically sets responsibilities, resources and triage rules. The plan sets out the response, and ISM-0043 lists what each system's plan must cover.
  • Implemented: the roles, resources and reporting routes they set are in place, and people follow them when an incident occurs.
  • Maintained: both stay current and are exercised at least annually (ISM-1784).

Why it matters

An incident is the wrong time to work out who decides, who does what and what comes first. An agreed policy and plan settle those questions in advance, so detection, triage and response can start sooner and stay coordinated.

How to implement

  1. Write the policy.

    State who prepares for, detects and responds to incidents, which people and tools are assigned to that work, and how events are triaged and escalated. Keep it consistent with the security monitoring policy (ISM-0580).

  2. Write the response plan that goes with it.

    Cover how to identify, contain and recover from an incident, who leads and how to report it. Use ISM-0043's list as the structure, since it sets what each system's plan must cover. Where a service provider runs part of the response, name its role and contacts.

  3. Approve both documents and give them to the people who act on them.

    The CISO approves organisational-level documentation and each system's authorising officer approves system-specific plans (ISM-0047). Documents and later changes go to all stakeholders (ISM-1602). Keep a copy that can be reached if the affected systems are down.

  4. Put in place what the plan relies on.

    Set up the reporting route to the CISO or a delegate (ISM-0123), the cyber security incident register (ISM-0125), contact lists and responder access. For a bought service, confirm the provider's reporting duty and contact (ISM-0141). Once an incident is identified, enact the plan (ISM-1819).

  5. Keep both documents current.

    Review them at least annually and show a 'current as at' date (ISM-0888). Exercise them at least annually (ISM-1784). Update them after incidents, exercises and changes to roles, systems or service providers.

Keep it running

Check contact details and named roles whenever people or service providers change, because an out-of-date list delays the first call. Review both documents after each incident and exercise.

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    The current policy and response plan, with their approval records.

    Look at

    Whether the policy and plan both exist, in one document or two that are clearly linked, and who approved the current versions.

    Good evidence

    The policy and plan both exist, in one document or two that are clearly linked. The CISO approved the organisational-level versions, and each system's authorising officer approved any system-specific plan (ISM-0047).

  2. Check 2 of 4What an auditor asks for

    Ask for

    Records of a recent incident chosen from service desk tickets or monitoring alerts, not from the incident register, or the latest exercise if there were no incidents.

    Look at

    Whether the response followed the roles, triage and reporting steps set by the policy and plan.

    Good evidence

    The records show those roles, triage decisions and reporting steps were followed, and any departure has a recorded reason.

  3. Check 3 of 4What an auditor asks for

    Ask for

    Interviews with two or three people the plan names, including someone outside the security team.

    Look at

    Whether each can say what they do first, and can find the current plan on the spot.

    Good evidence

    Each person describes the same first actions as the plan, and opens the current version during the interview.

  4. Check 4 of 4What an auditor asks for

    Ask for

    Changes since the last version, taken from staff departures, system changes and service provider changes, with a sample of contacts in the plan.

    Look at

    Whether the policy and plan reflect those changes, whether the contacts still work, and the 'current as at' date.

    Good evidence

    Each change that affects a role, step or contact appears in the current documents, sampled contacts work, and the 'current as at' date is no more than 12 months old (ISM-0888).

Mappings

Closest match in ISO/IEC 42001: A.8.4, Communication of incidents, which this control covers in full and more.

ISO 27001

ISO/IEC 27001: 5 mappings

  • A.5.37Documented operating proceduresPartially overlaps
ISO 42001

ISO/IEC 42001: 1 mapping

Essential Eight

ASD Essential Eight: 6 mappings

ASD Essentials

ASD Essentials for enterprise IT: 2 mappings

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