Aperçu de la situation

  • Identity is now the dominant attack vector. Ninety percent of incident response engagements in 2025 involved identity weaknesses, making ITDR essential for any modern security program.
  • ITDR complements — but does not replace — IAM, PAM, EDR, and XDR. It adds identity-specific behavioral detection that other tools lack.
  • Non-human identities are an emerging blind spot. With 18.1 million exposed API keys and 6.2 million AI tool credentials recaptured in 2025, machine identity threats demand the same scrutiny as human ones.
  • Effective ITDR requires phased implementation and measurable KPIs — including mean time to identify, false positive rate, and identity attack surface coverage.
  • Real-world breaches prove the case. The Snowflake, Midnight Blizzard, and FICOBA incidents each demonstrate how identity-based attacks succeed where traditional controls fail.

Identity has become the primary attack surface. In 2025, 90% of incident response investigations involved identity weaknesses, and 65% of initial access was identity-driven — through phishing, stolen credentials, or brute force — according to Unit 42's Global Incident Response Report 2026. Meanwhile, nearly two billion credentials were indexed from malware combo lists in that same year. Traditional perimeter and endpoint controls were never designed to catch attackers who walk through the front door with valid credentials. Identity threat detection and response (ITDR) exists to close that gap.

This guide explains what ITDR is, how it works, the attacks it detects, how it compares to other security tools, and how to implement it effectively — with real-world breach case studies and compliance mapping to back every claim.

What is identity threat detection and response (ITDR)?

Identity threat detection and response (ITDR) is a security discipline that detects, analyzes, and responds to threats targeting user and machine identities across on-premises and cloud environments, using behavioral analytics and AI to identify credential misuse, privilege escalation, and identity-based lateral movement that bypass traditional perimeter defenses.

Gartner first recognized ITDR as a top security and risk management trend in 2022, calling it out as a distinct category separate from identity and access management (IAM). The distinction matters. IAM manages who gets access. ITDR detects when that access is subverted, abused, or stolen.

The market has responded. The ITDR market is growing at approximately 22.6–22.9% CAGR, according to both Fortune Business Insights and MarketsandMarkets. That growth reflects a reality defenders already know — attackers have shifted from exploiting infrastructure to exploiting identities.

ITDR works alongside identity security posture management (ISPM), its preventive counterpart. Where ISPM focuses on hardening identity configurations, right-sizing permissions, and removing dormant accounts before attackers exploit them, ITDR monitors for active threats in real time. Together, they form a comprehensive identity security strategy built on both prevention and detection. Identity analytics provides the behavioral intelligence that powers both disciplines.

Why identity is the new perimeter

The scale of identity exposure is staggering. According to the IDS Alliance's 2024 Trends in Securing Digital Identities study, 90% of organizations experienced an identity breach in the past year. The SpyCloud 2026 Identity Exposure Report found that 65.7 billion identity records were recaptured in 2025 — a 23% year-over-year increase.

These numbers explain why identity-based attacks now dominate incident response engagements. Attackers do not need to exploit a vulnerability when they can log in with valid credentials. Every cloud application, SaaS platform, and federated identity provider expands the identity attack surface. And traditional security tools — firewalls, endpoint agents, network monitoring — were not built to detect an attacker who looks like a legitimate user.

How ITDR works

ITDR operates through a continuous cycle of data collection, behavioral analysis, threat detection, and automated response. Here is how the operational model breaks down.

ITDR Operational Model

The four-phase ITDR operational model

  1. Collect identity signals. Ingest authentication logs and identity telemetry from Active Directory, cloud identity providers (such as Entra ID), SaaS applications, PAM tools, and federation services.
  2. Establish behavioral baselines. Map normal identity behavior patterns — login times, geographic locations, privilege usage, authentication methods, and access frequency — for each user and machine identity.
  3. Detect anomalies and threats. Apply behavioral threat detection to identify deviations such as impossible travel, unusual privilege escalation, abnormal OAuth consent grants, and password spraying patterns.
  4. Automate containment and response. Execute automated responses including step-up MFA challenges, account disablement, credential rotation, and session isolation based on threat severity.
  5. Correlate across identity sources. Stitch identity signals from on-premises and cloud environments to build unified threat detection context.
  6. Tune and optimize. Continuously refine detection thresholds, reduce false positives, and expand coverage as the identity attack surface evolves.

