AI agents investigate every alert, add context, and prepare cases for response, on a full-stack SecOps platform that captures and correlates all your security data.
Cloud-based SIEM platform providing visibility across all your data sources
Every alert investigated, with a verdict and the evidence behind it
Manage your external footprint, publicly available data, and Dark Web leaks
Log management and threat detection across any of your log sources
Get ultimate assurance that your environment is free from threat actors
Fully featured distrubuted NDR for on-premises and public cloud environments
A SecOps platform purpose-built for industrial and OT environments
Integrated endpoint agent providing deep visibility, response and forensics
Deploy honeypots and honeytokens and stay ahead of threat actors
24x7 security operations from our Australian SOC. AI investigates every alert, and experienced analysts validate findings and contain threats around the clock.
24x7 managed detection and response across endpoint, network, cloud, identity, and log sources
AI investigations and 24x7 MDR on the Microsoft Sentinel you already own
Eyes-on-glass SOC and continuous threat hunting
Expert hunters and AI agents find attacker activity your alerts missed
Quickly recover from cyber attacks and breaches
ThreatDefence is the only SecOps as a Service company providing broad coverage across your entire technology stack with evidence-based security.
We provide security teams with full-stack SecOps infrastructure – you get deep visibility from day one, gain control over your security data, and get access to a comprehensive set of ready-to-use tools, detections, workflows, playbooks and scenarios.
24x7 SOC, Continuous Monitoring, Threat Containment and Incident Response
Visibility and actionable insights for all IT assets
Leverage our Cyber Range to train defenders based on real-world scenarios and simulations
OT and industrial cyber security services for critical infrastructure
Monitoring, evidence and a 24×7 SOC in one platform
Compliance monitoring, evidence and board reporting
Privacy Act reform impacts, obligations, and practical security considerations
Monitoring and compliance support for critical infrastructure environments
A practical guide to securing critical infrastructure with continuous monitoring
A practical buyer’s guide for schools evaluating SIEM and SOC services
A practical guide to selecting the right SIEM and SOC service for local government
Articles on security operations, AI and compliance
Events, awards and company news
Read what our customers say about us
Solution briefs and datasheets
How we keep your data secure
Technical support and knowledge base
Guides, case studies, and advisories in one place
How AI agents investigate alerts and run security operations
Free ebook: a practical guide to adopting an AI SOC platform
A practical guide to incident response and digital forensics
Where SOAR playbooks fit and where AI agents take over
Free ebook: modern security operations with Microsoft Sentinel
How the framework is structured and what changes from the Essential Eight
How an attack unfolds stage by stage and how to detect each one
November 16, 2026
November 13, 2026
November 10, 2026
We provide end-to-end SecOps solutions for Managed Security Service Providers (MSSPs), Managed Service Providers (MSPs), and Value-Added Resellers (VARs).
Find out how you can become a ThreatDefence partner.
Protect your entire technology stack and build your SecOps on your own pace
White-labeled AI SOC for every client tenant, co-managed with our SOC team
Launch your SOC business without any upfront investment
Embed security operations, threat intelligence and exposure data in your product
Sovereign SOC for Australian MSPs and MSSPs, with onshore analysts and client data
Set the rules for closing alerts automatically, with evidence checks and review
How MSPs deliver branded security monitoring with a SOC partner
ThreatDefence was an official partner of the Cyber Resilience Summit NSW, 29 October 2026 at Hilton Sydney.
Our team was back at BSides Canberra, and our cyber quiz was a hit again.
Two days in Perth with our partner Ever Nimble, on security operations and cyber resilience.
Sponsors of the AUSCERT Cyber Security Conference on the Gold Coast.
Sponsors of the Gartner Security & Risk Management Summit in March.
Sponsors of the Cyber Security for Critical Assets Summit in Perth, February 2026.
Expert conversations with speakers and attendees at CyberCon Melbourne 2025.
An incident response plan is a written document that sets out how an organization will detect, manage, and recover from a cybersecurity incident. It records who decides, who acts, and how people reach each other when normal systems may be unavailable.This guide goes through a plan section by section. For each one it explains what to write and gives example wording that can be adapted.
Most organizations that suffer a serious incident already had a plan. In many cases nobody opened it. The plans that are used during a real incident share a few features, and they have little to do with length or polish.
They can be found. A plan stored only on the file server is gone when the file server is encrypted. Working plans exist on paper and somewhere outside the corporate environment.
They name people. The CISO will notify the board works until the CISO is on a flight. A plan that gives each role a named person and a named deputy, with mobile numbers, still works that day.
The CISO will notify the board
They settle authority. The single most common delay in real incidents is waiting for someone to approve an action that everyone agrees is necessary. A working plan says in advance who may disconnect a server, and who may take the website down.
They match reality. A plan that assumes a 24x7 security team, when the organization has two IT staff, describes a different company. The process has to fit the people and tools that actually exist.
A plan is a record of decisions made in calm conditions, for use when conditions are anything but calm. The rest of this guide is about which decisions to record.
A plan has several audiences, and each reads a different part.
They need to know whether this is an incident, who to tell, and what to do in the next 15 minutes. They read the activation section and the contact list.
They need the whole process, the authority they hold, and when to escalate.
They need to know which decisions are theirs, how they will be kept informed, and who speaks for the company. They read the roles, severity, and communication sections.
They need to know when they are brought in and what is expected.
They need to know who their contact is, what access they have, and what they may do without asking.
They read the plan afterward, to see whether the organization had one and followed it.
A common and effective layout puts a one-page summary first: how to declare an incident, the severity table, and the key phone numbers.
A workable plan has few sections, and each answers one question. The table is the whole outline, and it comes to eight to ten pages before the contact list.
Detailed technical steps for specific incident types belong in playbooks, which the plan lists. Keeping them out is what lets the plan stay short enough to read during an incident.
The Australian Signals Directorate publishes guidance for cyber incident response plans that organizations can use as a starting structure.
State what the plan covers in plain terms: which parts of the organization, which systems, and which kinds of event. Define an incident so that staff outside IT can recognize one.
Example wording: A cybersecurity incident is any event that has compromised, or is likely to compromise, the confidentiality, integrity, or availability of our systems or information. This plan applies to all company systems, cloud services, and information held by suppliers on our behalf.
A cybersecurity incident is any event that has compromised, or is likely to compromise, the confidentiality, integrity, or availability of our systems or information. This plan applies to all company systems, cloud services, and information held by suppliers on our behalf.
Say what the plan does not replace. The disaster recovery and business continuity plans stay separate documents, and the recovery handover section records where each takes over.
List each role with the people who hold it. The most valuable lines in the whole plan are the ones that say who may act without asking.
Runs the response and holds the single current version of the facts.
Directs investigation and containment.
Isolates, rebuilds, and restores.
Approves actions that affect customers, revenue, or public statements.
Advises on notification, privilege, and contracts.
Prepares messages for staff, customers, and media.
Assesses whether personal information is involved.
Keeps the incident log of events, decisions, and actions, each with its time.
Example wording: The incident lead may isolate any workstation or internal server, and disable any standard user account, without further approval. Taking a customer-facing system offline requires the executive sponsor, or the deputy if the sponsor cannot be reached within 15 minutes.
The incident lead may isolate any workstation or internal server, and disable any standard user account, without further approval. Taking a customer-facing system offline requires the executive sponsor, or the deputy if the sponsor cannot be reached within 15 minutes.
Write an equivalent sentence for each hard decision. Each is difficult to make well at 3 a.m. with incomplete facts, and each can be made on an ordinary afternoon.
Name who can order it, and say whether the answer changes for systems that customers use directly.
Executives are frequent targets, and staff hesitate to act against a senior person without clear authority.
A managed service provider or software vendor with access may be the route in, and suspending it has contractual and operational consequences.
A trigger tied to severity level avoids a debate about whether the situation is serious enough.
Response costs arrive before any budget process can approve them, so the plan sets who can authorize them and up to what amount.
This is a board-level decision in most organizations, and the board should have discussed it before it is real.
The plan names who decides on manual processes, alternative suppliers, and which customers are told first.
For each, the plan needs one sentence naming the role, and one naming who decides if that person cannot be reached. The discussion that produces those sentences is often more valuable than the document.
Define levels by business impact, in words a non-technical manager can apply in the middle of the night.
Add the rule for changing a level. Example wording: The incident lead reviews the severity level whenever new facts arrive, and raises it at once if personal information, a privileged account, or more than one system is found to be involved.
The incident lead reviews the severity level whenever new facts arrive, and raises it at once if personal information, a privileged account, or more than one system is found to be involved.
Give staff one way to report a suspected incident, and say what happens next.
Example wording: Report any suspected incident to the service desk by phone. The service desk passes the report to the on-call security contact within 15 minutes. The on-call contact assesses it, assigns a severity level, and declares an incident where the level is medium or higher.
Report any suspected incident to the service desk by phone. The service desk passes the report to the on-call security contact within 15 minutes. The on-call contact assesses it, assigns a severity level, and declares an incident where the level is medium or higher.
Declaration matters because it is the trigger. It starts the notifications, the meeting rhythm, and the incident log for that level. A plan that leaves declaration vague produces incidents that are handled informally for a day before anyone is told.
Assume email and chat may be unavailable or read by the attacker.
Name the messaging or conferencing service the team will use, hosted outside the corporate environment and tested in advance.
The incident lead keeps the current summary. Everyone else refers to it.
Set by severity level, as in the table above.
Name the people authorized to talk to customers, regulators, and media.
Keep short pre-approved wording for staff and customers, to be completed with facts on the day.
Example wording: No member of staff other than the communications lead or the executive sponsor makes statements about an incident to customers, suppliers, or the media.
No member of staff other than the communications lead or the executive sponsor makes statements about an incident to customers, suppliers, or the media.
Example holding statement for staff: We are responding to a cybersecurity incident that affects some of our systems. The response team is working on it now. Updates will come through [channel], and the next one is due at [time]. Pass any question from a customer, supplier, or journalist to [name] without answering it yourself.
We are responding to a cybersecurity incident that affects some of our systems. The response team is working on it now. Updates will come through [channel], and the next one is due at [time]. Pass any question from a customer, supplier, or journalist to [name] without answering it yourself.
A holding statement says what is known, when the next update comes, and where questions go. It leaves out the cause, the scale, and any promise that data is safe, because none of those is established in the first hours.
Describe the flow in a page or two, so everyone shares one picture. The cyber incident response guide covers each phase in depth.
State the principles that guide the technical work: preserve evidence before changing systems, contain at once where harm is spreading and otherwise establish scope first, and record every action with its time.
Example wording: The technical lead may begin containment before the investigation is complete where an attacker is active or damage is spreading. In all other cases the technical lead confirms the scope with the incident lead before accounts are disabled or systems are isolated.
The technical lead may begin containment before the investigation is complete where an attacker is active or damage is spreading. In all other cases the technical lead confirms the scope with the incident lead before accounts are disabled or systems are isolated.
One timed record of events, decisions, and actions, kept from declaration.
Who may collect evidence, where it is stored, and how access to it is recorded.
Which logs exist, how long they are kept, and where copies are held outside the production environment.
When counsel is engaged, so that advice and some investigation records can be protected where the law allows.
Example wording: The incident lead appoints a scribe at declaration. The scribe records each decision, who made it, and the time, in the incident log.
The incident lead appoints a scribe at declaration. The scribe records each decision, who made it, and the time, in the incident log.
List each outside party, the reason to contact them, and who makes the call: the incident response provider, the cyber insurer, legal counsel, key IT suppliers, the bank, the national cyber agency, police, and regulators.
For the response provider, record the steps to invoke the incident response retainer. For regulators, record who assesses whether a notification duty applies and the timeframes involved. Where personal information is involved, the data breach response plan carries that assessment.
Example wording: The incident lead calls the incident response provider for any incident rated high or critical. The executive sponsor notifies the insurer within the period the policy sets. Legal counsel assesses whether a regulator must be notified and advises the executive sponsor, who approves the notification.
The incident lead calls the incident response provider for any incident rated high or critical. The executive sponsor notifies the insurer within the period the policy sets. Legal counsel assesses whether a regulator must be notified and advises the executive sponsor, who approves the notification.
Incident response, disaster recovery, and business continuity plans answer different questions, and a cyber incident can trigger all of them.
Disaster recovery plans usually assume backups and identity systems can be trusted. After an intrusion that may be false. The incident response plan should name who confirms that restoration is safe.
Example wording: No system is restored to production until the technical lead confirms that the entry point is closed and the backup predates the intrusion.
No system is restored to production until the technical lead confirms that the entry point is closed and the backup predates the intrusion.
Say who calls the review, how soon, and what happens to its findings. The cyber incident response guide sets out what a post-incident review covers. The plan only has to make sure one is held and acted on.
Example wording: The incident lead holds a review within two weeks of closing any incident rated medium or higher. The review records what delayed the response, which parts of this plan were used, and what should change. Each action has an owner and a date, and the plan owner reports open actions to the executive sponsor each month until they are closed.
The incident lead holds a review within two weeks of closing any incident rated medium or higher. The review records what delayed the response, which parts of this plan were used, and what should change. Each action has an owner and a date, and the plan owner reports open actions to the executive sponsor each month until they are closed.
Include the plan itself in the review. If the team worked around a section, the section is wrong, and the review is the moment to rewrite it.
The contact list is the part of the plan used most and trusted least. It sits in an appendix so it can be replaced without reissuing the plan.
Give each role its named person and deputy, with a mobile number and a contact route that does not depend on corporate email.
Record the response provider’s incident line, the insurer’s claims line with the policy number, legal counsel, the bank’s fraud team, and out-of-hours numbers for key suppliers.
Print the date of the last check on the list, and check every number each quarter.
Keep the list with the printed plan and on the phones of the people named in it.
Example entry: Incident lead: [name], mobile [number], personal email [address]. Deputy: [name], mobile [number]. Last verified: [date].
Incident lead: [name], mobile [number], personal email [address]. Deputy: [name], mobile [number]. Last verified: [date].
An organization with one or two IT staff, or an outsourced provider, does not need every section above. It needs the same decisions on fewer pages.
A workable small-organization plan fits on two or three pages and covers:
Printed, signed by the owner, and kept where staff can find it, this covers most of what a longer plan achieves.
A plan is increasingly something outsiders ask to see.
Cyber insurers ask about incident response plans in applications and at renewal. A policy may require prompt notification, use of approved response firms, and consent before certain costs are incurred. The plan should carry the policy number, the insurer’s notification route, and those conditions, so they are followed under pressure. The incident response retainer guide covers getting a provider approved by the insurer in advance.
Regulators look at preparation when they assess an incident. Whether an organization had a documented, tested plan is relevant to whether it took reasonable steps. Sector rules for financial services and critical infrastructure go further and expect a maintained and exercised capability.
Customers include response and notification obligations in contracts. Timeframes for telling a customer about an incident affecting their data are often shorter than any legal requirement. A list of those obligations belongs in the plan’s appendix.
Auditors and certification bodies check for a plan, evidence that it is reviewed, and evidence that it is tested.
Keeping a simple record serves all of them: the plan’s version history, the dates of exercises, who attended, and what changed afterward.
A named person is responsible for keeping the plan current.
Every copy shows its version and date, so nobody works from an old one.
The owner updates the plan after new systems, new suppliers, staff changes in named roles, and every incident.
The people named in the plan, including executives, rehearse it once a year. The cyber tabletop exercise guide has a script that can be run as written.
Anyone given a role is briefed on it before they need it.
ThreatDefence reviews incident response plans as part of our incident response retainer and our readiness review. We check roles, escalation contacts, logging, and containment authority, and report what would slow a response today.
The retainer also includes incident-specific runbooks and a tabletop exercise.
Under our 24x7 SOC service, escalation contacts and pre-approved containment actions are agreed at onboarding, so the plan and the monitoring service work from the same decisions.
Experiencing a breach?
Our incident response team answers 24x7, with or without a retainer.
Explore Incident Response and DFIR
Ask about an incident response readiness review, including a review of your plan, contacts, logging, and containment authority.
CountryAustraliaUnited StatesNew ZealandUnited KingdomCanadaSingaporeOtherI'm an MSP, MSSP, or reseller
Δ
A plan covers purpose and scope, roles and authority, severity levels, reporting and activation, communication, the response process, evidence and records, external parties, recovery handover, review, and a contact list. The lines that matter most say who may act without asking, such as who can disconnect a production system. Technical steps for specific incident types sit in separate playbooks that the plan lists.
About eight to ten pages plus a contact list appendix for a mid-sized organization, and two or three pages for a small one. Roles and authority and the response process take one to two pages each, and most other sections take a page or less. Put a one-page summary first, with how to declare an incident, the severity table, and the key phone numbers.
One named owner, usually the security lead or IT manager, maintains the incident response plan. Executives approve it because it assigns decision rights and spending authority, while legal, communications, and privacy leads review their own responsibilities. The owner also updates the plan after every incident and exercise, and reissues the contact list whenever it changes.
Review the whole plan once a year, and straight after any incident, exercise, new system, new supplier, or change of person in a named role. Check the contact list every quarter, because phone numbers go out of date faster than anything else in the document. Record each review in the version history, which auditors and insurers ask to see.
An incident response plan covers stopping the attacker and establishing what happened. A disaster recovery plan covers restoring systems and data after any failure, and it usually assumes that backups and identity systems can be trusted. After an intrusion that assumption may be false, so the incident response plan names who confirms that restoration is safe before disaster recovery begins.
Yes. Two or three pages are enough: what to do first, who to call, who decides, how the team talks if email is down, where the backups are, who may have to be told, and support numbers for key suppliers. Name one person with authority to shut systems down and spend money, and one deputy. Print it and keep it where staff can find it.
It depends on the sector. In Australia, APRA’s prudential standard CPS 234 requires regulated banks, insurers, and superannuation funds to maintain information security response plans and to review and test them every year. Other organizations meet the expectation indirectly. Privacy regulators look at whether reasonable steps were taken, and cyber insurers and customer contracts commonly ask for a documented and tested plan.
The plan sets roles, decision authority, severity levels, and communication for any incident, and it changes when the organization changes. A playbook gives the steps for one incident type, such as ransomware or a compromised mailbox, from trigger to closure. The plan lists the playbooks and stays short by leaving their detail out.
Incident Response Playbooks
Cyber Tabletop Exercise
Incident Response Retainer