The standard change management process is documented in a change control workflow.
Having a structured workflow and guidance on change management helps reduce the risk of GitLab experiencing platform or application instability by increasing the predictability and reproducibility of the change management process.
This control applies to all systems within our GitLab.com production environment. The production environment includes all endpoints and cloud assets used in hosting GitLab.com and its subdomains. This doesn't include third-party systems that support the business of GitLab.com, which can be found in CM.3.01.
Change management encapulates multiple types of changes within our business environment.
The two primary production changes are infrastructure changes and source code changes to gitlab service itself.
Third-party systems, the data warehouse, and financial changes are related to the Business Technology Change Management Workflow.
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 Change Management Workflow control issue.
Examples of evidence an auditor might request to satisfy this control: