My main use case for StackHawk is for DAST, DAST, and API scans, providing early pen testing results. StackHawk helps our team become aware of issues earlier, leading to less tech debt and better security. The fast, tunable scans and effective documentation enhance developer collaboration in my organization effectively. I appreciate StackHawk for its comprehensive documentation, which is incredibly helpful for passing on to developers, ensuring everyone shares responsibility in writing scans. I love the speed and configurability of StackHawk scanning capabilities, which are very impressive. It enables me to fine-tune the balance between cost and effective scan speed to suit our needs. StackHawk embodies a shift-left mentality, where it allows us to identify issues earlier in the development cycle, thereby reducing technical debt and enhancing application security in my organization. Regarding my use case with StackHawk, the product is very rich in features, and the support from StackHawk team ensures the success of using this product. I also love the scanning speed, which previously was a challenge with Tenable Nessus, and that has drastically improved since we switched to StackHawk, especially with its configuration as code approach as opposed to a traditional web interface. Additionally, the initial setup was very quick and simple, making it easy to get started and integrate seamlessly with our existing tools like GitHub, CodeQL, and Jira for handling findings much more effectively.
My main use case for StackHawk is to analyze our application live in our EKS cluster. A specific example of how we use StackHawk in our EKS cluster is that we deployed an agent authenticated to the StackHawk platform and it is in charge of analyzing our different repositories, letting us know if we have any open vulnerabilities within our base code. Every scenario of analysis is completely published into the StackHawk platform so we can see if we have open vulnerabilities to solve and how much time it takes to perform the analysis.
Manager Sec Ops at a real estate/law firm with 501-1,000 employees
Real User
Top 20
Jan 14, 2026
My main use case for StackHawk is primarily as a PCI requirement for DAST. As a quick specific example of how I use StackHawk for that PCI requirement, it is one of the controls that sits alongside the requirement to have SAST. I deployed StackHawk and Snyk because those two products were easily integrated and therefore providing a unified view of vulnerabilities that existed either during the CI/CD process or running live.
StackHawk provides a dynamic application security testing tool designed to identify and fix vulnerabilities in modern CI/CD workflows quickly. It seamlessly integrates into developers' pipelines to deliver real-time feedback, helping teams prioritize and address application security efficiently.Known for its developer-first approach, StackHawk empowers teams to conduct proactive security testing at every stage of the software development lifecycle. It offers robust scanning capabilities that...
My main use case for StackHawk is for DAST, DAST, and API scans, providing early pen testing results. StackHawk helps our team become aware of issues earlier, leading to less tech debt and better security. The fast, tunable scans and effective documentation enhance developer collaboration in my organization effectively. I appreciate StackHawk for its comprehensive documentation, which is incredibly helpful for passing on to developers, ensuring everyone shares responsibility in writing scans. I love the speed and configurability of StackHawk scanning capabilities, which are very impressive. It enables me to fine-tune the balance between cost and effective scan speed to suit our needs. StackHawk embodies a shift-left mentality, where it allows us to identify issues earlier in the development cycle, thereby reducing technical debt and enhancing application security in my organization. Regarding my use case with StackHawk, the product is very rich in features, and the support from StackHawk team ensures the success of using this product. I also love the scanning speed, which previously was a challenge with Tenable Nessus, and that has drastically improved since we switched to StackHawk, especially with its configuration as code approach as opposed to a traditional web interface. Additionally, the initial setup was very quick and simple, making it easy to get started and integrate seamlessly with our existing tools like GitHub, CodeQL, and Jira for handling findings much more effectively.
My main use case for StackHawk is to analyze our application live in our EKS cluster. A specific example of how we use StackHawk in our EKS cluster is that we deployed an agent authenticated to the StackHawk platform and it is in charge of analyzing our different repositories, letting us know if we have any open vulnerabilities within our base code. Every scenario of analysis is completely published into the StackHawk platform so we can see if we have open vulnerabilities to solve and how much time it takes to perform the analysis.
My main use case for StackHawk is primarily as a PCI requirement for DAST. As a quick specific example of how I use StackHawk for that PCI requirement, it is one of the controls that sits alongside the requirement to have SAST. I deployed StackHawk and Snyk because those two products were easily integrated and therefore providing a unified view of vulnerabilities that existed either during the CI/CD process or running live.