Module 06 of 10

Security Testing Automation

Lessons

About This Module

Knowing which weaknesses to look for is only useful if you can check for them on every change. Security testing automation moves those checks into your pipeline, so each commit is scanned the same way without anyone having to remember to run a tool. Problems are found while they are still cheap to fix, and the pipeline can stop a risky change before it ships.

You'll start with the three main kinds of testing: SAST, which reads your source code, DAST, which attacks the running application, and SCA, which checks the third-party libraries you depend on. Then you'll see each one in practice with SonarQube, OWASP ZAP, and Trivy running inside a pipeline.

Once your code and dependencies are being scanned automatically, you'll be ready for the next module, Container & Kubernetes Security, where you secure the images and clusters that your application runs on.

Lessons

4 videos
01

Security Tools Explained: SAST vs SCA vs DAST (With Examples + When to Use)

A simple explanation of the three testing approaches, with real examples and where each one fits in the development process.

02

Dockerized SonarQube Setup and Static Code Analysis Tutorial

Run SonarQube with Docker and use it to perform static code analysis, so you see what a SAST tool reports on real code.

03

DevSecOps with GitHub Actions and OWASP ZAP (Live Code Session)

A live coding session on adding OWASP ZAP to GitHub Actions to run dynamic security scans as part of a pipeline.

04

Security Scanning in Your CI/CD Pipeline with GitHub Actions and Trivy

Integrate Trivy into a CI/CD pipeline to scan the filesystem, container images, and Helm charts for vulnerabilities and misconfigurations.