Product
Solutions
Resources
Customers
Company

Measure how fast your email defenses adapt

Mean time to coverage (MTTC) measures how quickly a missed attack becomes a new detection built for your organization.

Trusted by leading security teams
CompassSpotifyBentlerelasticSnowflakerampzscalerAnduril

What is mean time to coverage?

An email impersonating your helpdesk reaches finance, then sales, then your CFO. That’s a detection gap, and it stays exploitable until it’s closed. With adversaries using AI to run campaigns and shift tactics autonomously, open gaps compound fast.

Mean time to coverage (MTTC) measures how long you stay exposed: the average time from the first signal of a miss to a production-ready detection. Agent Hub tracks this for you, and Sublime customers see an MTTC of under 2 hours.

If something gets through, an autonomous loop closes the gap without waiting on a vendor update. ASA (Autonomous Security Analyst) investigates the miss. ADÉ (Autonomous Detection Engineer) writes detection logic tailored to your organization and backtests it against historical email. You decide what goes live.

When we find a new threat, we don't have to raise a ticket and wait for a black box vendor to make the change. With Sublime, a new detection can be deployed and tested in minutes.
Victor Sogaolu
Staff Security Engineer, Snyk

Why coverage gaps persist

Message cleanup handles one email

Remediating the message in front of you deals with that message alone. It does nothing for the next wave of the same attack.

One-off policies aren’t durable

A policy written for one attack may block that exact email again, but miss variations in the sender or content.

Hand-written detections compete for time

Writing detections yourself can work, but that takes time away from everything else your team works on.

Vendor updates follow the vendor’s schedule

Waiting on a vendor update leaves the timing of your protection, and the length of your exposure window, in someone else’s hands.

What mean time to coverage gives your team

Turn misses into stronger protection

Close coverage gaps without waiting on a vendor update. ASA investigates the suspicious message, and ADÉ generates and backtests a detection tailored to your organization.

Measure and improve your time to coverage

Use MTTC to see how quickly eligible misses become new detection coverage and where your workflow loses time.

Show progress without losing control

Give security leaders a clearer view of how fast the organization adapts, next to information about detection review and activation. Your team keeps control over how new protection is applied, and the logic behind every detection is open to inspect.

Detection efficacy and mean time to coverage

The two work together: efficacy shows how much gets caught up front, and MTTC shows how fast your defenses respond to what doesn’t.

Measure Detection efficacy Mean time to coverage
Question it answers

How well do your defenses catch attacks the first time?

How quickly do your defenses respond to a gap you’ve identified?

What it measures

Initial detection

How long an eligible miss takes to become a generated detection

What it doesn’t show

How fast protection follows a miss

Anything after generation, such as review and activation

Find out how fast your defenses adapt

See mean time to coverage in Agent Hub, and walk through how a missed attack becomes a new detection in an environment like yours.

Frequently asked questions

What is mean time to coverage?

Mean time to coverage (MTTC) is the average elapsed time from the earliest signal that a malicious message got through, such as a user report or an analyst classification, to the completion of the ADÉ job that generates a detection for it. It shows how quickly that part of your response runs.

Which misses count toward MTTC?

MTTC counts malicious messages that got through and have a successfully completed ADÉ job. Messages ASA classifies as spam or graymail aren’t counted, and neither are ADÉ jobs that are still running, failed, or canceled. Once a resubmitted job succeeds, it’s included.

Does MTTC tell me when a detection was deployed?

No. For the initial metric, the clock stops when the ADÉ job completes, and the calculation doesn’t require the generated detection to be accepted. Read MTTC as the time to generate coverage.

Why does this matter if we already measure detection efficacy?

Initial detection efficacy tells you how well your defenses catch attacks up front. MTTC adds a different view: how quickly they respond to a gap you’ve identified. The two measures complement each other.

What role do ASA and ADÉ play?

ASA investigates suspicious email. ADÉ generates and backtests detections tailored to your organization to address the gaps. The broader loop connects investigation to detection engineering, and the initial MTTC calculation measures eligible ADÉ jobs.

Is the whole process autonomous?

Sublime supports an autonomous defense loop, and the path and level of human involvement depend on your configuration. Not every customer has every automation turned on, and you choose which ones to enable.

Why does a lower MTTC matter?

A lower MTTC means your team generates detections faster after eligible misses. That closes coverage gaps sooner. The sooner new protection is generated and put into action, the sooner it helps stop follow-on attacks before they reach more employees.

How do we use MTTC to improve?

Start by mapping where the time goes, from the first signal to the ADÉ job. Manual steps, such as sending a message to ADÉ by hand or not running ASA on user reports, tend to raise MTTC, so your automation settings are the first place to look. Check with your Sublime team before you change settings, and look at review and detection quality alongside the number.

How should I report MTTC to my CISO?

Give the number with its measurement period and context, and explain that it measures time to detection generation and says nothing yet about whether a detection is active. Where available, add the number of eligible jobs, review and activation status, detection quality, and the steps your team is taking to improve the workflow. MTTC is one indicator of how fast you adapt, next to efficacy and detection quality.

Where do I see MTTC?

MTTC appears in the revamped Agent Hub, alongside information about agent activity and impact. It requires ASA and ADÉ to be enabled and running.

Now is the time

See how Sublime delivers autonomous protection by default, with control on demand.