Skip to content
Menu

Mean Time to Identify and Contain a Breach

The average days from the start of a confirmed security breach to its identification, plus the days from identification to containment.

Security Operations

Formula

Mean of (identified date − start date) + Mean of (contained date − identified date)

Why Track It

Every day an attacker sits undetected raises the cost and the chance of losing the client. The trend shows whether detection tooling and monitoring are catching intrusions early.

How It Is Measured

For each confirmed security incident at a client or at the MSP, record when the compromise began (from forensic evidence), when it was identified and when it was contained. Report the two intervals separately and combined. Source: the incident response record or security tickets in the PSA, with dates confirmed by the investigation.

Constraints

Most small MSPs see few confirmed breaches, so the mean rests on a handful of events. The start date depends on forensic work that is often incomplete.

Measurement Note

IBM's 2025 Cost of a Data Breach Report found a mean of 241 days to identify and contain a breach, the lowest in nine years. That is a cross-industry mean, not an MSP benchmark, so an MSP running managed detection should sit well below it and track its own trend.

Referenced In

Glossary and Answers

More in Security Operations

Whether the basic controls an MSP runs for clients are actually in place and working. These numbers show how exposed the client base is to the breach that ends a client relationship.

All KPIs
Sources1
  1. IBM: 2025 Cost of a Data Breach Reportibm.com

Welcome Back

Sign in to your MSP Outpost account.