The security tightrope: balancing security with ease-of-use
Nov 7, 2019Heather Simpson

Summary
This post details the security engineer's role in balancing user experience with security friction. It highlights initiatives focused on developing tooling and automation for deeper visibility and proactive security response, leveraging aggregated data for automated response pipelines. Key advice includes using unique passwords with a password manager and enabling 2FA. Emerging trends include integrating security into software development workflows (e.g., SOAR, compliance-as-code) and the need for security teams to scale through automation and actionable data. GitLab's transparency in handling security issues is noted as a strength.
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