Cyber Incident Response Plan Template | Stanfield IT
Colleagues conducting a tabletop cyber incident response exercise

Cyber Incident Response Plan Template for Australian Businesses

Table of Contents

An incident response plan template gives your business a practical starting point for handling a suspected cyber incident. It should identify who takes charge, how staff report a problem, who can approve containment and how decisions are recorded. An incident response plan template becomes useful when those details are completed and tested before an incident occurs.

For an Australian SME, that might mean responding to a compromised finance mailbox, a suspicious payment request or ransomware on a device. The first challenge is often uncertainty: the business knows something is wrong but has not yet established the scale or consequences.

Download the incident response plan template

Download the editable Word template. It contains six sections covering plan ownership, contacts and decision authority, first actions, containment and evidence, notification and communications, and recovery and testing. There is no form to complete before downloading it.

Replace the bracketed fields, appoint deputies, verify external contacts and agree the plan with your IT provider and relevant advisers. Keep a controlled offline copy that authorised people can access if business email or cloud services are unavailable. Do not place passwords, recovery codes or access tokens in the document.

This is a starting document, not a substitute for advice about your particular legal, contractual or insurance obligations. A completed incident response plan template also does not establish that your organisation is compliant with any standard.

What an incident response plan template must cover

A workable plan connects business decisions with technical actions. It explains who may interrupt a service, isolate a device, restrict an account or engage specialist support. It should also explain what happens when the usual approver is unavailable.

Keep the initial response instructions short enough to use under pressure. Supporting technical procedures can sit elsewhere, provided responders know where to find them and have access. Long lists of security terminology are less useful than a verified phone number and a clear decision owner.

The Australian Signals Directorate’s incident planning guidance provides a broader framework for preparation and response. Use it alongside a plan tailored to your systems, staff and business dependencies.

Incident lead, technical lead, privacy and legal lead, and communications lead responsibilities

Name the people and agree their authority

The incident lead coordinates the response, maintains the decision record and sets the next update time. The technical lead investigates and recommends containment. A privacy or legal lead assesses information exposure and obligations. The communications lead manages approved messages to staff and external audiences.

One person may hold several roles in a small business, but the responsibilities still need to be explicit. Include an executive who can accept business disruption and approve expenditure. Your IT provider should confirm who is available outside business hours and what work falls outside its normal agreement.

Use trusted contact routes for the bank, insurer, broker and key suppliers. If email may be compromised, do not rely on an address or phone number supplied within the suspicious message. Agree a separate coordination channel before you need it.

What should happen in the first hour?

The aim is to organise the response and reduce ongoing harm without destroying evidence. Actions depend on the incident; the plan should not direct every employee to shut down every device automatically.

Responsibility Initial action Record to keep
First reporter Report the observation through the trusted channel What was seen, system, time and contact details
Incident lead Activate the plan and appoint owners Incident ID, known facts, unknowns and next update
Technical lead Assess scope and propose proportionate containment Evidence, proposed action, approval and result
Finance lead Contact the bank urgently if payment fraud is suspected Verified contact, transaction details and bank advice
Privacy or legal lead Assess potential information exposure and duties Applicable obligations, deadlines and decisions

Avoid presenting assumptions as confirmed facts. “A mailbox appears compromised” and “all customer records were taken” describe very different levels of knowledge. Record what supports each conclusion and what still needs investigation.

Preserve evidence while containing the incident

Technical responders should decide how to preserve relevant logs, messages and device information while reducing harm. Wiping a computer, deleting a mailbox or restoring over existing data can remove information needed to understand the incident. Staff should escalate rather than improvise destructive repairs.

Maintain a controlled incident record with dates, times and time zones. For each evidence item, record its source, collector, protected location and any transfer between people. Limit access to those who need it, particularly where the record contains personal or confidential information.

Capture the reason for important decisions as well as the outcome. If an account remains active temporarily to protect an essential service, record the approver, compensating measures and review time. The same discipline helps later when management, insurers or advisers need an accurate account.

Incident evidence record: observation, evidence, decision and review

Check notification obligations early

For organisations covered by the Notifiable Data Breaches scheme, a suspected eligible breach requires a reasonable and expeditious assessment, taking all reasonable steps to complete it within 30 calendar days. Where there are reasonable grounds to believe an eligible breach occurred, notification is required as soon as practicable, subject to applicable exceptions. The assessment period is not a general waiting period.

The OAIC’s NDB guidance explains the tests, including likely serious harm and the effect of remedial action. Have the responsible adviser assess your circumstances. Contracts, insurers and sector regulators may create separate obligations.

Assign someone to track each applicable deadline and approval. Reporting to one organisation does not necessarily satisfy another obligation. Keep copies of submissions and messages, and use factual holding statements when the investigation is still developing.

Recovery is more than getting systems online

Agree what must be corrected before services return. Depending on the incident, this could include removing unauthorised access, addressing the entry point, validating restored data and checking that critical integrations work. The technical lead recommends readiness; the business owner accepts the remaining operational risk.

An incident response plan coordinates investigation, decisions and communications. A disaster recovery plan describes how services and data are restored. The two should connect, and our disaster recovery plan template guide covers that related planning task.

Test your incident response plan template

Run a tabletop exercise using a believable scenario. For example, ask the finance team what happens when a supplier reports that a payment went to a different account. Follow the reporting route, contact the nominated owners and test who can authorise urgent action.

Record gaps with an owner and due date. A missing deputy, inaccessible offline copy or uncertain insurer contact is a useful finding before a real incident. Repeat the exercise after significant staffing, system or supplier changes.

Who should help tailor the plan?

The business owns the decisions, supported by its IT provider and appropriate privacy, legal and insurance advisers. Stanfield IT’s incident response services can help assess technical readiness and connect the document with the systems and response arrangements your organisation actually uses.

Experience better IT services

If your IT feels reactive or unclear, we’ll stabilise the essentials and align it to your business goals.

Scroll to Top