CyberKit

Indicator of Attack

Also called IOA.

Evidence of adversary behavior while an attack is still under way.

What it is

An observable that reflects what an attacker is trying to do (the sequence of actions, techniques, and intent behind an intrusion) as opposed to a static artifact. Where an indicator of compromise says something bad happened, an indicator of attack describes the behavior as it occurs.

Why it matters

Because IOAs key on behavior rather than known-bad values, they can catch novel tooling and fileless activity that signature-based indicators miss, and they map naturally onto TTP-based detection.

In practice

Alerting on the behavioral chain of a process spawning a shell and then reaching out for credentials, regardless of which binary is involved.

What to look for

  • Behaviors such as credential dumping or lateral movement in progress.
  • Sequences of actions rather than single artifacts.
  • Alerts that fire before data leaves.

Common mistake

Treating it like an IOC list. It describes behavior, so it needs behavior detections.

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.

  • CrowdStrike Falcon Commercial

    An EDR agent that records process, file and network activity on each host and flags this kind of behavior.

  • Microsoft Defender for Endpoint Commercial

    Microsoft's EDR, with advanced hunting tables you can query for this activity across Windows, macOS and Linux.

  • Velociraptor Open source

    Collects and hunts for artifacts across many hosts at once, often during live response. Our notes.

  • Sysmon Free

    Free Windows logging of process starts, network connections and more, which many detections rely on. Our notes.

Read next

Sources