Traditional security testing for JS apps has focused on the front-end, but actual security issues most often lie in the backing REST API. Join StackHawk co-founder Scott Gerlach for a quick overview of why you need to rethink how you test your JS apps and how StackHawk can help you find and fix security bugs fast.
Automated Application Security Testing
AI Generated Video Summary
StackHawk is a dynamic application security testing tool that helps developers find and fix security issues. The scan identified a SQL injection issue and a cross site scripting issue. The StackHawk YAML is used to configure the scanner with important information such as the application's location, environment, and ID. The scanner can also be pointed at open API spec or GraphQL definitions. Try StackHawk for free at stackhawk.com and integrate it into your development process to improve software quality.
1. Introduction to StackHawk
StackHawk is a dynamic application security testing tool that helps developers find and fix security issues. It runs active security tests against running applications, handles user input and output safely, and implements OWASP top 10 best practices. The scanner is configured via YAML and provides simple descriptions and examples of patterns to help identify and fix issues. StackHawk integrates with CI/CD workflows and major CI platforms, and it can notify scan results in Slack, Data Dog, or via web hook.
Let's talk about StackHawk. Quickly, StackHawk is a dynamic application security testing tool. You can use it to test your running HTTP applications and API endpoints for security bugs and keep them from becoming vulnerable. You can use StackHawk to run active security tests on your running REST API, GraphQL API, soap API, server-side application, and single-page applications. StackHawk was built for automation and CI CDE to be part of your robust testing strategy for your application development life cycle. It also makes finding, understanding, and fixing security bugs easy.
How does StackHawk work, you ask? Great question! StackHawk runs active security tests against your running applications to ensure that your application is handling user input and output in a safe manner, as well as implementing OWASP top 10 best practices for application security. We can do this against your running application on your local host, in CI CDE workflows, and against applications that have yet to be published on the internet. We also made dynamic testing fast. By placing the scanner as close to the application as possible and by using open standards to inform the scanner, OpenAPI spec, GraphQL, introspection queries, SOAP, WSDL, in addition to the scanner tuning we've made, most StackHawk customer applications scan average around or under 10 minutes.
Finding and fixing security issues is simple with StackHawk. Our focus as a company is to help developers find and most importantly fix security issues. The Stackhawk scanner and platform are built around this simplicity model. The scanner is configured via YAML that lives with the code for the application that you're testing. When StackHawk findings are triaged, the platform is trying to give you the simplest version of the information needed to help you quickly understand what the problem is, with simple descriptions and examples of patterns to help you identify the anti-pattern, be able to recreate the issue with simple curl command to replay the attack, and get you into debug mode stepping through code as fast as possible to help you fix issues and get back to your regular job of creating value for your customers. All of this is CI CD enabled. Again, you can integrate this into your CI process and importantly get feedback into the CI process on scan findings. This information can be used to break a build if you choose. Based on severity of un-triage findings, most of the major CI player logos are shown here on this slide, and even if your particular one isn't, chances are pretty good Stackhawk will work in your platform as long as it can run a Docker container. You can run Docker, you can run Stackhawk. You can also see here Stackhawk integrates with your workflow and information tools. We can notify you of your scan results in a Slack channel, publish that information to Data Dog, or send you a simple web hook message that you can then use to process and do with the data what you choose.
Let's take a look at what running the Stackhawk scanner looks like. As you can see here, I've got a standard server side application. This one is a Pulse app that I want to test for security issues. So over here on my command line, I've got a simple Docker command that I ran. So Docker run Stackhawk, I fed it the stack on yamel, we'll look at that in a second. As you can see, it did a standard crawl looking for all the interesting things on the webpage that it could and then it did an attack.
2. Analysis of Scan Findings and SQL Injection Issue
The scan identified a SQL injection issue and a cross site scripting issue. The SQL injection issue is explained, along with the risks it poses and links to prevent it in different language frameworks. A specific issue is highlighted on the polls SQL path, where a post method has an issue. The scanner's request and response are shown, including a Case When injection. The Validate button provides a curl command to reproduce the attack. The StackHawk YAML code for the polls application is also provided.
So it actively attacked this application for potential security issues. When it was all done, we've got a summary of these findings. So I've actually got a SQL injection issue that I need to take care of, you can see that it's new. I also have a cross site scripting issue that I've done something with before, I actually made a ticket out of this. So now it's in an assigned status. We've got a bunch of other things that we can look at as well. But let's take a look at those two.
Down here at the bottom, we actually have a link to this scan. So we can actually take this link and paste it into a browser. By the way, output in a CICD system would look very much like this, because this is the standard output. So if you did choose to break a build, you would have this same link in CICD output. So we can go over here to our web browser and jump right into the scan that we were looking at. We were just looking at this exact same scan. We've got this SQL injection issue that we can look at quickly. You can see that we've got a SQL injection issue. We're quickly describing what SQL injection is, how to remediate it, what it's about, and what risks it might pose to an application. We also have links to different language frameworks that show you the pattern of how to prevent SQL injection in Spring, Laravel, Django, and Rails so that you can help identify the anti-pattern that we're looking for.
Let's take a look at this particular issue here. We can see that on the polls SQL path, we have a post method that has some kind of an issue. Over on our right-hand panel, we've got a request and response of what the scanner actually did and then came back with. We can see that the scanner made a request here against the application and it responded in some form or fashion. We can actually see that the scanner made a Case When injection here. We can replay this if we wanted to. This is all helping you understand what the scanner is trying to do and what issue it thinks it's found. But, interestingly, we've got this really cool Validate button up here. As I mentioned before, this Validate button gives you a curl command of exactly what the scanner did to identify this particular issue. So, you can copy and replay this attack against an application. Let's take a look at that StackHawk YAML. Here you can see the code that I've used to build my polls application. Inside of this repository, I've also stored the StackHawk YAML.
3. Configuring StackHawk Scanner
The StackHawk YAML is used to configure the scanner with important information such as the application's location, environment, and ID. Additional configuration options include authentication, handling of cookies and CSRF tokens, and excluding specific scan targets. The scanner can also be pointed at open API spec or GraphQL definitions. If time is limited, issues can be quickly pushed to a JIRA ticket and prioritized for future sprints or epochs. Triaged issues will no longer trigger alerts, and builds can continue as normal. Try StackHawk for free at stackhawk.com and integrate it into your development process to improve software quality.
The StackHawk YAML is how you configure the StackHawk scanner. So, you can see the important information that's in here is, where do I find the application I need to test? In this case, it's running on my local machine, so local host 8020. What environment am I in? What is the application ID? That is the minimal amount of information you need to run a StackHawk scan against your application.
There are other pieces of information that help tune the scanner to your application, such as authentication, how to handle cookies and CSRF tokens, as well as things you don't want the scanner to scan. If you wanted to add open API spec or GraphQL, minimal additional configuration is needed to make that happen, to point the scanner at those industry standard definitions of REST API and GraphQL.
Now let's say we don't have time to fix this particular issue. We need to get this feature out for a customer, but we do want to fix it, so we can push this quickly to a JIRA ticket. I can send this to a JIRA Cloud or JIRA DataCenter ticket right now from this particular screen. I can push this issue straight out to JIRA and now I can prioritize that and bring it back out of the backlog when I'm ready to do it in the next sprint or in the next epoch.
As you will see, this has now turned into a triaged status issue, so when we come back here to our summary of findings, you can see that our cross site scripting has been triaged and our SQL injections have been triaged. The next time the scanner finds these things, it will remember that you have triaged them already and it will stop trying to bring your attention to it. If you've configured builds to break, this will undo the build break mechanism and your build will continue as normal.
I hope you enjoyed my talk today and perhaps learned something new about how StackHawk could be integrated into your development workflow. If you'd like to check out StackHawk and see how you can integrate it into your development process to keep pushing the limits on software development quality, you can always start a free trial at stackhawk.com and StackHawk is always free to use on a single application. Hey, thanks for watching everybody. I hope you really enjoy React Summit.