Incident Response Statistics and Why the Pre-Holiday Tabletop Should Test the Handoffs

TU0LZJQA1-U0B3VV05084-10fa14008046-512
Diana Wright Publication date: 19 November, 2026
Education

Most incident response plans read fine on paper. The contact list is current, the escalation path is drawn, and the steps run in order. Then an incident crosses a company line. The client’s cloud host has to pull logs, the software vendor has to confirm what it shipped, and your analyst needs someone at the client to approve taking a server offline. Plans break at the seams between companies, and if you run a client’s security program, you sit at most of them.

The National Institute of Standards and Technology (NIST) now points the same way. Its 2025 revision of the incident response guidance gives its top rating, High, to several outcomes that name other companies outright. In those outcomes, the plan runs with third parties once an incident is declared, people outside the organization get notified, and exercises include suppliers. The holidays test every seam at once. Desks empty at the client and at your shop, and attackers know it: the 2021 Fourth of July weekend attack came through an RMM tool into MSPs and their customers.

So the tabletop you run with a client before the holidays should walk the seams. Who declares an incident, who may act on it, and who tells whom? Your team sits at the table as a named third party. The session ends with two documents, written while the people who own each handoff are still at their desks. One is a call tree with a backup for every role; the other is a signed list of the containment steps your analyst may take alone.

This page collects the primary-source figures behind that position. They include NIST’s own text and priority ratings, the UK government’s survey of incident response plans, breach and claims data from Verizon, IBM, and Coalition, and Cynomi’s State of the vCISO research on provider capacity.

Key statistics

  • Incident response was once “usually completed within a day or two,” and recovery now “often takes weeks or months,” according to NIST Special Publication (SP) 800-61 Revision 3 (NIST, 2025).
  • Only 25% of UK businesses hold a formal plan for incident response, falling to 21% of micro businesses (UK government, 2026).
  • A third party was involved in 55% of breaches at small and medium-sized businesses (Verizon, 2026).
  • The most expensive cost-increasing factor in IBM’s study was supply chain breaches, which added $227,250 to the average breach (IBM, 2026).
  • Initial ransom demands rose 47% year over year, to more than $1 million (Coalition, 2026).
  • Limited headcount is a barrier to offering vCISO services for 26% of providers not yet offering them (Cynomi, 2025).
  • Among MSPs, 44% said at least one in 10 of their clients was hit by a cyberattack in 2025 (Kaseya, 2026).

What NIST SP 800-61 Rev. 3 Changed in Incident Response

Rev. 3 keeps the work of the old phases and changes who owns it. The four-phase NIST incident response life cycle still describes the work, but Rev. 3 moves that work out of a closed loop run by one team and into the six Functions of the NIST Cybersecurity Framework 2.0 (CSF 2.0).

  • Revision 3 of SP 800-61 was published in April 2025, and the final publication supersedes Revision 2 (NIST, 2025).
  • The four-phase loop now carries the caption “previous incident response life cycle model,” drawn when incidents were “relatively rare” and narrow in scope (NIST, 2025).
  • Under that older model, it was realistic to treat incident response “as a separate set of activities performed by a separate team of personnel” (NIST, 2025).
  • Lessons learned should often be shared “as soon as they are identified, not delayed until after recovery concludes” (NIST, 2025).
  • Adopting the CSF 2.0 model is optional, and organizations should use “the incident response life cycle framework or model that suits them best” (NIST, 2025).
  • Govern, Identify, and Protect “are not part of the incident response itself,” which consists of Detect, Respond, and Recover (NIST incident response project).

Table 1 of Rev. 3 maps each phase of the old loop onto CSF 2.0 Functions:

Previous phaseCSF 2.0 Functions (Rev. 3, Table 1)
PreparationGovern, Identify (all Categories), Protect
Detection and AnalysisDetect, Identify (Improvement Category)
Containment, Eradication, and RecoveryRespond, Recover, Identify (Improvement Category)
Post-Incident ActivityIdentify (Improvement Category)

A response that closed in a day or two could live inside one team. An incident that runs for weeks crosses your security operations center (SOC), the client’s cloud host, its software vendor, and its insurer. Each crossing is a seam, and the plan has to say who acts at every one of them.

NIST Incident Response Priority Ratings for Third-Party Handoffs

Rev. 3’s CSF 2.0 Community Profile rates each outcome High, Medium, or Low for incident response. The outcomes below on running the plan with third parties, notifying outside stakeholders, reporting recovery, and exercising with suppliers come out High, while GV.SC-08, which includes suppliers in incident planning, response, and recovery, is rated Medium.

