Scoping
Determining the full extent of an incident: every affected asset.
What it is
Scoping is the investigative work of determining the full extent of an incident: which hosts, accounts, and data were affected, and how far the adversary reached. It draws the boundary of what has been compromised.
Why it matters
Response succeeds or fails on accurate scoping. Eradication and recovery fail if even one compromised system or account is missed, so under-scoping lets an adversary quietly persist through the cleanup.
In practice
Sweeping for the attacker's indicators across every endpoint to confirm the breach reached three hosts and not thirty.
What to look for
- Every host, account and system the attacker touched.
- Indicators searched across the whole environment, not just the first host.
- Time ranges extended back to the earliest activity.
Common mistake
Containing before scoping. You might evict the attacker from one host while missing the rest.
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
- Containment: Stopping an incident from spreading while you investigate.
- Eradication: Removing the threat and the attacker's footholds from the environment.
- Crown Jewel Analysis: Identifying an org's most critical assets to focus defense on them.