Customer Success Story
How Hagerty Scaled AppSec Across 40+ Developer Teams with StackHawk
Hagerty’s DevOps Security team rolled out StackHawk to more than 40 development teams in about two quarters. The playbook: coordinate implementation with developer sprint cycles, build repeatable patterns, and make the work easy for engineers to run with.
AppSec scaled without becoming a bottleneck
Wide-scale developer adoption
Distributed ownership across 40+ development teams
Use Case
Scaling DAST across dev teams
Industry
Insurance
Developers
350+
StackHawk is a great tool. The documentation is great, it’s very clear how to implement it in different environments, and flexible for all kinds of different scenarios or use cases.
The Problem
One security engineer responsible for 40+ developer teams couldn’t manually drive adoption. The challenge wasn’t technical or political — it was operational: getting StackHawk work scheduled, prioritized, and completed across dozens of independent sprint cycles.
The Solution
Hagerty treated the rollout as a project management problem. By partnering with PMs, building reusable stack templates, and leading with developer-friendly messaging, they distributed the work without distributing the burden.
The Results
In roughly two quarters, Hagerty deployed StackHawk across all 40+ teams without slowing engineering down — proving that AppSec at scale is a coordination problem first, and a technical one second.
The Problem
When John Mercer, DevOps Security Engineer at Hagerty, decided to scale StackHawk across more than 40 developer teams, the challenge wasn’t technical. Leadership buy-in at the CIO and CISO levels also came easily. The harder problem was operational: translating that priority into scheduled, completed work inside existing sprint cycles, with one security engineer covering dozens of teams.
As Mercer put it, “One person can’t go through 20, 30, 40, 100 teams… You have to distribute the work.”
Choosing a Solution
Hagerty took a coordination-first approach to the rollout, built around three principles:
Treat scale as a project management problem
Mercer partnered with Hagerty’s project managers to prioritize the StackHawk work, assign deadlines, and fit implementation into upcoming sprints. “The real problem wasn’t technical, and it wasn’t the devs. It’s an easy product to implement. It was a project management problem.
Templatize and repeat
Before rolling out broadly, Mercer configured and optimized initial scans across Hagerty’s main stacks (.NET, Python, and Node), then reused that work as a template every team could copy. “Once there’s a pattern, you can simply copy it with very little additional work needed.
Lead with value, not mandates
Mercer communicated StackHawk’s value in terms that developers care about: “I always led with ‘StackHawk mimics a real-world attack.’ Then I reassured them that I will never block them with StackHawk. It’ll only add like five minutes to their pipeline, and then they’re covered.” That message landed because Hagerty’s Security and Engineering teams had already invested in a strong working relationship.
Experience with StackHawk
The takeaway for other organizations: treat AppSec scale as a coordination problem first, then a technical one. Build the pattern, communicate the value, and make it easy for teams to run with it.
The real problem wasn’t technical, and it wasn’t the devs—It’s an easy product to implement. It was a project management problem.
Learn How to Scale AppSec Testing Coverage With the SOAR Framework
Scale runtime security testing beyond the pilot. The SOAR Framework maps key milestones across four phases—and breaks down the meetings, red flags, and pro tips to scale coverage fast without becoming a bottleneck.
Explore Our Customer Stories
Interested in seeing StackHawk at work?
Schedule time with our team for a live demo.
