Strengthening Security and Compliance in Our Data Platform
summary
gitlab hardens its data platform by hiring a data security engineer, automating CI security scans (SAST, DAST, secret and dependency checks) and running quarterly access reviews with deprovisioning after 60–90 days. Platform specifics: ~350,000 CV statements/day, 4,000 dbt models, 93 Airflow DAGs, ~120 TB production data, 64 sources and 220 monthly Snowflake users. They add a Snowflake data‑classification scanner, Permafrost permission/version control for Snowflake/Tableau, enforce MFA, key rotation, encryption and data minimization to reduce breach impact.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:28Why data security matters
- 1:29GitLab mission and goals
- 3:56Key metrics of platform
- 4:40Introducing data security engineer
- 6:24ARM yourself: Avert, Review, Mitigate
- 6:44Averting data breaches
- 8:51Reviewing and monitoring security
- 10:39Mitigating breach risks
- 12:48Lessons learned and next steps
related talks
40mDo the Magic with All-Remote Data Teams...
25mHow we create and leverage Data Services in GitLab.com
28mUsing Dataops To Build And Manage Data Products On Snowflake
42mThreat Detection across all environments with SnowflakeData Security Lake
31mHow to Implement DataOps using
31mAI-driven DataOps: Building data products with a taste of the future
35mBuilding a data analytics platform on strong opinions held loosely
27mDataOps & Full Snowflake Automation In 1 Click