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 retainer is an agreement with a specialist provider that is signed before an incident occurs. It gives an organization a defined route to responders, with access, contacts, and commercial terms already settled.The value of a retainer shows in the first hours of an incident. This guide starts there, with the same incident handled with and without one, then covers the models, the wording that matters, and how to compare providers.
An IT manager is woken by an alert. Files on a file server are being encrypted.
Nothing in the left-hand column is about skill. Every delay is a decision or an arrangement that could have been made months earlier. That is what a retainer buys.
A qualified responder is committed to start work within a stated time, at any hour.
Liability, confidentiality, rates, and data handling are agreed once, without pressure.
Accounts, tools, and approvals are in place, so responders can connect and collect evidence immediately.
Network layout, critical systems, logging, and key contacts are recorded at onboarding.
The agreement states who may declare an incident, and which containment actions responders may take without asking.
A plan review, runbooks, and exercises make the response faster when it comes.
A retainer covers response. Monitoring is a separate service, and the section on retainers and managed services below explains how the two fit together.
The call that invokes a retainer goes faster when the caller has a few facts written down. None of them needs to be certain, and the responder will ask for the rest.
Describe the alert, ransom note, or report that started it, with the time and the time zone.
Name the systems, accounts, and sites known to be involved, and the business services that depend on them.
List anything shut down, disconnected, reset, restored, or deleted since discovery, because each action changes the evidence.
Give the name and mobile number of the person who can approve containment and spending.
Offer a phone number or channel outside the affected environment.
Until the responder advises otherwise, the safe defaults are to disconnect affected systems from the network and leave them powered on, to stop restoring or wiping anything, and to keep discussion of the incident off corporate email and chat.
Write the time of the call and the responder’s name in the incident log. The response-time commitment in the contract is measured from this call.
The comparison above covers the first day. A serious incident runs for weeks, and the provider’s work changes with each phase, along with what it needs from the customer.
A responder takes the call and agrees immediate steps with the caller. Remote access is established and forensic tooling is deployed to the affected systems, then to the rest of the environment. Evidence that could be lost, such as memory and short-lived logs, is captured first.
The priority is scope. Responders search every system for the attacker’s traces, identify the accounts and hosts involved, and confirm the entry point. Containment runs alongside: accounts disabled, hosts isolated, external addresses blocked. The provider gives regular situation updates, usually on a call with the incident lead and executive sponsor.
With the attacker contained, work divides. Forensic analysis continues, to establish what was accessed and whether data left. Recovery begins on systems that have been validated as clean. The provider advises on the restore order, credential resets, and what must be rebuilt.
Recovery completes. Monitoring continues, watching for any sign that the attacker has kept or regained access. Findings are prepared for legal counsel, the insurer, and any notification assessment.
The provider delivers a written report and holds a review meeting that turns its recommendations into owned actions.
Most incidents pass through these phases at different speeds. A single compromised account may pass through every phase in two days. A network-wide intrusion takes the full month and sometimes longer.
The written report is the lasting product of a response. It is read by executives, insurers, lawyers, regulators, and sometimes a court, often months later by people who were not involved. Its quality is a fair test of a provider.
Every report carries an executive summary, a root cause, and the actions taken. The cyber incident response guide covers the post-incident review those feed. The parts below are the ones that separate a careful report from a template.
Each significant event carries its time and the record it rests on, from first attacker activity to closure.
The report lists every account and system found to be affected, and says how the list was established.
The report states what was accessed or taken, and how sure the investigators are of each finding.
The report names the logs that were missing, the systems that could not be examined, and the questions left open. A report with no limitations section has usually left something out.
Each recommendation is specific, prioritized, and traceable to something the investigation found.
The addresses, file names, and other traces of the attacker are listed, so they can be searched for again.
Ask a prospective provider for a sample report with client details removed. It shows more about how they work than any description of their service.
Two retainers at the same price can differ widely. The comparison that matters is what happens in the first four hours.
Onboarding is the part of a retainer that happens before anything goes wrong. A provider’s speed in an incident depends heavily on what the customer supplied here, and a thorough onboarding usually includes the following.
The output is a short document both sides hold: who to call, how responders connect, what they may do, and where the evidence is. A retainer where onboarding was skipped performs much like having no retainer at all.
Many retainers include hours or named activities for preparation. Used well, these reduce the chance of needing the emergency part.
Executives and technical leads work through a scenario with the provider’s responders, which tests the plan and introduces the people who will work together in a real incident. The cyber tabletop exercise guide has a script that can be run as written.
The provider reads the incident response plan and the playbooks from outside, and marks the steps its responders could not carry out as written.
A forensic sweep of the environment looks for signs of an existing intrusion.
A yearly repeat of the onboarding logging check catches sources that were added or dropped since.
A timed test covers specific steps, such as deploying forensic tools to every endpoint or isolating a site.
The provider reports the intrusion methods it is seeing, and what to check for.
Response-time wording is where retainers differ most. Establish which of these the commitment means.
A 15-minute acknowledgment followed by investigation the next day is a slow response with a fast receipt. The useful measure is the time until someone with the skills and the access is working on the problem.
Response time gets the attention when a retainer is being agreed. Scope decides whether the retainer applies to the incident at all.
Check that every legal entity, subsidiary, and country of operation is named. An incident at an unlisted subsidiary can fall outside the agreement.
Confirm that cloud tenants, hosted applications, and systems run by a managed service provider are covered, and who can authorize responder access to each.
Some retainers cover intrusions and ransomware and treat insider investigations, payment fraud, or industrial control systems as separate work.
Legal advice, notification mailings, call handling for affected people, and public relations normally come from other firms. Identify who supplies each before it is needed.
The contract should say where collected evidence is stored, who can access it, how long it is kept, and how it is returned or destroyed.
Ask how an acquired company or a new cloud platform is added, and whether the fee changes.
The annual fee is the smallest part of what a serious incident costs. Compare the terms that apply once it starts.
A major incident can use many times the hours a retainer includes. Check the hourly rate beyond them, and whether it is fixed for the term.
Some agreements charge more at night, on weekends, or for work at the site. Ask for the full rate card.
Some providers bill a minimum number of hours each time the retainer is invoked, which matters when the alarm turns out to be false.
Ask whether forensic and monitoring tools deployed during an incident are included or licensed separately per endpoint.
Travel, evidence storage, and specialist work such as data recovery are often billed on top.
Confirm whether continued monitoring after containment is part of the engagement or a new purchase.
Insurance pays for a response. A retainer delivers one. They need to agree before an incident, or the organization may pay for a response its policy would have covered.
Many policies cover response costs only where the insurer has approved the provider, sometimes from a fixed panel. Before signing a retainer, ask the insurer or broker whether the provider is acceptable, and keep the answer in writing.
Late notification can affect a claim, so the insurer’s notification route belongs in the incident response plan, next to the retainer’s invocation steps.
If the insurer appoints its own forensic firm, a retained provider that knows the environment can still shorten the investigation and carry out recovery alongside it. Agree in advance how the work would divide. One workable split has the insurer’s firm lead the forensic investigation and report to counsel, while the retained provider handles containment, monitoring, and recovery, with evidence shared under counsel’s direction.
A retainer answers the question of who responds. It leaves open the question of who notices. Organizations weighing a retainer should be clear about which problem they have.
A retainer alone suits an organization that already has reliable detection: an internal security team or a monitoring service that will spot an intrusion and make the call. The retainer adds forensic depth and extra hands.
Where nobody is watching at night, a retainer has a gap. The call is made when someone notices, which for ransomware usually means when systems stop working. By then the attacker has finished.
Combining monitoring and response under one provider closes that gap. The team that sees the first alert is the team that investigates and contains, with the environment’s history already in front of it. Response-time commitments are typically shorter for this reason, since no handover happens at the start.
The deciding question is this: if an attacker signed in at 2 a.m. on a Sunday, who would know, and when?
The arrangements made at onboarding stop matching the environment unless someone checks them. These are the parts that go stale.
Keep a copy of the invocation steps that does not depend on the network, and replace it whenever the steps change.
Accounts created at onboarding are disabled by inactivity rules, password expiry, and directory cleanups. Sign in with each one on a schedule, and again after any change to the identity platform.
Update the escalation list on both sides whenever a named person changes role or leaves.
Tell the provider about new sites, cloud tenants, acquisitions, and supplier changes when they happen.
Confirm at each policy renewal that the insurer still accepts the provider.
Walk through the onboarding document with the provider once a year and correct what has changed.
ThreatDefence offers an incident response retainer with priority access to our DFIR team, a response-time SLA of 2 hours, and a 30-minute SLA when combined with our 24x7 SOC service.
The retainer includes an incident response plan review, incident-specific runbooks, a cyber resilience assessment, a tabletop exercise, a named incident coordinator, and a post-incident report.
Our responders deploy our own SecOps platform, so no third-party tool costs are added to an engagement. We work alongside insurers and legal counsel. An incident response retainer is also included in our 24x7 SOC service.
Experiencing a breach?
Our incident response team answers 24x7, with or without a retainer.
Explore Incident Response and DFIR
Discuss incident response retainers, readiness reviews, and 24x7 monitoring for your organization.
CountryAustraliaUnited StatesNew ZealandUnited KingdomCanadaSingaporeOtherI'm an MSP, MSSP, or reseller
Δ
The incident lead and deputy named in the incident response plan should be able to invoke it without asking anyone first. Put their names on the retainer’s contact list, state in the plan that invoking it needs no purchase order, and set the spending level at which an executive must be told. A retainer that only one person can activate fails when that person is on leave.
The fee follows the model. A standby retainer costs little or nothing up front and bills time when used. A prepaid retainer charges an annual fee for a block of hours and a guaranteed response time. A retainer included in a monitoring service is part of that subscription. The larger costs arrive during an incident: the hourly rate beyond the included hours, tooling licensed per endpoint, travel, and monitoring during recovery.
Yes, when it settles rates, contract terms, contacts, and the activation route in advance. That removes the contract and purchase order delay at the start of an incident. Check the terms before relying on it. Standby agreements often promise best-effort availability, with no guaranteed time for a responder to start. Many also skip onboarding, so the provider arrives with no access and no knowledge of the environment.
The contract decides. Hours can expire at the end of the term, roll over into the next one, or convert to readiness work such as a tabletop exercise, a plan review, a compromise assessment, or a response drill. Ask which activities qualify and the date by which hours must be booked. Scheduling the readiness work at the start of the year means the balance is used on purpose.
Yes, in most cases. Insurance pays for a response and a retainer delivers one. A policy does not reserve a responder, and a panel firm appointed when a claim is made starts with no knowledge of the environment. Before signing, ask the insurer or broker in writing whether the retained provider is acceptable, because many policies cover response costs only for approved firms.
Managed detection and response watches the environment and acts on alerts every day. A retainer is used only when an incident is declared, and brings forensic investigation, containment, and recovery support. The gap between them is detection: a retainer does nothing until someone makes the call. Where one provider supplies both, the analysts who raise the alert begin the response without a handover.
Measure the commitment to the moment a qualified responder with access is investigating. An acknowledgment within 15 minutes means little if the investigation starts the next day. Ask whether the clock starts at the call or after onboarding steps, whether the commitment applies at any hour, and whether a first containment action is included. Commitments are shorter where the provider already monitors the environment.
Only where the contract names it. Retainers cover named legal entities and environments, so list subsidiaries, overseas offices, and acquired companies at signing and after each acquisition. A supplier’s own environment sits outside the retainer, because the customer cannot authorize access to it. The provider can still investigate what the supplier’s accounts and connections did inside the organization’s own systems.
Incident Response Plan
Cyber Tabletop Exercise
Incident Response and DFIR Services