Incident Response Retainer: What It Covers and How to Choose
Skip to content

Incident Response Retainer

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.

Saturday, 2 a.m.: The Same Incident Twice

An IT manager is woken by an alert. Files on a file server are being encrypted.

TimeWithout a retainerWith a retainer
02:10Searches the web for incident response firms.Calls the number in the incident plan.
02:40Reaches an answering service. A sales contact will call in business hours.A responder is on the phone, asking which systems are affected.
03:30Leaves messages with two more firms.The responder has remote access through an arrangement set up at onboarding, and is collecting evidence.
08:00Still no responder. Considers shutting everything down.First findings: the account used, the likely entry point, and which systems to isolate.
10:00A firm responds. It needs a signed contract and a purchase order before starting.Containment is under way. Backups are confirmed intact.
14:00Legal reviews the contract. The insurer says the firm is not on its approved panel.The insurer has been notified by the route agreed in advance. It approved the provider before the retainer was signed.
MondayWork begins. The attacker has had two more days.Recovery of priority systems has started.

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.

What You Are Buying

Availability

A qualified responder is committed to start work within a stated time, at any hour.

A signed contract

Liability, confidentiality, rates, and data handling are agreed once, without pressure.

Access already arranged

Accounts, tools, and approvals are in place, so responders can connect and collect evidence immediately.

Knowledge of the environment

Network layout, critical systems, logging, and key contacts are recorded at onboarding.

Agreed authority

The agreement states who may declare an incident, and which containment actions responders may take without asking.

Readiness work

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.

Making the First Call

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.

What was seen, and when

Describe the alert, ransom note, or report that started it, with the time and the time zone.

What is affected

Name the systems, accounts, and sites known to be involved, and the business services that depend on them.

What has been done

List anything shut down, disconnected, reset, restored, or deleted since discovery, because each action changes the evidence.

Who decides

Give the name and mobile number of the person who can approve containment and spending.

How to talk

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.

How a Response Unfolds Under a Retainer

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.

The First Hours

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.

Days One to Three

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.

Days Four to Seven

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.

Weeks Two to Four

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.

Afterward

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.

What the Final Report Should Contain

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.

A timeline with evidence

Each significant event carries its time and the record it rests on, from first attacker activity to closure.

Scope and method

The report lists every account and system found to be affected, and says how the list was established.

Data impact with confidence levels

The report states what was accessed or taken, and how sure the investigators are of each finding.

Limits of the investigation

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.

Recommendations tied to findings

Each recommendation is specific, prioritized, and traceable to something the investigation found.

Indicators

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.

Retainer Models Compared

ModelYou payYou getWatch for
Prepaid hoursAn annual fee that buys a block of hours.Guaranteed response, and hours to draw on.Whether unused hours expire or convert to other work.
StandbyLittle or nothing up front. Time is billed when used.Agreed rates and terms, with a faster start than no agreement.Whether response time is guaranteed or best effort.
Included in a serviceA subscription, such as managed detection or a SOC service.Response by the team already monitoring the environment.Limits on hours or incident types.
Insurer panelCovered under the cyber policy.A responder appointed when a claim is made.No prior knowledge of the environment, and little choice of firm.

Two retainers at the same price can differ widely. The comparison that matters is what happens in the first four hours.

What Onboarding Covers

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.

1
Contacts and decision makersBoth sides exchange names, roles, and phone numbers, with deputies. The customer names someone who can approve isolation of systems and spending at any hour.
2
Environment reviewThe customer supplies an asset list and network diagrams: what systems exist, which matter most, who owns each, and how sites, cloud environments, and suppliers connect. The provider learns the layout from them.
3
Logging reviewThe provider checks which logs are collected, where, and for how long. Remote access, firewall, directory, and cloud logs need to be kept long enough to cover an intrusion that began weeks ago, and gaps found here are far cheaper to fix than gaps found during an incident.
4
Tool checkThe provider confirms whether the existing endpoint and network tools can support an investigation, what it would deploy, and how: a software deployment system, or another agreed way to install forensic agents across the fleet quickly.
5
Access setupAccounts for responders in the directory, the cloud tenant, the endpoint tool, and the firewall are created in advance and tested end to end.
6
Authority agreementBoth sides record which containment actions responders may take without asking, and which need approval.
7
A separate communication channelThe customer sets up a messaging or conferencing service outside the corporate environment, for when email and chat cannot be trusted.
8
Supplier contactsThe customer lists the managed service provider, the internet provider, and key software vendors, with out-of-hours numbers.
9
Plan reviewThe provider reads the incident response plan against how it works, and the retainer’s invocation steps are written in.
10
A test callSomeone places a real call to the incident line, to confirm the route works out of hours.

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.

Readiness Work Through the Year