CSF 2.0 outcomeWhat NIST’s text coversRev. 3 priority
ID.IM-02Improvements from “security tests and exercises, including those done in coordination with suppliers and relevant third parties”High
RS.MA-01The plan “is executed in coordination with relevant third parties once an incident is declared”High
RS.CO-02“Internal and external stakeholders are notified of incidents”High
RC.CO-03Recovery progress is “communicated to designated internal and external stakeholders”High
ID.IM-04Incident response plans are “established, communicated, maintained, and improved”High
GV.SC-08“Relevant suppliers and other third parties are included in incident planning, response, and recovery activities”Medium
GV.RR-02“Roles, responsibilities, and authorities” are established, communicated, understood, and enforcedMedium

Section 2.2 of Rev. 3 then names the MSSP directly.

  • Outsourcing “a security operations center [SOC] to a managed security services provider [MSSP]” is one way an organization’s incident handlers can be on contract (NIST, 2025).
  • Framed as “a shared responsibility model,” that arrangement needs the provider’s responsibilities “clearly defined in a contract” (NIST, 2025).
  • The incident response team should know that division of responsibilities, including “information flows, coordination, and authority to act on behalf of the organization” (NIST, 2025).
  • It also includes restrictions on what the provider can do, such as making operational decisions like “immediately deactivating certain services to contain an incident” (NIST, 2025).
  • Once an incident is declared, RS.MA-01’s recommendations include contacting “the organization’s incident response service provider to request assistance” (NIST, 2025).
  • RC.CO-03 recommends following “the rules and protocols defined in contracts for incident information sharing between the organization and its suppliers” (NIST, 2025).
  • Exercises, in ID.IM-02’s note, prepare staff and “critical service providers and product suppliers” for future incident response (NIST, 2025).

Section 2.2 puts who may do what in the contract, and GV.RR-02 asks for the roles to be established and communicated. A tabletop shows whether the client’s plan names anyone on the far side of the seam before an incident tests it.

Incident Response Plan Statistics for Small Businesses

Small clients hold the thinnest plans, and the gaps sit where a provider would have to step in. The UK government’s Cyber Security Breaches Survey (CSBS) measures incident response plans by business size.

  • Formal incident response plans sit with 76% of large and 57% of medium-sized UK businesses, against 21% of micro businesses (CSBS, 2026).
  • Over the past 12 months, 43% of UK businesses identified a cyber breach or attack, rising to 65% of medium-sized businesses (CSBS, 2026).
  • Only 31% of UK businesses have a board member with explicit responsibility for cyber security (CSBS, 2026).
  • Among UK micro businesses, 3% have someone in an IT role looking after cyber security; the role sits mostly with the owner, chief executive, or another senior manager (CSBS, 2026).
  • UK micro businesses with an external cyber security provider rose to 44%, from 39% the year before (CSBS, 2026).
  • Risk assessments are slipping, with 41% of UK small businesses carrying one out, down from 48% a year earlier, against 30% of UK businesses overall (CSBS, 2026).
  • In a survey of 4,400 SMB decision-makers, 45% faced a cybersecurity incident in the past year and 14% faced more than one (ESET, 2026).
  • Confidence runs ahead of results: 87% of US SMBs feel at least slightly confident that their business is cyber resilient (83% in Canada), while 54% of US SMBs had an incident in the past year (ESET North America, 2026).
  • A cybersecurity strategy is reported by 83% of SMBs, yet those with plans were just as likely to suffer a breach as those without (CrowdStrike, 2025).

If your book looks like the UK survey, two or three clients in 10 hold a formal plan and the rest hold a phone number. That phone number is the seam, and nobody has written down what happens on either end of it. In CrowdStrike’s survey, having a plan did not change the odds of a breach. For those clients the tabletop’s whiteboard becomes the first draft, and an incident response plan template gives it a structure to land in.

Service Provider Capacity in Cynomi’s State of the vCISO

The provider’s side of the handoff has limits of its own. Cynomi’s State of the vCISO research, a yearly survey of 200 senior MSP and MSSP leaders in North America run by the independent firm Global Surveyz, measures them.

  • Cybersecurity frameworks such as NIST or ISO overwhelm 93% of MSPs and MSSPs, by their own account (Cynomi, 2024).
  • Just 2% say they are not overwhelmed at all by regulatory compliance frameworks, and 74% feel overwhelmed by them; none said the same of cybersecurity frameworks (Cynomi, 2024).
  • Among providers not yet offering vCISO services, limited headcount stands in the way for 26% (Cynomi, 2025).
  • For 17%, the barrier is having no processes in place for the offering (Cynomi, 2025).
  • High initial investment was a barrier for 33% of those providers (Cynomi, 2025).
  • Larger providers are more likely to offer the service, with 80% of providers with 1,000 or more employees offering vCISO services, against 52% of providers with 51–199 employees (Cynomi, 2025).

Rev. 3 is one more NIST change for teams that already feel buried by frameworks, and the tabletop turns it into three questions a client can answer in one session. Headcount is the harder limit. A provider short on people cannot put a senior person on call for every client over every holiday. So get the authority questions for each client handoff answered in writing in November, when someone senior can still take the call.

Third-Party Breach Statistics and Incident Response Handoffs

