Home→Blog→Incident Response Planning: Build Your Cyber Secur...
Compliance & Governance

Incident Response Planning: Build Your Cyber Security Playbook

Practical incident response framework for Australian organisations covering NIST 6-phase playbook, roles and responsibilities, communication templates, Notifiable Data Breaches notification requirements, and ransomware-specific response procedures.

Alpesh Nakar
Nov 3, 2025
9 min read
🇦🇺 Australian Context
📜 NIST, Privacy Act, NDB Scheme, ACSC

⚡TL;DR

  • •Structure your response around the NIST 6-phase framework: Preparation, Detection and Analysis, Containment, Eradication, Recovery, and Post-Incident Activity.
  • •Define clear team roles before an incident: Incident Response Manager, Technical Lead, Communications Lead, Legal Counsel, and Executive Sponsor (roles may be combined for SMBs).
  • •The Notifiable Data Breaches scheme gives you 30 days from awareness to assess and notify OAIC and affected individuals, with significant civil penalties for serious or repeated non-compliance.
  • •Keep a ransomware-specific playbook: isolate patient zero, preserve memory before powering off, assess backup integrity, and report to AFP Cyber Command via ReportCyber.
  • •Prepare communication templates in advance for staff, customers, and the OAIC so notifications are not drafted under pressure.
  • •Test the plan with quarterly tabletop exercises and an annual full simulation, then update it after every major incident.

Why every Australian organisation needs an incident response plan

Cyber incidents are inevitable-the question is not "if" but "when" your organisation will face a security breach, ransomware attack, or data compromise. Without a tested incident response (IR) plan, organisations panic, make costly mistakes, miss NDB (OAIC — Notifiable Data Breaches scheme, accessed 16 June 2026) notification deadlines, destroy forensic evidence, and suffer prolonged downtime. Organisations with documented IR plans typically recover substantially faster and incur materially lower breach costs than those without plans.

1. The NIST incident response framework (6 phases)

Phase 1: Preparation

  • Establish incident response team (roles, responsibilities, contact details)
  • Deploy security controls (SIEM, EDR, MFA, backups)
  • Create communication templates (internal, customer, media, OAIC)
  • Document escalation procedures and decision authority
  • Maintain forensic toolkits and evidence collection procedures
  • Conduct tabletop exercises quarterly to test plan

Phase 2: Detection and Analysis

  • Identify indicators of compromise (IOCs): unusual network traffic, failed login attempts, malware alerts, unexpected file encryption
  • Triage severity: Critical (production impact, data exfiltration) vs Medium (contained to non-critical system) vs Low (false positive)
  • Preserve evidence: Forensic images of affected systems, memory dumps, log files, network packet captures
  • Initial assessment: Scope of compromise, attack vector, threat actor attribution (if possible), business impact

Phase 3: Containment

  • Short-term containment: Isolate affected systems from network, disable compromised accounts, block malicious IPs at firewall
  • Long-term containment: Apply emergency patches, segment networks, deploy additional monitoring, implement temporary compensating controls
  • Balance: Containment vs business continuity. Shutting down entire network stops attack but halts business-risk-based decision required

Phase 4: Eradication

  • Remove malware from all systems (not just patient zero)
  • Close vulnerability that enabled attack (patch, configuration change, access revocation)
  • Reset credentials for all compromised accounts and privileged users
  • Verify threat actor no longer has foothold (scan for backdoors, persistence mechanisms)

Phase 5: Recovery

  • Restore systems from clean backups or rebuild from known-good images
  • Validate restored systems free from malware before reconnecting to production
  • Phased return to normal operations with enhanced monitoring
  • Communicate recovery status to stakeholders

Phase 6: Post-Incident Activity (Lessons Learned)

  • Root cause analysis: How did attack succeed? Which controls failed?
  • Timeline documentation: Attack progression, detection time, containment time, recovery time
  • Remediation actions: Implement missing Essential Eight (ACSC — Essential Eight maturity model, accessed 16 June 2026) controls, patch management improvements, staff training
  • Update IR plan based on lessons learned
  • Formal post-mortem report for executive/board review

