Part5 Inbuild Devsecops security features Sast and Dast provided by Gitlab

SAST (Static Application Security Testing) and DAST (Dynamic Application Security Testing) provided by GitLab ensure security testing is seamlessly automated into the CI/CD pipeline.

1. Why We Need This Use Case

With increasing risks of cyber threats, integrating security into DevOps processes is critical. SAST (Static Application Security Testing) and DAST (Dynamic Application Security Testing) provided by GitLab ensure security testing is seamlessly automated into the CI/CD pipeline. This use case emphasizes the need for identifying vulnerabilities during development and runtime without relying on third-party tools.

---

2. When We Need This Use Case

• To automate security testing in CI/CD pipelines.

• To comply with industry standards like OWASP Top 10, GDPR, and PCI-DSS.

• For early identification and remediation of vulnerabilities in the development lifecycle.

• To reduce costs and complexity associated with third-party security tools.

---

3. Complete first before this usecase

Part 1 - Implementing DevSecOps Pipeline using Gitlab - Link

Part 2.1 - Implementing SAST in Gitlab DevSecOps Pipeline using SonarQube with no code coverage - Link

Part 2.2 - Implementing SAST in Gitlab DevSecOps Pipeline using SonarQube with Code Coverage - Link

Part 3 - Implementing SAS in Gitlab DevSecOps Pipeline using Synk - Link

Part4 - Implementing DAST in Gitlab DevSecOps Pipeline using OWASP ZAP - Link

---

4. Challenge Questions