GitLab
A single application for the entire DevOps lifecycle
GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Remote Work Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream ManagementGitLab
A single application for the entire DevOps lifecycle
GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Remote Work Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream ManagementChanges to the production environment are implemented by authorized personnel.
Proper segregation of duties allows GitLab to reduce risk to the integrity and availability of the production GitLab environment and third party systems by ensuring that only those with the proper authorization can make production-level changes. Conflicting duties and areas of responsibility are segregated to reduce opportunities for unauthorized or unintentional modification or misue of GitLab's assets.
This control applies to all systems within our production environment. The production environment includes all endpoints and cloud assets used in hosting GitLab.com and its subdomains. This may include third-party systems that support the business of GitLab.com.
Non-public information relating to this security control as well as links to the work associated with various phases of project work can be found in the Segregation of Duties control issue.
Examples of evidence an auditor might request to satisfy this control:
SOC2 CC