Deploy an autonomous red team agent.
Set a goal such as reading a customer database. AutoAttack chains real attacks at machine speed and uses each new credential or foothold to pursue it.
Temporary Docker container
Authorized network
You set scope and exclusions.
Newly gained access guides the next attack toward your goal.
Campaign report
- Access gained
- How the attack progressed
- Captured evidence
- What supports each result
- Recommended fixes
- What allowed the access
- Objective outcome
- Whether the target was reached
Choose the campaign's starting position.
Open the quickstartRun the Docker command from your campaign page on a dedicated Linux host. The campaign starts when the agent connects. A host on an employee network tests a different starting point from a host on a server network; choose the position that matches your assessment.
- Deployment host
- Linux with Docker running as root
- Network position
- Access to authorized systems
- Cloud connection
- Outbound HTTPS to
agent.autoattack.ai - Target installation
- No persistent agent
You can start without credentials or supply an authorized account to test from its access. The internal network assessment guide helps you choose the starting position and authorized scope.
Set the objective, authorized scope, exclusions and starting access before deployment. Review the reversible changes included in the campaign setup.
Credential attempts use lockout controls. Each campaign runs in a fresh container, and you can request a stop from the campaign page. Read the campaign controls and data handling.
Review the run before you subscribe.
Read a published runThe campaign page updates as the agent attacks and stays available afterward. Follow the access AutoAttack gained and the steps that enabled it. The report guide works through how to check a result and hand it to the system owner.
Access gained
Follow the attack with anonymous target labels that stay consistent throughout the report. Technique and weakness labels remain visible.
Included in a free campaignEvidence and recommended fixes
See the target names, inspect the captured evidence and read the recommended fix beside each access step.
Available with a subscriptionYour discovered host count determines the subscription price. Discovery has no host cap. See pricing before you subscribe.
The report states whether the campaign reached your objective and shows the access it gained. Start a fresh campaign after a network change with the objective and scope needed to test the affected systems. Read the network testing overview to plan recurring access tests.