Gitlab hero border pattern left svg Gitlab hero border pattern right svg

IR.1.01 - Incident Response Plan Control Guidance

On this page

IR.1.01 - Incident Response Plan

Control Statement

GitLab defines the types of incidents that need to be managed, tracked and reported, including:

Context

The purpose of this control is to ensure GitLab creates, implements, and maintains an effective plan to identify, resolve, and prevent incidents within its application, systems, and services. By having an organized and continually evolving incident response plan, GitLab can maintain the availability, reliability, performance, and confidentiality offered to GitLab customers, GitLab team-members, and partners.

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

Additional control information and project tracking

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 Incident Response Plan control issue.

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

Policy Reference

Framework Mapping