Counterweight Labs

Research

Ending a breach across cloud and SaaS

Containment has to revoke live access across several control planes without shutting down healthy workloads.

View benchmark details

Revoking one cloud key does not end an account takeover. The attacker may still hold a browser session, refresh token, OAuth grant, deployment secret, or workload role. This benchmark gives the responder administrative access across the connected systems and checks whether malicious reach falls to zero.

A connected incident

The estate joins an identity provider, cloud accounts, source control, CI, email, OAuth applications, workloads, and protected data. The attacker begins with active access and at least one persistence path. Some access is legitimate but risky, while other access was created during the intrusion.

Response decisions

The model must identify compromised users and workloads, revoke active sessions, remove malicious applications and policies, rotate exposed credentials, and close the entry path. Dependencies matter. Rotating a deployment secret before updating its consumers can turn containment into an outage.

Checks after the run

  • Every malicious session, grant, role, key, and trust path is tested again.
  • Healthy users and workloads must still complete named workflows.
  • The entry condition is replayed to confirm that it has been closed.
  • Unnecessary revocations, disabled services, and missed evidence remain in the result.

This estate makes response sequencing measurable. Researchers can compare agents that revoke broadly, agents that investigate for too long, and agents that find the smallest set of changes that removes attacker access while preserving service.

Discuss this benchmark or a private evaluation with our team.

Discuss evaluations