Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Eradication in Incident Response?

Eradication removes the attacker and everything they left behind: malware, web shells, scheduled tasks, rogue accounts, and the vulnerability that let them in, ideally in one coordinated action.

Illustration for the cybersecurity term Eradication
Home / Blog / Cybersecurity Terms / What Is Eradication in Incident Response?
17 November 2026

What Is Eradication in Incident Response?

What Is Eradication in Incident Response?

Eradication is the phase where the adversary is removed from the environment and the conditions that allowed the intrusion are corrected. It follows containment and precedes recovery in the NIST SP 800-61 lifecycle, and it is where incidents are most often declared over prematurely. The measure of success is not that the malware is gone; it is that the attacker cannot return by any route they established.

Do Not Start Until Scope Is Known

The most expensive mistake in incident response is piecemeal eradication. An intruder with five footholds who loses one will use another, and will now know they have been detected. They will also change tooling, which costs you the indicators you were hunting with. So eradication waits for the investigation to map the full extent of the compromise, which is precisely why containment exists — it buys the time to do that mapping safely.

Decide the cut-over point explicitly, prepare every action, then execute them together: typically an out-of-hours window with the response team, platform engineers, and identity administrators all working from one runbook.

What Has to Be Removed

Credentials Are the Hard Part

Assume every credential that existed on a compromised host is known to the attacker. In an Active Directory compromise that means service account passwords, local administrator passwords, and the krbtgt account, which must be reset twice with enough delay between resets for replication to complete — otherwise previously issued golden tickets remain valid. Reset password hashes, revoke active sessions and refresh tokens in cloud identity platforms, and rotate certificates and API keys that could have been exported. A golden ticket issued before the reset is a ten-year credential if you skip this step.

Rebuild or Clean?

Rebuild from a known-good image wherever practical. Cleaning a host assumes you found everything, and modern intrusions rarely give you that confidence, particularly where kernel-level or firmware persistence is possible. Rebuilding is not always available — legacy application servers and OT systems may have no reproducible build — and in those cases document the compensating controls: enhanced monitoring, strict network restriction, and a plan to replace the system.

Restore data rather than systems, and check the restore point against the intrusion timeline. Recovering from a backup taken after initial access reinstates the attacker’s foothold, which is a surprisingly common way organisations suffer the same incident twice.

Verify, Then Watch

Eradication is not complete when the actions are executed. Rescan for the indicators, hunt again for the techniques rather than the artefacts, and keep elevated monitoring on the affected segment for weeks. Attackers who have invested in access frequently return, and the return is usually quieter than the original intrusion. Feed everything into the lessons learned review so the detections you wished you had become the detections you have.

At Privia Security, we plan and execute coordinated eradication as part of our investigation and incident response services, because the sequencing matters as much as the technical steps.

FAQ – Frequently Asked Questions

What Is the Difference Between Containment and Eradication?

Containment limits what the attacker can still do while you investigate, typically by isolating hosts and disabling accounts. Eradication removes them and everything they installed, and closes the vulnerability that allowed access. Containment is fast and reversible; eradication is deliberate and should happen once, as a single coordinated action across every affected system.

Do I Need to Reset the krbtgt Account?

Yes, if the domain was compromised. The krbtgt account signs Kerberos tickets, so an attacker who extracted its hash can forge tickets for any user indefinitely. Reset it twice, leaving enough time between resets for replication across all domain controllers, otherwise previously issued forged tickets stay valid and the compromise persists through every other remediation step.

Should Compromised Machines Be Rebuilt or Cleaned?

Rebuild from a known-good image where you can. Cleaning relies on having found every artefact, which is difficult to assert after a sophisticated intrusion and impossible where firmware or kernel persistence is suspected. Where rebuilding is not feasible, such as legacy or operational technology systems, document the risk and apply compensating network restrictions and monitoring.

How Do I Know Eradication Worked?

You do not know immediately, which is why verification continues after the action. Rescan for known indicators, hunt for the techniques rather than the specific artefacts, review authentication logs for the reset accounts, and keep enhanced monitoring on affected segments for several weeks. A quiet return through a missed foothold is the most common failure mode.

Related Terms

You May Be Interested In These

What Are SS7 Attacks?

Cybersecurity Terms

17 November 2026

What Are SS7 Attacks?

Read More
What Is an Indicator of Attack?

Cybersecurity Terms

17 November 2026

What Is an Indicator of Attack?

Read More
What Is a Human-Machine Interface?

Cybersecurity Terms

17 November 2026

What Is a Human-Machine Interface?

Read More