CM.2.01_segregation_of_duties.html.md 1.68 KB
Newer Older
1
---
2
layout: handbook-page-toc
3 4 5 6
title: "CM.2.01 - Segregation of Duties Control Guidance"
---

## On this page
7
{:.no_toc .hidden-md .hidden-lg}
8 9

- TOC
10
{:toc .hidden-md .hidden-lg}
11 12 13 14 15 16 17 18 19

# CM.2.01 - Segregation of Duties

## Control Statement

Changes to the production environment are implemented by authorized personnel.

## Context

20
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.
21 22 23 24 25 26 27 28 29 30

## Scope

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.

## Ownership

* Control Owners: 
  * Infrastructure
  * Finance
Nik Sarosy's avatar
Nik Sarosy committed
31
  
32 33 34 35 36 37 38
* Process owner(s):
    * Infrastructure
    * Finance


## Additional control information and project tracking

Jeff Burrows's avatar
Jeff Burrows committed
39
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](https://gitlab.com/gitlab-com/gl-security/security-assurance/sec-compliance/compliance/issues/783).
40 41 42

Examples of evidence an auditor might request to satisfy this control:

Nik Sarosy's avatar
Nik Sarosy committed
43
* Evidence that PostgreSQL database access above data reader is limited to [Database Reliability Engineers](/job-families/engineering/database-reliability-engineer/)