The backstory on GitLab's security hardening documentation
Aug 1, 2023Mark Loveless
Summary
This post details the origins and development of GitLab's security hardening documentation, including field research, attack scenarios, and guidance on when and how to apply hardening measures to self-managed instances. It emphasizes the importance of threat modeling and adapting recommendations to specific environments.
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