Skip to main content
Live webinar · Nov 3Register free →
Skip to main content

Guides/Identity recovery

After an attack, recovery starts with identity.

Almost everything else depends on it. Until Active Directory and Entra ID are trustworthy again, people can't sign in, and restored applications and data can't be used safely. This guide covers what to protect, the two kinds of identity recovery, and the order a forest rebuild follows.

A straight-on view of an office building facade after sunset, a grid of dark windows with a single lit office in the center

Why it matters

Identity is where attacks go first.

9 in 10
cyberattacks involve Active Directory
50–100+
tasks in a manual AD forest recovery
Days–weeks
typical manual AD recovery time
Source: Source: Commvault Active Directory protection, citing a Dark Reading 2021 estimate for attacks involving AD.

What to protect

The directory, and everything that hangs off it.

Active Directory

Users, groups, group policy objects and the relationships between them, recoverable down to a single object or attribute.

Entra ID

Users, groups, roles, conditional access policies and app registrations, so deleted or modified objects can be restored and access comes back.

Two kinds of recovery

One bad change, or the whole forest.

Object restore

Rolls back the individual users, groups, policies or attributes that were deleted or changed, so only what broke is touched.

Forest recovery

Rebuilds Active Directory itself, domain controller by domain controller, when the whole directory is compromised.

Runbook outline

A forest recovery, in order.

An outline to build your own runbook from. Done by hand, these steps run to dozens of tasks; automated, runbook-driven recovery handles most of them and shows progress as it goes.
  1. 01

    Declare and contain

    Stop the spread: isolate affected systems and agree who leads the recovery and how the team communicates.

  2. 02

    Find a known-clean point

    Compare the directory between two points in time to see exactly what changed, and choose the last backup taken before the attack.

  3. 03

    Pick the restore order

    Use the topology to decide which domain controllers come back first, usually one per domain.

  4. 04

    Restore the first domain controllers

    Bring the first DC in each domain back from the clean backup, isolated from the compromised network.

  5. 05

    Run the consistency tasks

    Seize FSMO roles and adjust the RID pool, as Microsoft's forest recovery guidance describes.

  6. 06

    Rebuild the rest

    Restore or promote the remaining domain controllers to rebuild the pre-incident infrastructure.

  7. 07

    Reset privileged credentials

    Reset administrator and service account passwords, and the KRBTGT account, before anyone signs in again.

  8. 08

    Restore Entra ID and validate

    Restore deleted or changed Entra ID users, groups, roles and conditional access policies, then confirm people can sign in before applications come back.

Test it first

Prove it before an attacker forces you to.

Run forest recovery in a non-production lab, so the process is proven before you need it. KELYN plans and runs those tests with you.
  1. 01

    Do you back up Active Directory and Entra ID frequently, including roles, policies and relationships?

  2. 02

    Could you restore a single deleted user, group or attribute without a full rollback?

  3. 03

    Is there a written, tested forest recovery runbook, and who owns it?

  4. 04

    Have you run forest recovery in a non-production lab in the last year?

Commvault protects the directory. KELYN runs the recovery.

From a single deleted group to a full forest rebuild. Talk to a recovery engineer about your Active Directory and Entra ID.