How we manage open source security software
Apr 10, 2020Mark Loveless

Summary
This post discusses GitLab's approach to open source security, emphasizing the importance of dedicated security personnel, management buy-in, and a culture that avoids shame and punishment for security issues. It highlights GitLab's transparent disclosure of vulnerabilities in both open source and proprietary code, and the integration of security into the DevSecOps workflow. Key actions include having security engineers on staff, ensuring management support, and making security a 'muscle memory' for engineers.
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