2. Incident response team roles and responsibilities

  • Incident Response Manager (IRM): Overall coordination, decision authority, stakeholder communication, OAIC liaison. Typically: IT Manager, CISO, or Security Manager.
  • Technical Lead: Forensic analysis, malware reverse engineering, system restoration. Typically: Senior Systems Administrator, Security Analyst.
  • Communications Lead: Internal communications (staff), external communications (customers, media, OAIC), NDB notifications. Typically: Communications Manager, Legal Counsel.
  • Legal Counsel: Privacy Act obligations, NDB assessment, regulatory reporting, litigation hold, law enforcement liaison.
  • Executive Sponsor: Authority for business-impacting decisions (shut down network, pay ransom, public disclosure). Typically: CEO, CIO.
  • External Specialists (on retainer): Forensic investigators (for complex incidents), cyber insurance provider, PR firm (for major breaches), law enforcement (AFP Cyber Command for serious cybercrime).

3. Communication templates

Internal incident notification (to staff)

Subject: URGENT: Security Incident Response - Action Required

Body: "We are currently responding to a cyber security incident affecting [systems/data]. Our incident response team is actively investigating and containing the issue. Please take the following immediate actions: [specific instructions]. Do not [prohibited actions]. Updates will be provided every [frequency]. Questions: contact [IR Manager] at [contact details]."

Customer notification (data breach)

Subject: Important Security Notice Regarding Your Personal Information

Body: "We are writing to inform you of a data security incident that may have affected your personal information. On [date], we discovered [brief description]. The information potentially accessed includes [data types]. We have taken immediate steps to [remediation actions]. We recommend you [protective actions for customers]. We sincerely apologise for this incident. Questions: [contact details]. We have notified the Office of the Australian Information Commissioner as required."

OAIC NDB notification

Submitted via OAIC online NDB form within 30 days, including:

  • Organisation identity and contact details
  • Description of breach (date discovered, attack vector, systems affected)
  • Kinds of personal information involved (names, addresses, financial data, health information)
  • Number of individuals affected (estimate if exact number unknown)
  • Recommended steps individuals should take (credit monitoring, password changes)
  • Contact details for individuals seeking more information

4. Notifiable Data Breaches (NDB) assessment and notification

30-day assessment timeline

  • Day 0: Become aware of suspected eligible data breach
  • Days 1-14: Conduct reasonable investigation to determine if breach is eligible (unauthorised access/disclosure) and likely to cause serious harm
  • Day 15-28: If breach assessment incomplete, prepare for conservative notification approach
  • Day 30 (deadline): Submit NDB notification to OAIC and notify affected individuals if serious harm likely OR assessment incomplete

Serious harm assessment factors

  • Type of information: Health records, financial information, government IDs (high harm). Contact details only (low harm).
  • Sensitivity: Information about vulnerabilities (domestic violence victims, children, medical conditions) increases harm likelihood.
  • Who accessed: Malicious actor (high harm). Accidental internal disclosure to trusted staff (low harm).
  • Safeguards: Encrypted data (reduces harm). Plaintext data (increases harm).
  • Nature of harm: Identity theft, financial fraud, physical safety risks, reputational damage, psychological distress.

5. Ransomware-specific response playbook

Immediate actions (0-2 hours)

  • Isolate patient zero device from network (disconnect network cable or disable Wi-Fi)
  • Identify ransomware variant (ransom note, file extensions, IOCs) using ID Ransomware tool
  • Assess spread: Check file servers, backups, domain controllers for encryption
  • Notify incident response team and executive sponsor
  • Preserve forensic evidence (do NOT power off systems-take memory dumps first)
  • Document ransom demand (amount, payment method, deadline, threat actor contact)

Containment and recovery (2-48 hours)

  • Contain spread: Disable admin accounts, reset passwords, block lateral movement
  • Assess backup integrity: Are backups encrypted? When is last clean backup?
  • Engage cyber insurance and external forensics if policy requires notification within 24 hours
  • Law enforcement notification: Report to AFP Cyber Command via ReportCyber (ACSC — ReportCyber, accessed 16 June 2026) (provides intelligence, may assist recovery)
  • Ransom payment decision: Consult legal counsel, cyber insurance, executive sponsor. AFP and ACSC discourage payment but acknowledge business realities.
  • Restore from backups OR rebuild systems if backups compromised

Post-ransomware remediation

  • Root cause analysis: Phishing? RDP exploit? Unpatched vulnerability?
  • Implement Essential Eight controls to prevent recurrence (application control, MFA, patch management, backups)
  • NDB assessment: If ransomware exfiltrated data (double extortion), likely serious harm-notify OAIC
  • Communicate with customers if personal information encrypted or exfiltrated