This cycle runs continuously. Unlike point-in-time audits, ITDR provides persistent monitoring that adapts as user behavior changes — new roles, new applications, new locations all trigger baseline recalibration.

Identity security posture management (ISPM)

ISPM is the preventive counterpart to ITDR's detective and responsive role. Where ITDR asks "is this identity behaving maliciously right now?", ISPM asks "are our identity configurations creating unnecessary risk?"

Key ISPM functions include identity inventory, permission right-sizing, misconfiguration detection, and dormant account identification. The need is acute. According to Unit 42's 2026 research, 99% of analyzed cloud identities had excessive permissions — a massive, exploitable attack surface that ISPM is designed to shrink before ITDR ever needs to detect an attacker leveraging those permissions.

Organizations that deploy both ITDR and ISPM together create a defense-in-depth model for identity. ISPM reduces the blast radius by eliminating unnecessary access. ITDR catches the threats that make it past preventive controls.

Types of identity-based attacks ITDR detects

Identity-based attacks span a wide range of techniques targeting both human and machine identities. ITDR is designed to detect these attacks through behavioral analytics rather than static rules.

Table: Identity-based attacks and ITDR detection methods

Type d'attaque How ITDR detects Real-world example
Credential-based attacks (password spraying, credential stuffing, brute force) Detects abnormal authentication failure rates, velocity anomalies, and distributed login attempts across accounts Midnight Blizzard used password spraying against a legacy non-MFA test account
Privilege escalation (anomalous role assignments, shadow admin creation) Flags unexpected role changes, new admin account creation, and permission modifications outside normal change windows Attackers create shadow admin accounts to maintain persistence after initial compromise
Lateral movement (pass-the-hash, pass-the-ticket, token replay) Identifies unusual authentication patterns between systems, abnormal service ticket requests, and Kerberos anomalies Pass-the-ticket attacks enabling movement across domain-joined systems
Account takeover (session hijacking, MFA bypass, SIM swapping) Detects concurrent sessions from disparate locations, session cookie reuse, and MFA method changes Tycoon 2FA platform enabled adversary-in-the-middle session hijacking at scale
OAuth and token abuse (malicious consent grants, token theft) Monitors for unusual OAuth application registrations, excessive permission grants, and token usage anomalies Midnight Blizzard leveraged legacy OAuth apps with elevated Exchange Online permissions
Non-human identity threats (API key compromise, service account abuse) Baselines machine identity behavior and flags deviations in API call patterns, service account usage, and credential access times Infostealer malware harvesting API keys and session tokens from developer workstations

For deeper exploration of specific attack types, see the dedicated guides on credential theft, privilege escalation, lateral movement, account takeover, and Kerberoasting.

Non-human identity (NHI) threats

Non-human identities — API keys, service accounts, OAuth tokens, and AI agent credentials — now outnumber human identities by more than 10-to-1 in most enterprises. They represent a rapidly expanding blind spot.

The SpyCloud 2026 Identity Exposure Report revealed that 18.1 million exposed API keys and tokens were recaptured in 2025, alongside 6.2 million AI tool credentials exposed via infostealer malware. These machine credentials often have broad permissions, long or nonexistent expiration periods, and limited monitoring — making them high-value targets.

Key NHI attack vectors include OAuth token abuse, service account compromise, API key theft, and session cookie replay. ITDR solutions address NHI threats by baselining machine identity behavior and flagging deviations — an API key suddenly used from an unfamiliar IP range, a service account accessing resources outside its normal scope, or an AI agent credential being used at unusual hours.

