Zero Trust at GitLab: Where do we go from here?
Oct 15, 2019Mark Loveless

Summary
This post details GitLab's progress and challenges in implementing a Zero Trust Network (ZTN) approach. It covers the integration of SaaS applications with Okta for authentication and authorization, the rollout of Okta Advanced Server Access (ASA) for SSH access, the use of Camo proxy for encrypted communications, and the importance of robust server and container security with visibility through tools like Tenable and Uptycs. It also discusses the challenges of logging and budget allocation for ZTN initiatives, and provides advice on breaking down needs into simple components and focusing on user and device authentication.
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