6. Australian case study: Professional services firm Business Email Compromise (BEC)

Incident: Finance manager received email appearing from CEO requesting urgent AUD $180K wire transfer to "new supplier account." Email used CEO's display name but external Gmail address. Manager did not verify via phone (CEO travelling interstate). Transfer completed.

IR Response:

  • Detection (Day 0, 11am): CEO returned from travel, finance manager mentioned wire transfer. CEO confirmed did not authorise. IR team activated immediately.
  • Containment (Day 0, 11:30am): Contacted bank to freeze transfer (too late-already cleared to offshore account). Reviewed email logs, identified phishing email bypassed spam filter.
  • Analysis (Day 0-1): Forensic review of CEO's email account found no compromise. BEC was pure social engineering, not account takeover. No personal information disclosed-financial loss only.
  • Reporting (Day 1): Reported to AFP Cyber Command via ReportCyber. No NDB notification required (no personal information breach). Notified cyber insurance for financial loss claim.
  • Recovery (Day 2-7): Implemented dual-approval process for wire transfers over AUD $10K. Deployed email authentication (DMARC, SPF, DKIM). Staff training on BEC tactics.
  • Outcome: AUD $180K loss (partially recovered via cyber insurance-AUD $120K payout). No regulatory penalties (no Privacy Act breach). Prevented future BEC via process and technical controls.

Before / After

Before incident response plan: No documented procedures, panic during incidents, prolonged downtime, missed NDB deadlines, destroyed forensic evidence, uncoordinated communications, repeated incidents due to no lessons learned.

After incident response plan: Documented 6-phase playbook, defined team roles, communication templates ready, quarterly tabletop exercises, substantially faster recovery, NDB compliance, preserved evidence for insurance claims, continuous improvement from post-incident reviews.

Australian Context

  • Notifiable Data Breaches (NDB) scheme: Mandatory notification to OAIC and affected individuals within 30 days if breach likely to cause serious harm. Incident response plan must include NDB assessment procedures.
  • AFP Cyber Command: Report cybercrime via ReportCyber (online portal). AFP investigates serious incidents, provides intelligence, may assist recovery or attribution.
  • ACSC guidance: ACSC publishes incident response guides, ransomware playbooks, and threat intelligence. Essential Eight controls reduce incident frequency and impact.
  • Cyber insurance requirements: Most Australian cyber insurance policies require incident notification within 24-48 hours and use of panel forensic providers. Review policy before incident.

Evidence to Collect

  • Incident response plan document with 6-phase playbook and team roles
  • Communication templates (internal, customer, OAIC, media)
  • Tabletop exercise records (quarterly testing with scenarios and participant feedback)
  • Incident log (all incidents responded to, even false positives, with timelines and actions)
  • Post-incident reports (root cause analysis, lessons learned, remediation actions)
  • NDB notifications (copies of OAIC submissions and customer notifications)
  • Forensic evidence chain of custody documentation

Call to Action

Don't wait for a cyber incident to discover you have no response plan. Build your incident response playbook now, define team roles, create communication templates, and conduct quarterly tabletop exercises. When (not if) an incident occurs, you'll be prepared.

Sources referenced in this article: OAIC (Notifiable Data Breaches scheme), ACSC (Essential Eight, ReportCyber), NIST, AFP Cyber Command, SOCI Act.

Assess Your Maturity

Understand where your organisation stands on the Essential Eight maturity model and identify priority controls.

Train Your Team

Hands-on Essential Eight fundamentals course for security teams, architects, and IT leaders.

Frequently Asked Questions

Questions security teams commonly ask about Essential Eight implementation.

Ready to Move from Level 1 to Level 2+?

Start your 12-month Essential Eight maturity journey with expert guidance and practical roadmaps.

Read Next

Continue exploring security insights and best practices

Technology
Oct 25, 2025

A practical guide to implementing system monitoring, logging, and SIEM for Australian organisations—covering compliance, threat detection, and operational best practices.

Privacy & Compliance
Mar 9, 2026
10 min read

The OAIC Notifiable Data Breaches scheme explained for Australian small business owners. Who is covered, the 30-day assessment clock, and the steps to take when a breach happens.

SharePoint Governance
Nov 3, 2026
12 min read

Copilot does not break your permissions. It reveals them. Five checks a site owner can run in under an hour, no admin rights needed, before Copilot reaches your site.