GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsGitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsThis realm is for the engineering security team to deploy shared and team-specific infrastructure resources.
To request access to a group, please see group access request tutorial.
For email authenticity security reasons, only GitLab issues or Slack messages to owners or counterparts are allowed for infrastructure requests.
Name | GitLab.com Handle | Group Role | Job Title |
---|---|---|---|
Jan Urbanc | jurbanc |
Owner | Director, Security Operations |
Laurence Bierner | laurence.bierner |
Counterpart | Director, Application Security |
The global labels/tags and realm labels/tags should be applied to each resource.
Each gl_dept_group has a shared GCP project and/or AWS account for group members.
If a group has not been implemented yet, please contact the realm owner for assistance. After a group is implemented, a separate handbook page is created with usage documentation.
Group Name (AWS Account/GCP Project Name) | Usage Documentation (Empty cells are not implemented yet) |
---|---|
eng-security-shared-infra |
|
eng-security-shared-services |
|
eng-security-ops-red |
|
eng-security-ops-incident-response |
|
eng-security-ops-trust-safety |
|
eng-security-risk-compliance |
|
eng-security-eng-app-sec |
|
eng-security-eng-automation |
|
eng-security-eng-research |
This is a placeholder for the realm owner to provide instructions on best practices and usage guidelines for this infrastructure.