The developer-security divide: frank talk from both sides
Aug 13, 2020Brendan O'Leary

Summary
This post discusses the challenges developers face in adopting security testing tools like SAST and DAST due to high setup barriers and noisy results. It highlights GitLab's approach of integrating security findings into merge requests, allowing developers to validate and address issues early. The security team's role in tuning tools, assessing trends, and providing context is also emphasized. The conversation underscores the need for a shared culture of security and collaboration between development and security teams to effectively find and fix bugs earlier in the development lifecycle.
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