The third parties NIST wants at the table are also involved in a large share of breaches. Verizon’s 2026 Data Breach Investigations Report (DBIR) breaks out the share of breaches with a third party involved, by segment:

SegmentBreaches with a third party involved (Verizon 2026 DBIR)
Retail68%
Manufacturing61%
Small and medium-sized businesses55%
Financial and insurance34%
Healthcare32%
  • Third-party involvement doubled to 30% of all breaches in the previous year’s report (Verizon, 2025).
  • Of 2024’s data breaches, 35.5% originated from third-party compromises, a share the researchers call a likely undercount (SecurityScorecard, 2025).
  • Supply chain breaches, where a compromised business partner became the attack vector, added $227,250 to the average breach (IBM, 2026).
  • In financial services, 49% of institutions had a vendor-related cyber incident in the past year, and 66% feel pressure to strengthen third-party risk management (Ncontracts, 2025).
  • Only 33% of organizations comprehensively map their supply chains (World Economic Forum, 2026).
  • The security maturity of suppliers is evaluated by 66% of organizations (World Economic Forum, 2026).
  • MSP customers should make sure their contracts specify the security measures their MSP implements, says a joint advisory from the Cybersecurity and Infrastructure Security Agency (CISA) and its Five Eyes partners (CISA, 2022).

When more than half of small-business breaches involve a third party, a tabletop that walks only the client’s own staff through a ransomware note never rehearses the call to the supplier. Put a supplier compromise in the scenario, and seat the vendor or the person at the client who owns that vendor relationship.

Holiday Ransomware and On-Call Response Capacity

Holiday risk comes down to who is available when an attack lands, and who is allowed to act without them.

  • A joint FBI and CISA advisory warned of an increase in ransomware attacks on holidays and weekends, citing a 2021 Fourth of July weekend attack through an RMM tool that hit multiple MSPs and their customers (FBI and CISA, 2021).
  • When “network defenders and IT support of victim organizations are at limited capacity for an extended time,” attackers gain a head start (FBI and CISA, 2021).
  • Staffing is the agencies’ fix: identify IT security employees “to be available and ‘on call'” during holidays and weekends (FBI and CISA, 2021).
  • Dual-extortion attacks made up 70% of ransomware claims (Coalition, 2026).
  • A record 86% of Coalition policyholders hit by ransomware in 2025 refused to pay the demand (Coalition, 2026).
  • Ransomware was present in 88% of SMB breaches, against 39% of breaches at large organizations (Verizon DBIR SMB snapshot, 2025).
  • An estimated 46% of SOC alerts are false positives, and 42% go uninvestigated (Microsoft and Omdia, 2026).
  • On staffing, 53% of security leaders cite a lack of qualified candidates, and 25% are relying more on external partners, including MSSPs (KPMG, 2025).

The analyst on call at 2 a.m. on Dec. 26 is working an alert queue where close to half the alerts are noise, for clients whose decision-makers are away. Each containment step that needs a phone call first leaves the attacker more time. The tabletop should settle which steps the analyst can take without calling anyone.

Incident Response Costs and Client Expectations

A slow handoff costs the client money, and the costs below show how much is at stake.

  • In IBM’s 2021 breach research, organizations with an incident response team and a tested plan averaged $3.25 million per breach, a 54.9% difference from the $5.71 million average for organizations with neither (IBM, 2021).
  • Surveyed organizations with fewer than 250 employees put their cyber incident costs at around $52,000 a year (Hiscox, 2026).
  • For its policyholders, Coalition recovered $21.8 million in stolen funds, an average of $202,000 per recovery (Coalition, 2026).
  • Cyber insurance is carried by 86% of US SMBs and 78% of Canadian SMBs (ESET North America, 2026).
  • According to 61% of MSPs, clients depend on them for cybersecurity advice (Kaseya, 2026).

Response stalls at the handoffs, waiting on a sign-off, a supplier, or an insurer’s go-ahead. A tabletop in the fall settles those decisions, so the December call is already made.

Run the Pre-Holiday Incident Response Tabletop This Quarter

Book a 90-minute tabletop this quarter with the decision-makers and other providers at each client where your team handles incident response, starting with the accounts where a holiday outage would hurt most. CISA publishes more than 100 Tabletop Exercise Packages you can adapt, so spend your preparation on the client’s contract and cyber insurance policy, where the seams are already written down or missing. Leave the room with two documents. The first is a one-page call tree that names a primary and a backup for every role, with the dates each person is away. The second is a signed list of the containment steps your analyst may take before anyone answers the phone. NIST’s own example, deactivating services to contain an incident, belongs on the first line of that list.

Those decisions have to end up in a written plan. With the IR Plan Builder in CISO Intelligence, part of Cynomi’s Security Growth Platform for service providers, your team can turn what the room agreed into a draft incident response plan the client reviews before the holidays. Your on-call analyst then starts the season knowing what they are allowed to do, and every seam has a name on both sides.