Automated security testing for DevSecOps
Jul 8, 2020Vanessa Wegner

Summary
This post details how to automate security testing in software development, specifically focusing on SAST and DAST scans. It outlines four ways to integrate automated security testing: running SAST scans for every code change, automatically initiating work tickets or stopping builds based on scan results, applying policies automatically upon code commit, and analyzing running web applications with DAST scans. It also discusses the benefits of automated security, the difference between automation and orchestration, and common types of security automation tools.
More from the Security Control Framework trail
- Track organization-wide security risk in one dashboard
- Dependency Firewall: Block risky packages before the build
- Two front doors: Module-level access in a Django GRC app
- How GitLab tracks vulnerabilities through refactors and reformatting
- Shai-Hulud copycat campaign targets Python developers through PyPI typosquatting