Only the steps that
reached the objective.
Most security tools hand you a list of maybes. AutoAttack hands you the attack itself: an autonomous adversary that breaks in, chains what it finds, and proves every step it takes.
Deploythe problem
the list The list is the whole product. Hundreds of maybes, ranked by a score, with no way to tell which one a real attacker would ever use.
the maybe A maybe isn’t a breach. It says a door might be unlocked. It never says who walks through it, or what they reach once they do.
the wait So the list sits there. The path it hinted at stays open the whole time nobody’s sure it’s real.
the standard
it does it AutoAttack doesn’t describe what might happen. It does it, then shows you. Every line in the report is an attack it completed, captured as it ran.
not a guess Everywhere else, an entry is a guess. Here it’s something that already happened: a step it took, with the evidence to prove it.
no maybes If it can’t prove something, it isn’t reported at all.
nothing spare The report holds the steps that led to what the adversary achieved, and stops there. A weakness it never used to get anywhere isn’t on the page, so there is no ranking to argue about and no second list to reconcile. How the report reads
the method
every path at once It works every path at once, not one after another. The full benchmark
precise It throttles to your real lockout policy, touches only what it needs, and leaves nothing on disk.
nothing to set up It arrives as one container, runs for the engagement, and is gone after it. Nothing to install, nothing to integrate first: it takes the estate as it stands, whatever mix of operating systems is in it, whatever its size or topology.
it doesn’t stop It doesn’t get bored, distracted, or call it a day. It works until the goal is met, or until every path is spent.
the reach
the way in Run the container on any Linux host inside the estate. From there it starts where a real intruder starts — a web app, a file share, a laptop on the guest VLAN — with no agent on any host and no directory it depends on.
the chain From there it keeps moving. A leaked credential, a trusted link between machines, a service no one remembered. It turns each one into the next move.
deep One foothold is all it needs. It works inward, host to host, until it reaches what matters: your data, your domain, the keys to everything.
the boundary An application-scoped test stops at the login page; the intrusion does not. The same run carries that foothold across identity, cloud, SaaS, Linux and your data stores, if that is where the path to your objective runs.
the goal
you Domain Admin. The customer database. The CEO’s inbox. You decide what a breach would mean for you.
autoattack You set a goal. AutoAttack goes after it, and comes back with the chain it built.