What is our primary use case?
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.
How has it helped my organization?
StackHawk has positively impacted my organization.
StackHawk has been able to address the need for a DAST scanner that supports ethical hacking, enables early vulnerability detection, and also enhances secure development practices. I love it because it offers automation where it automates security assessments and allows our cybersecurity team and development teams to identify weaknesses in the web applications before they can be exploited. Its capabilities facilitate proactive security testing, helping my organization integrate security into the Software Development Life Cycle (SDLC) and also adopt a shift-left approach. With StackHawk, we have been able to strengthen our security posture while ensuring compliance with industry standards and best practices in my organization.
What is most valuable?
The best features StackHawk offers include improved handling of findings more easily due to its scanning speed and the configuration-as-code approach that help my team day-to-day.
In terms of features, the shift-left mentality allows us to identify issues earlier in the development cycle, thereby reducing technical debt and enhancing application security. I also love the support from StackHawk team, which ensures the success of using the product. The scanning speed, which was a challenge when we were using Tenable Nessus, has drastically improved since switching to StackHawk. I also love the intuitive user interface and comprehensive documentation, which enhances our user experience, allowing my team to quickly address security issues. I also love the fast integrations into CI/CD pipelines, which makes it very valuable for us to identify security vulnerabilities earlier in the development processes.
What needs improvement?
I believe a learning path should be added to help users maximize the potential of StackHawk. While the tool is powerful and intuitive, a structured learning path will provide step-by-step guidance on configuring scans, interpreting results, and implementing security best practices.
StackHawk needs more reporting capabilities and more dashboard views to showcase the progress of vulnerabilities remediation. Additionally, some customization of scan policies will be neat, as the current way to apply policies for scans is very manual.
StackHawk is a strong solution, but improved reporting, easier integration, and more AI-driven recommendations would make it even more effective. Overall, I am highly satisfied with its capabilities and continued improvement.
For how long have I used the solution?
I have been using StackHawk for four years.
What do I think about the stability of the solution?
StackHawk is very stable because we have experienced minimal downtime. It is reliable for our application security testing, helping us identify vulnerabilities consistently and integrate well into our development workflow with minimal disruptions.
What do I think about the scalability of the solution?
StackHawk scales well with our application and development teams as they grow. It supports automated security testing across multiple applications, and it integrates smoothly into our CI/CD pipelines, helping us maintain security without significantly slowing development down.
How are customer service and support?
According to my experience, customer support has been very helpful and responsive. The guidance provided makes it easier to resolve technical issues very easily, and my experience has been very positive so far with the support team. I would rate customer support a nine out of ten.
Which solution did I use previously and why did I switch?
Earlier in the review, I mentioned we switched from Tenable Nessus.
The reason we switched from Tenable Nessus is that we relied more on manual security testing and traditional vulnerability scanning. We adopted StackHawk to automate application security testing, identify vulnerabilities earlier, and integrate security checks into our development workflow.
What was our ROI?
StackHawk has been really helpful. It is very easy to use even for non-technical users, and I love that because of the intuitive user interface and the documentation guidance, which is very plenty. StackHawk has helped us save time by automating security testing and identifying vulnerabilities earlier in the development cycle. We estimate a saving of four to five hours per week on manual testing and also troubleshooting while improving efficiency and reducing rework without needing additional staff.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing was straightforward, with more flexible pricing plans and clear licensing options.
Which other solutions did I evaluate?
Intruder and GitLab were some of the tools that we evaluated before switching to StackHawk.
What other advice do I have?
My experience with StackHawk has been very credible, and I would rate them a five out of five. I chose five out of five for StackHawk for a couple of reasons: it enables me to set up any type of authenticated scans due to its YAML configuration setup, and it is possible to run internal scans since it only needs the binary to run it. Customer support has also been very great so far; they are always ready to answer any questions. Even their bot helps a lot. The integration they have with Snyk makes it great for deeper analysis, enabling us to make data-driven decisions easily.
Regarding governance and security for StackHawk AI capabilities, I feel the AI features are managed in a way that ensures my data is kept safe and that there are good controls or transparency about how the AI is used. I absolutely trust how StackHawk handles sensitive information or automates decisions using AI.
StackHawk accuracy and reliability of output have been consistent and trustworthy in our experience, and I love it. It focuses on transparency and secure practices, which builds confidence in using AI for our application security.
My experience with StackHawk has been very positive, and I highly recommend integrating StackHawk into your CI/CD pipeline early, starting with the critical applications and configuring scans to match your security needs. I encourage you to take time to understand the findings and tune scan settings to reduce false positives. This will help your team identify vulnerabilities earlier, improve efficiency, and also get the most value from the platform. I would rate StackHawk a five out of five overall.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
Disclosure: My company does not have a business relationship with this vendor other than being a customer.