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).
Free. Save your status, tasks and notes.
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
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).
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.
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.
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).
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
- 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).
- 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.
- 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.
- 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/IEC 27001: 5 mappings
This control partially overlaps A.5.26.
Annex A 5.26 requires incidents to be responded to in line with documented procedures. ISM-0576 requires developing, implementing and maintaining an incident management policy and associated incident response plan, which provides the documented basis for those procedures. Implementing ISM-0576 ensures consistent alignment with Annex A 5.26's 'documented procedures' expectation.
This control partially overlaps A.5.29.
Annex A 5.29 requires the organisation to plan for maintaining information security during disruptions. ISM-0576 relates by requiring an incident management policy and incident response plan, which supports maintaining security when disruptions are caused by cyber incidents. The primary control is broader because it covers disruption scenarios beyond incidents and expects planning for maintaining security levels across operations, not just incident handling governance and playbooks.
This control partially overlaps A.5.37.
Annex A 5.37 requires operational procedures for information processing to be documented and made available to relevant personnel. ISM-0576 requires documented incident management policy and incident response plan, which are a class of operating procedures used during incident handling. ISM-0576 is focused specifically on cyber security incidents, whereas Annex A 5.37 applies to operating procedures across all information processing activities.
This control depends on A.5.5.
ISM-0576 requires an incident management policy and incident response plan that are implemented and maintained, which typically include external notification and coordination procedures during incidents. Annex A 5.5 requires the organisation to establish and maintain contact with relevant authorities, enabling the practical execution of the external liaison steps that the ISM-0576 plan would call for (e.g. knowing who to contact and how). Annex A 5.5 does not require an incident response plan or incident governance, but it supports ISM-0576 by making authority engagement feasible when the plan is enacted.
This control depends on A.5.27.
Annex A 5.27 requires organisations to use knowledge from incidents to strengthen and improve information security controls. ISM-0576 requires a cyber security incident management policy and response plan, which creates the process framework where post-incident reviews and improvement actions can be embedded. ISM-0576 focuses on establishing incident management capability, while Annex A 5.27 focuses specifically on feeding incident learnings into control improvements.
ISO/IEC 42001: 1 mapping
This control is broader than A.8.4.
Annex A 8.4 requires the organisation to determine and document a plan for communicating incidents to users of the AI system. ISM-0576 requires an organisation-wide cyber security incident management policy and associated incident response plan to be developed, implemented and maintained, within which communication to impacted parties can be defined. ISM-0576 is broader and less specific about user communications, while Annex A 8.4 is a targeted requirement for documented incident communications to AI system users.
ASD Essential Eight: 6 mappings
- E8-AH-ML2.16Report cyber security incidents to the CISO or a delegate as soon as possibleBroader than
This control is broader than E8-AH-ML2.16.
E8-AH-ML2.16 requires cyber security incidents to be reported to the CISO (or delegate) as soon as possible. ISM-0576 requires an incident management policy and associated incident response plan to be developed, implemented and maintained. E8-AH-ML2.16 is a specific operational reporting expectation that would typically be defined and governed through the broader policy/plan framework required by ISM-0576.
This control is broader than E8-RA-ML2.11.
ISM-0576 requires an incident management policy and associated incident response plan to be developed, implemented and maintained, which would define escalation paths including CISO notification. E8-RA-ML2.11 requires cyber security incidents to be reported promptly to the CISO (or delegate). The primary control is a specific operational requirement that would typically be implemented as part of the broader governance and planning mandated by ISM-0576.
This control supports E8-AC-ML2.11.
E8-AC-ML2.11 requires enacting the cyber security incident response plan once an incident is identified. ISM-0576 requires the organisation to develop, implement and maintain the incident management policy and associated incident response plan. E8-AC-ML2.11 depends on ISM-0576 because a plan must exist, be implemented, and be maintained before it can be reliably enacted during an incident.
This control supports E8-AH-ML2.18.
E8-AH-ML2.18 requires that the incident response plan is enacted following identification of a cyber security incident. ISM-0576 requires a cyber security incident management policy and associated response plan to be developed, implemented and maintained. E8-AH-ML2.18 depends on ISM-0576 because enactment presupposes a maintained policy/plan framework exists and is current.
This control supports E8-MF-ML2.12.
E8-MF-ML2.12 requires enacting the incident response plan after identifying a cyber incident. ISM-0576 requires that an incident management policy and associated incident response plan are developed, implemented and maintained, which is a prerequisite for activation. Without the ISM-0576 artefacts in place, E8-MF-ML2.12 cannot be reliably satisfied beyond ad hoc response.
This control supports E8-RA-ML2.13.
E8-RA-ML2.13 requires the organisation to enact the cyber incident response plan immediately after an incident is identified. ISM-0576 requires that an incident management policy and associated incident response plan are developed, implemented and maintained, which is a prerequisite for being able to enact the plan.
ASD Essentials for enterprise IT: 2 mappings
- IT.RES-03.1Respond to cyber security incidents using documented, tested and approved proceduresPartially overlaps
This control partially overlaps IT.RES-03.1.
IT.RES-03.1 requires documented, tested and approved procedures to be used when responding to cyber security incidents; ISM-0576 requires an incident management policy and response plan to be developed, implemented and maintained, providing the documented basis for that response.
- IT.RES-05.1Integrate external coordination obligations into incident response activities where requiredPartially overlaps
This control partially overlaps IT.RES-05.1.
IT.RES-05.1 requires external coordination obligations to be built into incident response where required; ISM-0576 requires an incident management policy and response plan to be developed, implemented and maintained, the documents where those obligations can be set out.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