ITDR vs. other security tools

Security teams already operate IAM, PAM, EDR, XDR, and SIEM platforms. ITDR does not replace any of them. It fills a specific gap — identity-specific behavioral detection — that none of these tools was designed to address.

Table: How ITDR relates to existing security tools

Outil Fonction principale Identity coverage Relationship to ITDR
IAM Manages access policies, authentication, and authorization Defines who gets access ITDR detects when IAM policies are subverted or abused
PAM Controls and monitors privileged access Governs privileged accounts ITDR detects anomalous behavior within privileged sessions. Gartner and KuppingerCole recommend PAM + ITDR convergence
EDR Monitors endpoints for malicious processes and behaviors Limited to endpoint-level user context ITDR monitors identity signals that EDR cannot see (OAuth grants, federated auth, cloud IdP activity)
XDR Correlates telemetry across endpoints, network, and cloud Broad but shallow on identity ITDR provides specialized identity signal depth that enriches XDR platforms
SIEM Aggregates logs for correlation, alerting, and compliance Log-based identity visibility ITDR provides identity-specific behavioral analytics that reduce alert noise vs. raw log correlation

The key distinction is behavioral depth. IAM and PAM enforce policies. EDR watches endpoints. SIEM correlates logs. None of them apply continuous behavioral analytics specifically to identity signals across the full identity attack surface — on-premises Active Directory, cloud identity providers, SaaS applications, and federation services simultaneously.

Identity attacks in practice

Real-world breaches demonstrate why ITDR matters more effectively than any theoretical discussion. Each of the following cases involved identity-based attacks that bypassed traditional controls — and each reveals specific points where ITDR would have detected the threat.

Snowflake customer breaches (2024)

Threat actor UNC5537 used infostealer-harvested credentials — some dating back to 2020 — to access approximately 165 customer instances on the cloud data platform. Affected organizations included major telecommunications, entertainment, and financial services companies.

Three factors enabled the breach. Customer accounts lacked MFA. Valid credentials from years-old infostealers still worked. No network access policies restricted login sources.

ITDR lesson. Behavioral analytics would have detected anomalous login patterns — new geolocations, unfamiliar devices, and known-compromised credentials — flagging the access attempts before data breach exfiltration began. Source: Cloud Security Alliance.

Midnight Blizzard (2024)

APT29 used password spraying to compromise a legacy test account that lacked MFA. From there, the threat actor leveraged legacy OAuth applications with elevated permissions to create malicious OAuth apps and grant them Exchange Online full access — ultimately reading senior leadership email.

ITDR lesson. ITDR would have detected the password spraying pattern, flagged the OAuth application creation from an unusual source, and alerted on the abnormal role assignment granting Exchange Online access. Multiple detection opportunities existed across the kill chain. Source: MSTIC incident guidance.

French FICOBA registry breach (2026)

An attacker used stolen civil servant credentials to access the national bank account registry (FICOBA), exposing financial data for approximately 1.2 million individuals. PAM alone could not detect the abuse because the attacker used valid credentials with authorized access levels.

ITDR lesson. Behavioral analytics would have flagged anomalous access patterns — unusual data volume, atypical query timing, and access frequency far exceeding the user's historical baseline. Source: The Hacker News.

Identity-Based Breaches and ITDR Detection

Detecting and preventing identity threats

Effective identity threat detection requires phased implementation, measurable KPIs, and a deliberate choice between self-managed and managed approaches. Here are the best practices and a practical roadmap.

ITDR best practices:

  • Continuously monitor all identity sources (Active Directory, cloud IdPs, SaaS, PAM)
  • Integrate ITDR with existing SIEM and XDR platforms for correlated context
  • Implement least privilege and enforce just-in-time access
  • Deploy deception-based detection using honeypot accounts and honeytokens
  • Develop identity-specific incident response playbooks
  • Enable proactive threat hunting focused on identity signals

