Huntress Extends SOC Response to Microsoft Defender
The 24/7 security operations center now investigates and responds to incidents raised across the wider Microsoft Defender suite.
Updated on Nov. 18, 2026 in Cybersecurity

Huntress expanded its Agentic Security Platform SOC to cover incidents raised across the Microsoft Defender suite. The move follows a token-replay campaign that compromised 97 Microsoft 365 accounts across 79 organisations between 14 July and 22 September 2026.
Why it matters
Attackers who capture session tokens after victims complete multi-factor authentication can access accounts without a password or further prompt, making identity signals harder to act on. Huntress's expansion targets that gap by correlating alerts across Defender, Entra ID Protection and related tools before customers receive a report.
Huntress now ingests incident data from Microsoft Defender for Identity, Defender for Office 365, Defender for Cloud Apps and Entra ID Protection, with analysts correlating these signals to prioritise the queue. Detection logic was rebuilt so a single incident naming several accounts attaches to each affected identity, though the source does not give latency or false-positive rates.
The players
Huntress
Huntress is a managed security company that provides 24/7 security operations and threat detection services to small and mid-sized businesses.
Microsoft Entra ID Protection
Microsoft Entra ID Protection is Microsoft's identity-risk detection service within its Entra cloud identity platform, which flags suspicious sign-ins and compromised accounts.
The details
Huntress analysts correlate signals across the Defender suite, confirm whether a threat is active and respond before sending customers a report. The token-replay campaign used adversary-in-the-middle phishing to capture session tokens, then registered rogue devices and authenticator apps and set inbox rules to hide activity; in one case a hijacked mailbox sent a payroll-related email to an external accountant. Huntress Managed ITDR detected the activity first, and Microsoft Entra ID Protection flagged the same attacker infrastructure.
Timeline
14 July 2026: Token-replay campaign tracking begins.
22 September 2026: Token-replay campaign tracking ends.
18 November 2026: Huntress announces the expanded Defender SOC response.
The Tech Race
Microsoft's Defender and Entra ID Protection products are now a central layer of enterprise identity security, and third-party managed providers like Huntress are competing to sit on top of them. The move reflects a shift from device-centric monitoring toward identity-centric detection as session-token theft replaces password attacks.
Organisations running Microsoft 365 should review whether session-token replay and rogue authenticator registration are covered by their current monitoring. Administrators can check for unfamiliar devices, authenticator apps and inbox forwarding rules on user accounts.
The takeaway
Session-token theft can bypass multi-factor authentication, so monitoring should look for new devices, authenticator registrations and hidden inbox rules rather than relying on login prompts alone. Correlating alerts across identity and email tools helps reveal campaigns that single-product alerts miss.
Further reading
For more on how attackers exploit identity systems, see our Cybersecurity coverage.
Source note: This article includes information reported by IT Security Guru.



