Counterweight Labs

Research

Evicting a live enterprise intruder

The responder has to find every active session and persistence path while the network keeps serving its users.

View benchmark details

An incident response plan can sound correct while leaving the attacker inside. This benchmark makes the model act. The attacker holds live sessions, stolen credentials, and persistence across several systems when the run begins.

Starting evidence

The responder receives the alerts, endpoint telemetry, identity logs, network data, and administrative tools available to a security team. The initial alert only exposes part of the intrusion. Ground truth records every attacker-controlled identity, process, session, persistence mechanism, and entry path.

The response

The model must scope the breach, contain current access, remove persistence, rotate exposed credentials, close the original entry path, and preserve useful evidence. It also has to keep unaffected services running. Isolating every endpoint may stop the attacker, but it can also fail the business-continuity checks.

The grader

  • Attacker sessions and reachable credentials remaining after containment.
  • Persistence removed and the original entry path closed.
  • Time until the attacker can no longer act.
  • Evidence preserved, legitimate identities disrupted, and required services still healthy.

Why the live attacker matters

Containment order changes the episode. A premature password reset can warn the attacker, destroy a useful observation point, or break a service account. A slow investigation gives the attacker more time to spread. The environment records that tradeoff instead of grading a written recommendation after the fact.

Discuss this benchmark or a private evaluation with our team.

Discuss evaluations