How open source contributions accelerate GitLab Secure
This post details GitLab's strategy for building secure systems in the open, emphasizing "shifting left" by integrating security tools directly into developer workflows. It highlights the suite of GitLab Secure features (SAST, DAST, Container Scanning, Dependency Scanning, License Scanning, Secret Detection, API Fuzzing, Coverage Fuzzing) and the importance of community contributions and integration partners. Specific community contributions mentioned include Mobile SAST support via MobSF, Helm Chart support, performance improvements to Fuzz testing, updates to secret detection and dependency scanning, OS updates for scanners, .NET Framework support, and a full list of community contributions for Secure. It also mentions the integration partner program.
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