How information security practices help everyone
Sep 14, 2020Heather Simpson
Summary
This post details the application security stable counterpart role, where security engineers collaborate with development teams throughout the SDLC to assess risk, review code, and drive security-conscious outcomes. It also highlights initiatives to enable GitLab's Secure tooling (SAST, DAST, Container Scanning) in major product repositories and configure container scanning for Docker images. The author provides advice on writing unit tests for unexpected cases to improve application security and emphasizes GitLab's commitment to transparency in security.
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