StackHawk
Sign In
Get a Demo
Blog
API Security Testing

Building Secure CI Pipelines Using GitHub Actions

Scott Gerlach   |   Jul 29, 2020

Share on LinkedIn
Share on X
Share on Facebook
Share on Reddit
Send us an email
Scott Gerlach Blog Image

Last week, I had the privilege of joining Sherif Koussa, Founder and CEO of Software Secured , to chat about ensuring security in production applications by adding application security testing into the CI pipeline.

Watch the video below for details on how to add security checks into CI using GitHub Actions , including:

  • Dynamic Application Security Testing (DAST)

  • Static Application Security Testing (SAST)

  • Secrets Detection

Video

For more details on instrumenting StackHawk with GitHub Actions, check out our documentation .

More Hawksome Posts

DAST Onboarding in Minutes with StackHawk’s GitHub Copilot Custom Agent

DAST Onboarding in Minutes with StackHawk’s GitHub Copilot Custom Agent

We are excited to announce StackHawk’s GitHub Copilot Custom Agent that analyzes your repository’s source code, generates a complete DAST configuration, and creates a working CI/CD security testing workflow—all in just minutes. No more setup friction between development and security. No more “we’ll add security testing later.” Just intelligent configuration that identifies what you should test, and starts finding runtime vulnerabilities faster.