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 ManagementMulti-factor authentication is required for remote sessions access to environments that host production systems.
Where and only if applicable, appropriate, and technically feasible, and with the understanding GitLab is a cloud-native, multi-factor authentication will be enabled on user accounts accessing production systems.
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.
Control owner:
Process owner:
Identity access management systems should enforce SSH or MFA for connections to production systems and networks.
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 Multifactor Authentication control issue.