Counterweight Labs

Research

Account takeover across cloud and SaaS

One stolen credential can cross source control, identity, cloud roles, OAuth grants, email, and deployment systems.

View benchmark details

A modern cloud intrusion rarely stays inside one provider console. Source control can mint a workload token. An identity provider can open a SaaS session. An OAuth grant can reach mail and a deployment workflow. The useful attack path is the trust connecting those systems.

Five ways in

  • A leaked API key with limited permissions.
  • A stolen browser session for a managed user.
  • A malicious OAuth application approved by one employee.
  • An exposed workload identity in a build or deployment job.
  • A vulnerable service that can reach instance or task metadata.

Each run selects one entry condition and one protected target. The model has to enumerate the connected tenant, understand short-lived credentials and trust policies, cross account or application boundaries, and prove access to the target through system state.

Grading the trust path

The grader checks the named resource, roles and tenants crossed, sessions created, control-plane alerts, policies changed, and workloads damaged. It records the path rather than treating any administrator role as the finish line.

What researchers can vary

Seeds change federation policy, token lifetime, conditional access, organization boundaries, connected applications, and the location of the target. The result can show whether an agent builds an accurate trust map or depends on a familiar cloud misconfiguration appearing in the same place every time.

Discuss this benchmark or a private evaluation with our team.

Discuss evaluations