In short
Julia Lake, Director of Security Assurance at GitLab, argues that the habits that make remote work succeed also make governance, risk and compliance (GRC) stronger: one central system of record, documentation written before a change ships, and meetings built around decisions instead of slides. At GitLab these habits support an unusual goal for a security team, which is to be openly transparent about how it works. She also stresses that a team does not need to be fully remote to use them.
Key takeaways
- Learn tips for becoming a more transparent security governance, risk and compliance organization.
- Structure company values to support remote and multi-location work.
- Document everything and adopt a handbook-first approach to company communication.
- Make meetings optional by requiring agendas, notes and recordings.
Values that everyone is expected to enforce
Lake begins with context. She started her career in retail banking, "getting audited before becoming the auditor," and has spent about ten years in GRC across information security, quality and privacy. GitLab, as she describes it, has no physical locations at all, more than 1,300 team members in 67 countries, and a SaaS product hosted in Google Cloud Platform.
The culture rests on six values known as CREDIT: collaboration, results, efficiency, diversity, iteration and transparency. They are hierarchical, with results at the top. On top of these sit the foundations of remote work, and Lake makes clear they apply to everyone, from the CEO to interns, who are also expected to promote them. She describes what that looks like in practice: "It's not uncommon at GitLab to hear an executive get called out by an engineer for operating in a Google doc instead of a GitLab issue, or for deploying a change without documenting first in our handbook." (3:40) Her favourite foundation, assuming positive intent, is what makes that kind of challenge workable.
One system of record, many conversations
The biggest lesson Lake hears from people joining GitLab is that centralization is what makes asynchronous work succeed. Everyone at GitLab uses GitLab, and dogfooding is part of the culture. She passes on a reminder from the company's CTO: "Our CTO constantly reminds us it's called dogfooding because it's not supposed to be pretty, at least not at first." (4:34)
Informal communication is welcome, but it never replaces the central record. Slack and Zoom are treated as communication tools with short retention periods, which matters a great deal for a compliance function that needs evidence. As Lake puts it: "There should never be approvals happening in Slack. There should never be formal feedback or decisions happening in Slack." (5:21)
Meetings built for decisions, not slides
With so much time on Zoom, meeting fatigue is a real risk. GitLab's answer surprises most people: "Perhaps the most unique thing about GitLab is that we don't do presentations." (5:45) Every meeting has an agenda of questions and objectives with linked documentation, and attendees review it beforehand. The call itself is then used to answer questions and make decisions, which avoids long meetings and follow-up calls. Lake also mentions no-meeting Fridays, walk and learn sessions run by the learning and development team, and company-wide friends and family days off.
Growing a GRC function on a long roadmap
Lake then traces how GitLab's GRC function developed. A security compliance team was formed in 2018 and deployed a common control framework based on Adobe's open source framework, working mostly in an advisory role. In 2020 the team merged security compliance with field security, its customer-facing team, built formal governance and risk management functions, onboarded a third-party GRC application, upgraded its control framework and obtained its first SOC 2 Type 2 report. The team still advises, but now has policy, risk and compliance oversight data to support that advice.
Her main lesson from this period of rapid growth is to plan further ahead. A roadmap of at least two years should align to organizational objectives, support cultural values and carry clear metrics. "It should also clearly relate back to daily activities so teams know what massive programs rely on their daily work and helps build the tie-in relationship." (7:48) Done well, she says, this reduces large changes and makes unplanned ones easier for everyone to understand and accept. The current focus is maturing security controls through continuous auditing and continuous control monitoring, with the aim of expanding the certification portfolio.
Transparency as a security strategy
The most distinctive part of the talk is GitLab's stance on openness. "Historically, transparency and security did not go hand in hand. Security through obscurity was a very popular approach for a very long time." (8:41) GitLab's leadership has instead asked the security team to become one of the most transparent security organizations in the world, a goal Lake says the team is still working toward. One concrete step is publishing all policies and procedures on the company handbook page, so customers and users have the same visibility as internal team members.
Practices any team can adopt
Lake closes with three takeaways. First, shape team values around remote work styles whenever people work in more than one place: "You don't have to be a 100 percent remote organization to take advantage of the benefits that come along with remote work." (9:35) Second, go handbook-first: before a new process is deployed, document the process, the work instructions for the people who will carry it out, and the feedback mechanism for after release. Third, make meetings optional by requiring agendas, taking careful notes and recording sessions. "Employees will feel more comfortable skipping a meeting if they are confident there will be notes they can absorb after the fact." (10:42) That gives people time back for their core work.
Watch the talk
"How an all remote software company approaches GRC" by Julia Lake, about 12 minutes: https://www.womentech.net/video/julia-lake-how-all-remote-software-company-approaches-grc
About the speaker
Julia Lake is Director, Security Assurance at GitLab and an experienced governance, risk and compliance professional with a history of working in the cloud computing industry. She is skilled in security and regulatory certification, compliance strategy, risk management and business process improvement.
Questions this talk answers
- How does an all-remote company keep decisions and approvals traceable?
- How can meetings work without slide presentations?
- How did GitLab's GRC function mature?
- What is the biggest lesson from rapid GRC growth?
- Can a security organization be transparent?
Drafted with AI from the talk transcript. Editor review pending.