Many retainers include hours or named activities for preparation. Used well, these reduce the chance of needing the emergency part.

Tabletop exercise

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.

Plan and playbook review

The provider reads the incident response plan and the playbooks from outside, and marks the steps its responders could not carry out as written.

Compromise assessment

A forensic sweep of the environment looks for signs of an existing intrusion.

Logging and visibility review

A yearly repeat of the onboarding logging check catches sources that were added or dropped since.

Response drills

A timed test covers specific steps, such as deploying forensic tools to every endpoint or isolating a site.

Threat briefings

The provider reports the intrusion methods it is seeing, and what to check for.

Reading the Response-Time Clause

Response-time wording is where retainers differ most. Establish which of these the commitment means.

The contract promisesWhat it measuresAsk
AcknowledgmentTime until someone answers or returns the call.Is that person a responder, or a call handler?
Remote responseTime until a responder is investigating.Does the clock start at the call, or after onboarding steps?
On-site responseTime until a responder is at the site.Which locations are covered, and is travel billed?
ContainmentTime until a first containment action.Is authority to act agreed in advance?

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.

Reading the Scope Clause

Response time gets the attention when a retainer is being agreed. Scope decides whether the retainer applies to the incident at all.

Entities and locations

Check that every legal entity, subsidiary, and country of operation is named. An incident at an unlisted subsidiary can fall outside the agreement.

Environments

Confirm that cloud tenants, hosted applications, and systems run by a managed service provider are covered, and who can authorize responder access to each.

Incident types

Some retainers cover intrusions and ransomware and treat insider investigations, payment fraud, or industrial control systems as separate work.

Excluded 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.

Evidence handling

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.

Changes during the term

Ask how an acquired company or a new cloud platform is added, and whether the fee changes.

Costs Beyond the Fee

The annual fee is the smallest part of what a serious incident costs. Compare the terms that apply once it starts.

Overage rate

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.

Out-of-hours and on-site rates

Some agreements charge more at night, on weekends, or for work at the site. Ask for the full rate card.

Minimum charge

Some providers bill a minimum number of hours each time the retainer is invoked, which matters when the alarm turns out to be false.

Tooling

Ask whether forensic and monitoring tools deployed during an incident are included or licensed separately per endpoint.

Expenses

Travel, evidence storage, and specialist work such as data recovery are often billed on top.

Monitoring during recovery

Confirm whether continued monitoring after containment is part of the engagement or a new purchase.

Cyber Insurance and the Retainer

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.

Questions That Separate Providers

Speed

  • Who answers at 3 a.m., and what can they do?
  • How long until a responder is investigating, and what must be in place for that?

Capability

  • How do you investigate cloud and identity incidents, as well as endpoints and networks?
  • Which tools do you deploy, and how long does deployment take across a whole fleet?
  • Do you monitor the environment during recovery, and who does it?
  • Can your evidence handling support legal proceedings?

Commercial Terms

  • What happens when the hours run out?
  • What is charged in addition to time?
  • How do you work with insurers and legal counsel?

Readiness

  • What do you do in the first month to learn our environment?
  • What readiness work is included each year?
  • Who will lead our response, and will we meet them beforehand?

Retainer or Managed Service

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?

Keeping the Retainer Ready

The arrangements made at onboarding stop matching the environment unless someone checks them. These are the parts that go stale.

The offline copy

Keep a copy of the invocation steps that does not depend on the network, and replace it whenever the steps change.

Responder accounts

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.

Contacts

Update the escalation list on both sides whenever a named person changes role or leaves.

Scope

Tell the provider about new sites, cloud tenants, acquisitions, and supplier changes when they happen.

The insurer’s approval

Confirm at each policy renewal that the insurer still accepts the provider.

The yearly review

Walk through the onboarding document with the provider once a year and correct what has changed.

Incident Response Retainers With ThreatDefence

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.

The case board in the ThreatDefence portal with cases by stage: new, in progress, waiting approval, resolved and closed

Experiencing a breach?

Our incident response team answers 24x7, with or without a retainer.

Talk to Our Experts

Discuss incident response retainers, readiness reviews, and 24x7 monitoring for your organization.

    I'm an MSP, MSSP, or reseller

    By submitting this form, you accept the terms in our privacy policy.

    Frequently Asked Questions

    Who should be able to invoke the retainer?

    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.

    How much does an incident response retainer cost?

    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.

    Is a zero-cost retainer worth having?

    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.

    What happens to unused retainer hours?

    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.

    Do we need a retainer if we have cyber insurance?

    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.

    What is the difference between a retainer and managed detection and response?

    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.

    How quickly should a retainer provider respond?

    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.

    Can a retainer be used for incidents at a subsidiary or supplier?

    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.