It's 2:30 a.m., and your security tool has flagged a suspicious admin account. Someone has been using it, and it wasn't the admin.
You've found the compromised identity. Now the harder questions start:
What did the attacker create, change, or delete with it?
Which permissions, roles, and group memberships did those changes touch?
Did they plant a backdoor that will let them back in next week?
If you roll things back, how do you avoid restoring the attacker's changes or breaking something the business depends on?
Most teams I talk to have a good answer to "Which identity is compromised?" and a much weaker answer to "What do we do about it?"
That's the gap we're closing.
Today, I'm excited to announce the general availability of Identity Behavioral Insights and Guided Recovery for Active Directory, Microsoft Entra ID, and Okta.
Why attackers go after identity
Identity has become the front door for attackers. When an adversary logs in with a compromised credential, they inherit its permissions and gain valid access to critical systems. From there, they can quietly escalate privileges, modify configurations, establish persistence, and move laterally. Each step widens the blast radius, and much of it goes unnoticed. When it's time to respond, and ultimately recover, businesses face an uphill battle:
1. Nobody can see the blast radius
Teams can't quickly tell what a compromised identity touched, or how those changes rippled across other identities, permissions, and resources. Investigators end up rebuilding the timeline by hand, and malicious changes slip through.
2. Investigation is slow, manual, and tedious
Activity data is fragmented and sometimes missing critical context, forcing analysts to correlate it across multiple records and systems. Every hour spent doing that is another hour the attacker keeps access or operations stay down, and an hour your SOC and IT teams aren't spending on response.
3. Response depends on who's on shift
Even after you've pieced together what happened, someone has to decide which objects to restore and which changes to reverse. Without a defined workflow, two analysts can handle the same incident in two entirely different ways. Steps get skipped, outcomes vary, and legitimate business operations can be disrupted.
4. Recovery remains a guessing game
Restoring an object doesn't make the environment clean, especially without precise evidence of what's risky and what's safe. The environment can only be trusted once malicious permissions, access paths, and persistence are removed. Fail to re-establish that trust, and reinfection follows.
Our answer to these challenges was to go a level deeper, applying insights and evidence to guide decision-making and re-establish trustworthy access faster.
How Druva helps
Druva Identity Resilience gives IT and SecOps teams an identity-aware view across Active Directory, Microsoft Entra ID, and Okta. It's powered by Dru MetaGraph, our AI-driven relationship graph, which continuously correlates identity metadata so teams can understand the full blast radius of a compromise in minutes instead of spending days digging through logs.
Behavioral Insights reveals impact, how far an attacker reached, and what they changed. Guided Recovery then turns that evidence into a pre-validated plan to contain the threat and restore identities to a known-good state.
Continue reading to learn more, and watch this demo to see it in action.