Newtec Services · Threat Detection and Response 101
The average breach isn’t caught the day it happens. It’s caught 241 days later, usually by someone outside the business.
That’s not a worst-case estimate. It’s the global average for 2025: 181 days for an organisation to even realise something is wrong, and a further 60 days to bring it under control. That is the fastest this figure has been in nine years, and still the better part of eight months an attacker can operate inside a business undetected.
What Is Threat Detection & Response, Really?
It’s the discipline of actively watching your environment for signs of compromise: not waiting for antivirus to flag a known file, but catching the quieter signals (a login from an unexpected location, an account suddenly accessing data it never touches) and acting on them immediately, not whenever someone happens to notice.
Why This Should Matter at Leadership Level
A general IT team noticing something unusual on top of their regular workload isn’t the same as dedicated, round-the-clock monitoring, and the gap between the two is where most dwell time happens. The regulatory clock makes it worse: under GDPR, a breach involving personal data must be reported to the Data Protection Commission within 72 hours of becoming aware of it. Under NIS2, in-scope organisations face an even tighter sequence: a 24-hour early warning, full notification within 72 hours, and a final report within a month. Neither clock can be met if detection doesn’t already exist before the incident starts.
What Active Detection & Response Does
- Monitors around the clock: your environment (network, endpoints, cloud, and email) is watched continuously, not just during business hours.
- Correlates signals across systems: security event data from across your systems is collected and correlated, surfacing patterns a single alert would never reveal alone.
- Catches what signature-based tools miss: detection goes beyond known malware signatures to flag unusual behaviour, the patterns that mark an intrusion already underway.
- Responds and documents in real time: confirmed threats are isolated and contained immediately, with documentation produced as the response happens, not reconstructed afterward under deadline pressure.
What a Gap Usually Looks Like
The businesses hit hardest are rarely the ones with no security tools at all. They’re the ones where monitoring covers business hours but not the other sixteen, where alerts get generated but nobody has the capacity to review them, or where detection is tuned for known malware and misses the quieter behavioural signs of an intrusion already underway. The gap doesn’t need to be large to be costly: it just needs to be the one an attacker happens to use.
What “Good” Looks Like
Anomalies get investigated as they happen, not discovered months later during an unrelated audit. When something is confirmed, response is already underway, not improvised while a regulatory deadline is already running. And when a regulator, client, or your own board asks how quickly your organisation would notice a threat, you have a specific, demonstrable answer instead of an estimate.
Quick Answers (Threat Detection FAQ)
Q: We have antivirus and a firewall. Isn’t that detection?
Those tools catch known threats based on signatures. They’re not built to notice behavioural anomalies, such as a legitimate-looking login from the wrong place or an account suddenly reaching for data it’s never touched, which is exactly how most active intrusions are actually found.
Q: Can a small IT team handle this instead of a dedicated service?
Technically, yes. But 24/7 coverage on top of a team’s regular workload is rarely sustainable, and dwell time tends to reflect exactly that gap: detection that exists in theory but isn’t being watched when it matters.
Book a cyber security consultation with Newtec and request a threat detection readiness review.
Further Reading (Primary Sources)
- IBM Cost of a Data Breach Report 2025. The source of the 241-day average breach lifecycle figure referenced above.
- NIS2 Directive (EU) 2022/2555. Article 23 sets the 24-hour/72-hour/one-month incident reporting sequence referenced above.
- GDPR (EU) 2016/679. Article 33 sets the 72-hour breach notification duty referenced above.
- NCSC Ireland: NIS2 Quick Reference Guide. Ireland’s official summary of NIS2 risk-management and reporting obligations.


