How we made GitLab more secure in 2020
Dec 16, 2020Johnathan Hunt
Summary
This post details the implementation of functionality to identify AWS instance keys accidentally disclosed in public repositories on GitLab.com. This functionality alerts AWS and displays findings in the security dashboard. It also discusses the improvement of vulnerability management across application security, infrastructure security, and bug bounty programs, including the adoption of a GRC tool. The post also introduces a next-generation SIEM (Panther Labs) for improved visibility, detection, and response, and the creation of a public 'Red Team Tech Notes' project for sharing technical challenges and solutions.
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