AI is speeding up how software is built, which means more code, more changes, and more chances for vulnerabilities to reach production. It's speeding up how attackers find and exploit them too, with time-to-exploit now down to a single day. Security testing has to keep up with both.
AI pentesting has emerged as a way to run in-depth tests whenever teams need them, instead of waiting for the next scheduled pentest. To see how far adoption has come and what security teams need from it, Intruder surveyed 500 security and engineering leaders across the US and UK. Read on for the top findings.
68% of organizations deploy code to production at least daily, and 37% deploy multiple times a day. Understandably, pentesting runs on a much slower cycle. Nearly half (47%) go more than a month between full pentests on their web applications and APIs. Those figures are for each organization's most frequently tested application, so the rest of their estate is tested less often still.
Running a human-led pentest as often as code ships has never been realistic, largely because of the cost. But it means a vulnerability introduced in one release can go weeks or months without a pentest, and only 4% of security leaders believe their current testing frequency gives them sufficient coverage.
Most teams cover the gap between pentests with a mix of approaches, but 42% accept the risk and ship code without additional security checks in between. Automated scanning in the build pipeline, more frequent manual pentests, internal AppSec teams, and AI-driven pentesting are each used by around half.
Source link







