TL;DR: Autonomous penetration testing tools are getting better at generating findings, but Synack argues that benchmark gains still do not solve the harder problem of prioritisation, false negatives, and real-world judgment, especially as authorization flaws dominate modern attack paths, according to Synack. The practical issue is not whether machines can find more, but whether security teams can trust them to identify the one weakness that actually matters.
NHIMG editorial — based on content published by Synack: Autonomy Was Never the Goal
By the numbers:
- Agents solve 16.1% of enterprise-like exploitation tasks in realistic environments, and hints roughly double their success rate.
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes, and as quickly as 9 minutes in some cases.
Questions worth separating out
Q: What breaks when autonomous pentesting runs without human validation?
A: Without human validation, autonomous pentesting produces noisy, low-trust findings that can inflate backlog volume without improving remediation.
Q: Why do authorization bugs remain hard for AI-assisted security testing to catch?
A: Because authorization failures are usually about relationships, ownership, and business context rather than obvious code patterns.
Q: How do security teams know if autonomous testing is working?
A: Look for fewer disputed findings, faster triage, and a higher percentage of issues that map to real attack paths.
Practitioner guidance
- Use autonomous testing as a discovery layer, not a decision layer Route agent findings into a human triage workflow that validates exposure, reproducibility, and business impact before remediation is assigned.
- Prioritise authorization paths in attack-path testing Direct testing effort toward broken access control, entitlement drift, and session-bound privilege escalation rather than generic vulnerability counts.
- Measure coverage, not just findings Track what the machine did not explore, which branches were abandoned, and where human hints changed the result.
What's in the full analysis
Synack's full article covers the operational detail this post intentionally leaves for the source:
- Benchmark-by-benchmark comparisons of AI agent performance against real-world penetration testing environments
- The specific reasoning failures and prioritisation gaps observed in autonomous testing workflows
- Discussion of how the merger combines offensive testing capacity with agentic AI underneath the platform
- The market context around autonomous pentesting claims and why human judgment still matters
👉 Read Synack's analysis of autonomous pentesting and human judgment →
Autonomous pentesting and the governance gap teams are missing?
Explore further
Autonomous pentesting has a prioritisation problem, not a tooling problem. The article shows that modern agents can explore and report at scale, but they still struggle to decide which routes deserve depth. That is the same governance failure practitioners face in identity programmes when entitlement sprawl makes every finding look equally urgent. The lesson is not that automation fails, but that security value depends on judgment layered over discovery.
A question worth separating out:
Q: When should teams keep humans in the loop for AI-assisted pentesting?
A: Humans should stay involved whenever scope, regulatory context, business impact, or custom architecture changes the meaning of a finding. AI can accelerate testing and reporting, but people still need to decide materiality, exception handling, and whether the issue is truly relevant to the environment being tested.
👉 Read our full editorial: Autonomous pentesting still needs human judgment to find real risk