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.
Please refer to the communication section of the STORM Program & Procedures page for information on the various ways that team members can use to escalate potential risks to the Security Risk Team.
Security Third Party Risk Management (TPRM) Program
GitLab maintains an industry-leading Third Party Risk Management (TPRM) Program through the use of automation, continuous monitoring, and deep integration across business functions to validate the security of GitLab data shared with external parties. The integration of GitLab’s TPRM program within the vendor Procurement flow enables cross-functional collaboration between Privacy, Legal, IT, and People Operations to facilitate transparent, risk-based decision making, Business and Stakeholder-focused Results, and adherence to GitLab’s Regulatory and Compliance Obligations. The 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. As such, the Security Risk Team collaborates closely with IT and Business Owners to ensure new systems are added to the Tech Stack.
Operating Model
Core Processes
Function | DRI |
---|---|
Annual Risk Assessment | Kyle Smith |
Business Impact Analysis | Nirmal Devarajan |
New System Onboarding Checklist | Nirmal Devarajan |
Critical System Tiering | Kyle Smith |
Ongoing SecRisk-Related Observations Management | Nirmal Devarajan |
Ongoing Risk Treatment | Kyle Smith |
Ongoing TPRM Assessments | Ryan Lawson |
Periodic SOX CUEC Facilitation | Eric Geving |
Periodic TPRM Assessments | Eric Geving |
TPRM Data Quality and Emerging Requirements Management | Eric Geving |
STORM Metrics and Reporting | Kyle Smith |
TPRM Metrics and Reporting | Ryan Lawson |
TPRM Application Integrations | Ryan Lawson |
Engagement Models
- Request a TPRM Review
- Report Security or Technology Risk
- In GitLab, tag the team across GitLab using
@gitlab-com/gl-security/security-assurance/security-risk-team
Communication Channels
- Email:
securityrisk@gitlab.com
- Slack: #security_help channel - Mention
@security-risk
- 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 Critical and Cross-Functional Roadmap (CCFR) for significant cross-functional efforts.
Review and Updates
This charter will be reviewed and updated quarterly to ensure alignment with:
- GitLab Strategy
- Security Division Mission and Vision
- Security’s Multi-year Strategy (internal only)
- Security Assurance Mission and Vision
- Security Assurance Multi-year Strategy (internal only)
Next scheduled review: 2025-12-15
Security Third Party Risk Management
SOX CUEC Mapping Procedure
0d265ac0
)