WatchGuard Blog

Stopping an Intrusion Doesn't Mean the Incident Is Over

See how MDR helps MSPs contain threats and investigate their true scope.

When unauthorized access is detected and blocked, the threat might seem contained. But locking the attacker out doesn't answer the most critical questions: What did they do before they were discovered? What did they access? Were they able to exfiltrate data? 

This is what happened in the recent cyberattack on France's General Directorate of Public Finances. In late June, the agency detected multiple instances of unauthorized access during a routine check and immediately shut them down. Initial investigations found no evidence that any information had been exfiltrated, suggesting the incident was under control.

The situation changed on August 12, when a threat actor claimed on a cybercrime forum to have compromised the tax administration and put an alleged database up for sale. The follow-up investigation confirmed that the access points that had been blocked weeks earlier had, in fact, allowed the intruder to view and exfiltrate data belonging to 678,000 individuals and businesses. 

The affected information included reference tax income, family status ratios, and withholding tax rates, as well as company names and SIREN business registration numbers. Reaching this conclusion required more than just detecting and blocking malicious activity. It took a full reconstruction of the intrusion to determine what actually happened. 

For MSPs and anyone in cybersecurity, the lesson is clear: containing an intrusion is only part of the response. The critical work continues as you determine how far the attacker progressed, which systems they reached, and whether the threat still remains. And when a client asks what happened, MSPs need more than a ticket closure. They need a way to show the full picture.

The Four Challenges That Make It Harder to Determine the Scope of an Intrusion

For MSPs, the work doesn't stop once an alert is resolved.  Monitoring multiple client environments simultaneously means analyzing signals, correlating events, and retaining enough context to understand what is happening before, during, and after an intrusion. 

  1. Understanding What's Behind an Alert: A detection flags that something needs attention, but on its own, it can't tell you if an intrusion is underway or how far it has reached. That's why MSPs must validate an alert, correlate it with other events, and evaluate it within the context of the affected asset before deciding how to respond.
  2. Investigating Across Diverse Environments: Every endpoint, identity, SaaS app, and cloud workload generates activity that needs monitoring. When managing multiple clients, reconstructing an attack sequence requires gathering evidence from different sources without losing the context of each individual environment. As the number of clients grows, so does the effort required to collect evidence, correlate events, and determine which systems might be tied to the incident. 
  3. Recognizing Seemingly Legitimate Activity: A login, an authorized tool, or an outbound connection might appear to be normal client activity. However, when several of these actions occur in sequence, they can reveal an attacker making progress across the environment.
  4. Maintaining 24/7 Coverage: Malicious activity can surface at any time. An alert that comes in overnight or during the weekend gives a threat actor hours to escalate privileges, move laterally across systems, or hunt for sensitive data if no one is analyzing it in real time. This is where having analysts available around the clock, not just tools, changes the outcome.

How MDR Helps Turn Alerts into Investigations

For an MSP, having a Managed Detection and Response (MDR) service in place should mean more than receiving alerts. The real value is in the expertise and context needed to uncover what's happening, act on threats, and reconstruct incidents when necessary. And demonstrating that value to clients is just as important as delivering it. 

Comprehensive, real-time dashboards and structured reporting give partners a visual way to bring endpoint, network, identity, cloud, and vulnerability data together in one place. That kind of visibility gives MSPs a concrete answer when a client asks: 'What have you actually been doing for us?'

A strong MDR provider combines advanced detection technology with expert analysts to deliver that context and relieve the burden on MSP teams. In practice, this enables MSPs to:

  • Gain context for prioritization: By correlating incoming telemetry with other events and asset context, you can distinguish an isolated alert from an attack sequence. It also allows you to determine whether that activity extends to a client's other assets, identifying if the compromise is isolated to a single system or more widespread.
  • Deliver specialized analysis: Analysts review detections, filter out false positives, and evaluate the risk of each case. Their intervention is especially valuable when an attacker uses legitimate tools or operates in ways that don't match known threat patterns.
  • Understand the entry point: A critical part of reconstructing an intrusion is identifying how the attacker got in. Identifying current gaps and vulnerabilities connects what was detected to what was left exposed and flags whether similar vulnerabilities exist elsewhere in the client environment.
  • Determine what happened after containing the threat: This is where the investigation becomes especially crucial. Once the malicious activity is contained, MDR helps reconstruct how the intrusion began, what actions the threat actor took, and which assets they managed to reach. The goal isn't just to stop what's happening in the moment, but to gain a clear enough picture of the incident to know whether the threat has been eliminated and what impact it left behind.

For MSPs, that distinction is fundamental. A closed alert doesn't necessarily mean a closed incident. Containment mitigates the immediate risk; investigation reveals the risk that has already materialized. In an incident like the one at the French tax authority, that distinction can mean the difference between assuming an intrusion is over and knowing exactly how far it went.

That's why WatchGuard MDR is built around the principle that the work doesn't stop when an alert is closed. Around-the-clock analyst expertise, cross-source visibility, and client-facing reporting are there to back that up in practice, and to give MSPs something concrete to show clients when it matters most.

Want to dive deeper into how an MDR service can strengthen your clients' security? Explore these related articles on our blog: