Policies

These are the GitLab policies that IT Enterprise Applications adheres to.
  1. https://handbook.gitlab.com/handbook/security/security-and-technology-policies/access-management-policy/
  2. https://handbook.gitlab.com/handbook/security/password-standard/
  3. https://handbook.gitlab.com/handbook/security/security-and-technology-policies/change-management-policy/
  4. https://handbook.gitlab.com/handbook/security/security-and-technology-policies/audit-logging-policy/
  5. https://handbook.gitlab.com/handbook/business-technology/policies/gitlab-business-continuity-plan/
  6. https://handbook.gitlab.com/handbook/business-technology/policies/gitlab-incident-response-plan/
  7. https://handbook.gitlab.com/handbook/business-technology/policies/gitlab-security-incident-response-plan/

Business Continuity Plan

Purpose

Business Continuity Plan is the process involved in creating a system of prevention and recovery from potential threats to GitLab. The plan ensures that personnel and assets are protected and are able to function quickly in the event of a disaster.

Scope

GitLab, by its remote-only nature, is not easily affected by typical causes of business disruption, such as local failures of equipment, power supplies, telecommunications, social unrest, terrorist attacks, fire, or natural disasters. System data from the Business Impact Analysis may be leveraged as part of business continuity planning and testing. Additionally, the BCP works in conjunction with the Disaster Recovery Plan (DRP).