0:0012:02

How an all remote software company approaches GRC

Julia Lake 12:02 2021

GitLab's security team publishes its policies instead of hiding them

Security through obscurity was popular for a very long time, yet GitLab's leadership asked its security team to become one of the most transparent in the world, publishing policies and procedures where customers can read them. Julia Lake, Director of Security Assurance at GitLab, explains how an all-remote company of over 1,300 people runs governance, risk and compliance without offices or slide decks. What does it take to make that openness work day to day?

Learn three practices for documentation, meetings and values you can apply in any team

Watch on YouTube

In short

Julia Lake, Director of Security Assurance at GitLab, explains how an all-remote company runs governance, risk and compliance (GRC) using its CREDIT values, handbook-first documentation and agenda-driven meetings. She describes how GitLab's GRC function matured toward its first SOC 2 Type 2 report and why it publishes its security policies openly. She argues that teams don't have to be fully remote to use these practices.

“Historically, transparency and security did not go hand in hand. Security through obscurity was a very popular approach for a very long time.”
“There should never be approvals happening in Slack. There should never be formal feedback or decisions happening in Slack.”

What you will learn

  • Apply a handbook-first approach that documents the process, the work instructions and the feedback mechanism before anything is released.
  • Separate informal communication tools such as Slack and Zoom from the system of record where approvals and decisions live.
  • Run meetings with an agenda, pre-read documentation, notes and recordings so attendance can be optional.
  • Design a GRC roadmap of at least two years that ties to organizational objectives, values, metrics and daily activities.
  • Make a security governance function more transparent by publishing policies and procedures for customers and users.

Key takeaways from the speaker

  • learn tips to becoming a more transparent security governance, risk and compliance organization

Details

Level
Intermediate
Format
Talk
Technical depth
Introductory technical
For
Mid-career, Senior individual contributor, People manager
Length
12:02
Published
June 2021

Questions this talk answers

How does an all-remote company keep decisions and approvals traceable?

GitLab centralizes work in GitLab itself and treats Slack and Zoom as communication tools with short retention periods. Approvals, formal feedback and decisions never happen in Slack.

How can meetings work without slide presentations?

Every GitLab meeting has an agenda of questions and objectives with linked documentation that attendees review beforehand. The meeting is then used to answer questions and make decisions quickly.

How did GitLab's GRC function mature?

A security compliance team started in 2018 with a common control framework based on Adobe's open source framework. In 2020 the team merged compliance and field security, added governance and risk management, onboarded a GRC application and obtained its first SOC 2 Type 2 report.

What is the biggest lesson from rapid GRC growth?

Design a roadmap of at least two years that aligns with organizational objectives, supports cultural values and has clear metrics. Linking it to daily activities makes unplanned changes easier to follow and accept.

Can a security organization be transparent?

GitLab's leadership tasked its security team with being one of the most transparent in the world. It publishes all policies and procedures on its handbook page so customers and users see what internal team members see.

About this talk

Learn how GitLab, a 100% remote organization since founded in 2014, implements our unique set of company values and remote best practices into daily security governance, risk and compliance activities.

Topics

Related talks

Browse the library

Canonical Meet & Greet

Miona Aleksic +3 Product Manager

Open source needs contributors who never write a line of code

All levels Software engineering and cloud 2023