AEGLIX News
A survey of 500 security and engineering leaders across the US and UK conducted by Intruder found that only 4% believe their current testing frequency provides sufficient coverage, while 88% of those running scheduled pentests worry about unmapped risk introduced between tests. The research highlights a significant gap between deployment velocity and security validation, with 68% of organizations deploying code to production at least daily and 37% deploying multiple times a day, yet nearly half go more than a month between full pentests on web applications and APIs.
The survey documents a shift toward AI-driven penetration testing, with 55% of organizations already using AI pentesting across their environment and 36% having tried it but not yet adopted it at scale. Adoption is highest among the largest organizations surveyed, those with 5,000 to 10,000 employees, where 71% report using AI pentesting across their environment. Nine in ten leaders agree that the traditional annual pentest is dead and that continuous AI pentesting is now required, reflecting a consensus on the need for more frequent security validation.
Contrary to assumptions about quality concerns, only a quarter of respondents see AI testing quality as a top concern. Instead, the primary barriers to adoption are data privacy at 40%, safety on production systems at 36%, and auditor or regulator acceptance at 28%. Trust issues center on visibility and reproducibility: 46% say lack of visibility into what was tested (25%) or lack of reproducible proof of exploitability (21%) would most damage trust in AI pentesting. Operational burden is also significant, with 56% of teams spending six hours or more per week validating findings from their security tooling.
The survey indicates that 42% of organizations accept risk and ship code without additional security checks between pentests, underscoring the pressure to maintain deployment velocity. While the findings document current adoption levels and barrier perceptions, the source material does not detail specific remediation actions, patches, or vendor notifications taken in response to these concerns. The data reflects leader sentiment on required capabilities rather than confirmed mitigation steps implemented across the surveyed environments.
Report prepared 2026-11-18 · Based on reporting from The Hacker News. Source publication date above; subsequent developments may not be reflected.