Security Risk Team

Mission Statement

To drive security and technology risk treatment at GitLab by empowering teams to make informed and intelligent decisions through proactive identification, monitoring, prioritization, and reporting of security and technology risks.

Value Proposition

We perform thorough, collaborative, and efficient risk assessments as well as drive risk reduction so that GitLab can achieve its goals while maintaining a high level of security.

Core Competencies

Security and Technology Operational Risk Management (STORM) Program

The Security Risk team manages an integrated Operational Risk Management program focused on the identification, assessment, continuous monitoring, and reporting of Security and Technology Risks across the organization. Risk Reduction is 1 of 5 of the Security Department’s operating principles (Security Vision and Mission). As such, the Security Risk Team takes a leading role in providing the information required by leadership to establish our Strategic Roadmap and support GitLab’s key initiatives (internal only). Visit the STORM Program & Procedures handbook page for additional details including templates and how we integrate with other risk programs at GitLab.

Security Third Party Risk Management (TPRM) Program

GitLab maintains an industry-leading Third Party Risk Management (TPRM) Program(/handbook/security/security-assurance/security-risk/third-party-risk-management) through AI-powered automation and continuous security monitoring to validate the security of GitLab data shared with external parties. The seamless integration of the TPRM program within the vendor Procurement flow enables cross-functional collaboration between Privacy, Legal, IT, and People Operations to facilitate transparent, data-driven decision making, Business and Stakeholder-focused Results, and adherence to GitLab’s Regulatory and Compliance Obligations. Vendor relationships maintained through this program are leveraged to create efficiencies across the organization.

Business Impact Analysis (BIA) and Critical System Tiering (CST)

The Business Impact Analysis (BIA) helps determine the systems critical to serving GitLab’s Customers. The output of the BIA is the designation of a Critical System Tier (CST) for a new system by the Security Risk Team.

Asset Inventory Maintenance

Establishing a complete and accurate inventory of assets is key to the success of GitLab’s Risk Program. The Security Risk Team coordinates with Business Technology to maintain oversight and accuracy of the Tech Stack.

Operating Model

Core Processes

Engagement Models

1. Report Security or Technology Risk
2. In GitLab, tag the team across GitLab using @gitlab-com/gl-security/security-assurance/security-risk-team

Communication Channels

1. Email: securityrisk@gitlab.com
2. Slack: #security_help channel - Mention @security-risk
3. GitLab: Tag the team across GitLab using @gitlab-com/gl-security/security-assurance/security-risk-team

Team Members

Strategic Initiatives

The Security Risk Team conducts periodic planning and prioritization to ensure that resources are dedicated to driving down risk. This includes facilitating risk treatment and, at times, taking ownership of control design and implementation where applicable. Please refer to the GitLab Operating Model for updates on cross-functional efforts involving Security Risk.

Review and Updates

This charter will be reviewed and updated quarterly to ensure alignment with:

1. GitLab Strategy
2. Security Division Mission and Vision
3. Security’s Multi-year Strategy (internal only)
4. Security Assurance Mission and Vision
5. Security Assurance Multi-year Strategy (internal only)

View page source - Edit this page - please contribute.