According to a recent LinkedIn post from StackHawk, the company is positioning AI-driven penetration testing as a complement to, rather than a replacement for, dynamic application security testing (DAST). The post contrasts episodic, high-cost manual pentests with AI-enabled automation, suggesting significant gains in speed and cost efficiency for traditional pentest workflows.
Claim 30% Off TipRanks
- Unlock hedge fund-level data and powerful investing tools for smarter, sharper decisions
- Discover top-performing stock ideas and upgrade to a portfolio of market leaders with Smart Investor Picks
The company’s LinkedIn post highlights DAST as a continuous, build-by-build safeguard that can run on every commit, pull request, and local development environment. It notes that AI penetration testing, even when accelerated to hours, may still be too slow and expensive to attach to each pull request, implying that StackHawk’s shift-left DAST tooling is aimed at the higher-frequency, always-on segment of the application security market.
As shared in the post, StackHawk is presented as suited to scan API endpoints and authentication flows, including code generated by AI coding assistants. This framing suggests a strategy to stay relevant as AI-generated code volume grows, potentially expanding the addressable market for automated security testing and reinforcing demand for tools that integrate directly into developer workflows.
For investors, the emphasis on a “DAST as baseline, AI pentest as pressure test” model points to a layered security approach that could support recurring revenue from continuous scanning alongside periodic AI pentesting spend. Positioning StackHawk at the core of frequent development cycles may enhance stickiness with engineering teams and differentiate the platform within the competitive application security and DevSecOps landscape.