ITDR implementation roadmap

Table: Phased ITDR implementation roadmap

Phase Actions Critères de réussite Chronologie
1. Assess Identity source inventory, gap analysis, prerequisite readiness check Complete inventory of all identity sources (AD, cloud IdPs, SaaS, PAM) Weeks 1–4
2. Baseline Establish behavioral baselines for all monitored identities Stable baselines with documented learning period expectations Weeks 5–10
3. Integrate Connect to IAM, PAM, SIEM, and identity provider sources Bi-directional data flow confirmed across all sources Weeks 8–14
4. Detect Enable identity-specific detection rules and behavioral analytics Detection rules active with initial alert triage workflow Weeks 12–18
5. Respond Configure automated response playbooks (step-up MFA, account lockout, credential rotation) Automated containment for critical identity alerts <1 hour Weeks 16–22
6. Optimize Tune detection thresholds, reduce false positives, expand coverage False positive rate <10%, identity attack surface coverage >95% En cours

ITDR metrics and KPIs to track throughout implementation:

  • MTTI (mean time to identify identity incidents): Target <1 hour for critical identity alerts
  • MTTC (mean time to contain identity-based intrusions): Target <4 hours
  • Identity attack surface coverage: Target >95% of identity sources monitored
  • False positive rate: Target <10% of total identity alerts
  • Detection-to-containment gap: An industry annual threat report found that 68% of organizations detect identity threats within 24 hours, but only 55% contain them effectively — a 13-point gap that ITDR automation is designed to close.

Managed ITDR for resource-constrained teams

Not every organization has the staffing to build and operate ITDR in-house. Managed detection and response services provide outsourced identity threat detection and response for teams that need 24/7 coverage without expanding headcount.

When to consider managed ITDR:

  • Security teams with fewer than five FTEs
  • Limited 24/7 monitoring coverage
  • Insufficient identity security expertise in-house

What to evaluate: Coverage breadth (AD + cloud + SaaS), response SLAs, integration with the existing stack, and transparent reporting. The market for managed ITDR is growing rapidly, with multiple vendors expanding their managed ITDR capabilities to meet demand from MSPs and MSSPs.

ITDR and compliance

ITDR capabilities map directly to identity-related controls across major regulatory compliance frameworks. Aligning ITDR to these frameworks simplifies audit evidence collection and demonstrates proactive identity security governance.

MITRE ATT&CK identity technique mapping

Table: MITRE ATT&CK techniques covered by ITDR

Tactique ID de la technique Nom de la technique ITDR detection
Accès Initial T1078 Comptes valides Detects anomalous logon patterns, impossible travel, and credential reuse from known-compromised sources
Accès aux identifiants T1110 Force brute Identifies abnormal authentication failure rates and distributed password spraying
Accès aux identifiants T1558 Steal or Forge Kerberos Tickets Flags anomalous Kerberos ticket requests and golden/silver ticket usage patterns
Mouvement latéral T1550 Use Alternate Authentication Material Detects pass-the-hash, pass-the-ticket, and token replay across domain boundaries
Persistance T1098 Manipulation de compte Monitors for unauthorized role changes, new admin account creation, and permission modifications

For a broader overview of the framework, see the MITRE ATT&CK topic page.

Compliance framework crosswalk

Table: How ITDR maps to compliance frameworks

Le cadre ID de contrôle ITDR mapping
NIST CSF 2.0 ID.AM, PR.AA, DE.CM, DE.AE, RS.AN, RS.MI Identity inventory, access monitoring, anomaly detection, investigation, mitigation
ISO 27001 A.9, A.12.4, A.16 Access control monitoring, security event logging, incident management
CIS Controls v8 5, 6, 8 Account management, access control management, audit log management
PCI DSS 4.0 Req 7, 8, 10 Restrict access, identify and authenticate, log and monitor
HIPAA 45 CFR 164.312 Access controls, audit controls, integrity controls, transmission security
NIS2 Article 21 Risk management measures including identity and access management
DORA Ch. II, Art. 5–15 ICT risk management framework including identity security

