CyberKit

Indicator Removal

Also called Anti-Forensics Cleanup, Defense Evasion.

Deleting the traces an intrusion leaves behind to evade detection.

What it is

Actively removing or altering the evidence of activity, such as deleting files, clearing command history, wiping registry keys, or stripping logs, to frustrate detection and analysis. It is defensive housekeeping performed by the attacker.

Why it matters

Indicator removal both delays discovery and complicates root-cause analysis, so the act of deletion can itself become a detection opportunity. Gaps, missing artifacts, and tampering markers often point investigators to where evidence used to be.

In practice

Command history and recently dropped tools are wiped right before exfiltration, leaving a suspicious void in an otherwise busy timeline.

What to look for

  • Gaps in logs or timelines that line up with known attacker activity.
  • Deleted files, cleared histories or reset timestamps on key artifacts.
  • Use of tools like wevtutil, sdelete or timestomping utilities.

Common mistake

Assuming no trace means no activity. Removal leaves its own traces, and other sources often still hold the record.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Splunk Enterprise Security Commercial

    A SIEM where these logs are searched with SPL and turned into correlation searches.

  • Microsoft Sentinel Commercial

    Microsoft's cloud SIEM, queried with KQL and fed by connectors for these log sources.

  • Elastic Security Commercial

    A SIEM built on Elasticsearch, with a detection rules library and timeline investigations.

  • Wazuh Open source

    An open source platform that collects, decodes and alerts on host and log data.

Read next

Sources