Document Separation of Duties for Release Governance (#199753) · Issues · GitLab.org / GitLab

Document Separation of Duties for Release Governance

Problem to solve

What product or feature(s) affected? Release: Release Governance
What docs or doc section affected? Compliance

Further details

The goal is to help support customers seeking to accomplish adequate separation of duties leveraging GitLab features. This will be for:

Compliance personell
Release managers
DevOps roles

Proposal

This is an example pattern of using an externalized GitLab CI YAML for separation of duties. One could write that YAML one time and make it applicable for multiple projects.

Another couple of options, supported and non-supported, references to issues that would make this support possible, example and instructions at https://gitlab.com/gitlab-com/account-management/emea/eni/poc/tree/master/CI-CD#rp312-multi-repository-pipelines

Who can address the issue

Anyone

Other links/references

<!--

* Use this issue template for suggesting new docs or updates to existing docs.
  Note: Doc work as part of feature development is covered in the Feature Request template.

* For issues related to features of the docs.gitlab.com site, see
     https://gitlab.com/gitlab-org/gitlab-docs/issues/

* For information about documentation content and process, see
     https://docs.gitlab.com/ee/development/documentation/ -->

### Problem to solve

* What product or feature(s) affected? 
Release: Release Governance

* What docs or doc section affected? 
[Compliance](https://docs.gitlab.com/ee/administration/compliance.html)

### Further details

The goal is to help support customers seeking to accomplish adequate separation of duties leveraging GitLab features. This will be for:

* Compliance personell 
* Release managers 
* DevOps roles

### Proposal

This is an example pattern of using an externalized GitLab CI YAML for separation of duties. One could write that YAML one time and make it applicable for multiple projects.

* https://gitlab.com/gitlab-silver/tpoffenbarger/separation-of-duties
* https://gitlab.com/gitlab-silver/tpoffenbarger/separation-of-duties-deploy

Another couple of options, supported and non-supported, references to issues that would make this support possible, example and instructions at  https://gitlab.com/gitlab-com/account-management/emea/eni/poc/tree/master/CI-CD#rp312-multi-repository-pipelines

### Who can address the issue

* Anyone

### Other links/references

* https://about.gitlab.com/handbook/engineering/security/guidance/CM.2.01_segregation_of_duties.html 
* https://gitlab.com/gitlab-com/gl-security/compliance/compliance/issues/783

Discussion
Designs