Tendances futures et considérations émergentes

The identity threat landscape is evolving faster than most security programs can adapt. Over the next 12–24 months, several developments will reshape how organizations approach ITDR.

AI-accelerated attacks are compressing response windows. Unit 42's 2026 research found that AI-assisted attack simulations achieved full exfiltration in just 25 minutes, with the fastest observed real-world exfiltration at 72 minutes. These timelines leave no room for manual investigation. ITDR solutions that automate detection and response will become table stakes, not differentiators.

PAM and ITDR convergence is accelerating. Both Gartner and KuppingerCole now recommend unified identity defense layers that merge privileged access controls with identity threat detection. Organizations that keep these capabilities siloed will face gaps that attackers already know how to exploit.

Session-based attacks are scaling through phishing-as-a-service. The Tycoon 2FA platform — which Europol disrupted in a coordinated takedown — enabled adversary-in-the-middle attacks that bypassed MFA at scale. Despite the disruption, the platform returned within weeks, demonstrating the resilience of the phishing-as-a-service economy. ITDR must detect session hijacking and token replay regardless of how the initial credential was compromised.

Non-human identity protection will become a regulatory requirement. As API keys, service accounts, and AI agent credentials proliferate, expect compliance frameworks to mandate monitoring and lifecycle management for machine identities. Organizations should begin inventorying their NHI attack surface now.

Modern approaches to identity threat detection

The most effective ITDR programs today go beyond standalone identity monitoring. They integrate identity signals with network detection and response, cloud telemetry, and endpoint context to build a unified view of attacker behavior across the entire attack surface.

Cloud-native ITDR extends detection to cloud identity providers, SaaS platforms, and multi-cloud environments where traditional on-premises tools have no visibility. AI security capabilities — including AI-driven threat intelligence and behavioral modeling — enable ITDR solutions to keep pace with adversaries who are themselves using AI to accelerate attacks.

The integration of ITDR with zero trust architectures represents a natural evolution. Zero trust mandates continuous verification. ITDR provides the identity behavioral intelligence that makes continuous verification meaningful rather than performative.

How Vectra AI approaches identity threat detection

Vectra AI's approach to identity threat detection centers on Attack Signal Intelligence, which applies behavioral analytics to identity signals across on-premises Active Directory, cloud identity providers, and SaaS applications. By correlating identity behaviors with network telemetry, the methodology identifies real attacks hiding in normal-looking identity activity rather than generating more alerts for analysts to triage. The goal is signal over noise — giving security teams the clarity to act on what matters and the confidence to ignore what does not.

Conclusion

Identity-based attacks are not a trend. They are the dominant attack vector — responsible for the majority of initial access in confirmed incidents and the root cause of high-profile breaches at organizations of every size and industry. The Snowflake, Midnight Blizzard, and FICOBA cases each tell the same story — valid credentials, insufficient monitoring, and preventive controls that were never designed to catch an attacker who looks like a legitimate user.

ITDR closes that gap. It brings continuous behavioral detection to the identity attack surface, catches threats that IAM, PAM, and EDR cannot see, and automates containment before attackers achieve their objectives. Combined with ISPM for preventive posture management and aligned to frameworks like MITRE ATT&CK and NIST CSF, ITDR gives security teams the visibility and speed they need to defend the most targeted surface in modern enterprises.

For organizations ready to evaluate their identity threat detection capabilities, explore how Vectra AI approaches ITDR through Attack Signal Intelligence.

Foire aux questions

What is identity threat detection and response (ITDR)?

How does ITDR differ from EDR?

Why is ITDR important?

What is identity security posture management (ISPM)?

What is managed ITDR?

What are the key ITDR metrics?

How does ITDR map to MITRE ATT&CK?