
Incident response services: agree the help before you need it
Almost every incident response plan has a line like “call the incident response provider”. Whether that provider answers, how quickly, and whether they already know your environment is not in the plan but in the contract behind it. This is about that contract for incident response services: what you agree in advance, so you do not have to negotiate it on the worst day of the year.
An incident response plan says who you call. A retainer makes sure that provider answers, already knows your environment and starts within an agreed time.
The most important terms are not about money but about time and authority: when the clock starts, who may declare an incident and what the provider may shut down.
Check before you sign that your cyber insurer accepts the provider. Forensics is a specialism of its own; we isolate, supply clean hardware and restore.
Your plan names who you call; the contract decides whether they answer
What to do in the first hour is covered in our article on the first hour after an incident. This article is about one line in that runbook: outside help. Without an agreement in advance, you are a new customer at that moment. There has to be a non-disclosure agreement first, an engagement letter, a data processing agreement and a walk-through of your network, while the servers are encrypted.
Incident response services agreed in advance, usually called a retainer, bring that work forward. The paperwork is signed, the provider knows your environment, and there is a number with an agreed response time. Whether it is worth it depends on how dependent you are on IT, and whether someone in your own organisation or at your IT partner can already lead an incident.
The test is simple: read the line in your incident response plan that names outside help, and ask what happens if you ring that number at three in the morning. If the answer is “we will see”, there is no agreement yet.
Three forms of incident response services, and what drives the difference
Incident response can be agreed in advance at three levels, and each buys something different:
- An availability agreement. A number that is answered around the clock and a commitment that someone calls back within an agreed time. Preparation only happens during the incident.
- An onboarded service. On top of that, an introduction to your environment: network diagram, key systems, where the logs are, who decides. Work then starts straight on the substance.
- A bank of hours. Hours you commit to in advance and use during an incident. Agree what happens to unused hours; in good contracts they can go towards an exercise or an assessment, so they do not simply expire.
What drives the difference in price is always the same: how short the response time is, whether it also applies out of hours, how large and spread out your environment is, whether someone must be able to come on site, and how deep the preparation goes. Compare quotes on those points, not on the total.
Response times: what exactly the clock measures
“Within four hours” means nothing until it is clear from when. Agree three separate times per severity level, because each means something different:
- To the first substantive conversation with someone who can assess the incident, not with a switchboard.
- To remote work starting in your environment. That depends on access arranged in advance.
- To someone on site, if needed. Name the locations this applies to.
Agree too when the clock starts: at your call, or at the provider’s confirmation. And who may declare an incident: a list of names, so not every employee can trigger an expensive engagement, but not only the managing director who is on holiday either.
What must be ready before the incident
Most time in an incident is not lost to the investigation but to searching. A retainer only earns its keep if this is arranged in advance:
- Signed paperwork: the engagement, confidentiality and, because the provider will see personal data, a data processing agreement.
- A current contact list with management, IT, your IT partner, your insurer and your software vendors, on paper and outside your own environment.
- A break-glass account with admin rights that does not depend on the normal domain, so there is access if the usual accounts have been taken over.
- Logs that exist and are kept long enough: from the firewall, endpoint security and Microsoft 365. What was not recorded cannot be investigated afterwards.
- Knowing where the backup is and whether it can be reached independently of the network.
Have the provider check this at the start and agree that it is updated every year. Ring the number once on an ordinary Tuesday, to know that it works.
Who decides, and what the provider may do on its own
In the middle of an incident some decisions cannot wait: blocking an account, taking a server off the network, closing a site. Write into the contract what the provider may do on its own and what needs your approval first. Either is defensible, but it must be fixed in advance, with names and deputies.
Some decisions never sit with the provider. Whether you consider a ransom, what you tell customers and the press, and whether and when you report a breach are decisions for senior management. Under UK GDPR, a personal data breach that poses a risk is reported to the ICO within 72 hours. In the UK, the NCSC also runs an assured Cyber Incident Response scheme, which is a useful starting point when you are choosing a provider. The provider supplies the facts; you report.
Your insurer and your provider have to fit together
If you have cyber insurance, this is the trap that costs the most. Many policies work with their own panel of response firms and ask you to call the insurer’s helpline first. If you bring in a different provider yourself, you risk those costs not being covered.
So put the two side by side before you sign: does the insurer accept the provider in your retainer, and if not, how do they work together? Your incident response plan should then contain one order, so nobody has to choose in the moment who gets called first.
Evidence, reporting and what you receive afterwards
An incident does not end when the systems are running again. Agree what you receive afterwards:
- A timeline of what happened and what was done, usable for the notification, the insurer and your own review.
- How evidence is preserved: which copies are made, who holds them and for how long, so they remain usable if it comes to a police report or a dispute.
- Recommendations in order of priority, not a list of everything that could be better.
- Where your data stays during and after the investigation, and when it is deleted.
Also agree how the provider works with your own IT team or IT partner. Investigation and recovery run at the same time, and without one point of contact the recovery overwrites exactly the evidence the investigation needs.
Where our work stops
What we do. Our emergency line is answered day and night. In a cyber incident we take the affected environment off the network without damaging the evidence, put clean hardware in place and run the recovery, so you can keep working while the investigation continues. For the environments we manage, we agree response times per severity level and keep the contact list, break-glass access and logs in order.
What we do not do. We do not carry out forensic investigations: that is a specialism of its own, and we work alongside the firms that do it. We are not an insurer and do not assess what your policy covers. We are not lawyers and do not review contracts. We do not negotiate with attackers or decide on ransom. And we do not report to a regulator on your behalf; we supply the facts you need to do so.
Questions we get about this
The five that come up most often.
What are incident response services?
Incident response services are the outside help an organisation calls in during a security incident: assessing what is happening, containing it, investigating and supporting recovery. They can be bought at the moment of need or agreed in advance with set response times. Agreeing them in advance means the paperwork and preparation are done before the incident.
What is an incident response retainer?
A retainer is a contract you sign in advance with a provider who will help you in an incident. It sets out availability, response times and often onboarding to your environment, so work can start immediately. Sometimes it includes a bank of hours that can also be used for an exercise.
What should an incident response contract include?
Response times per severity level and when the clock starts, who may declare an incident, what the provider may shut down and what needs approval. Also onboarding to your environment, how evidence is preserved, what you receive afterwards and what happens to unused hours. Have the contract reviewed by a lawyer before you sign.
Does my incident response provider have to be the one my insurer uses?
Not necessarily, but the two must fit together. Many policies have their own panel of response firms and do not always cover the cost of a different provider. Check your retainer against your policy before signing, then put one order in your plan.
Do you carry out forensic investigations after a cyber attack?
No. Forensics is a specialism of its own, and we work alongside the firms that do it. We isolate the affected environment without damaging the evidence, supply clean hardware and run the recovery, so you can keep working while the investigation continues.
Further reading
What this agreement connects to.
Shall we test your plan against reality?
Send us the line from your incident response plan that names outside help. We will tell you what is still missing in the contact list, break-glass access and logs, and what we can do about it ourselves.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.