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

IR.1.01 - Incident Response Plan Control Guidance

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. Since this control is related to incident response, there is no easy way to test this unless citing examples of an actual incident. Hence this can be tested by proving that GitLab has sufficient documentation in place for an efficient Incident Response plan, which can include documentation pertaining to the handbook pages, Merge requests, and issues opened in reference to and in adherence to the IR plan.

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

  1. Procedures for the identification and management of incidents:
  2. Procedures for the resolution of confirmed incidents.
  3. Key incident response systems:
  4. Incident coordination and communication strategy:
  5. Contact method for internal parties to report incidents
  6. Support team contact information
  7. Notification to relevant management in the event of a security breach
  8. Provisions to contact support team
  9. Production Infrastructure related IR Plan:
    • Production infrastructure incidents are documented in the production project
    • The #incident-management Slack channel is used for synchronous incident communication via chat
    • In the channel, the Production-watch app monitors the aforementioned production project and notifies channel participants of the issue
      • The Situation Room permanent Zoom channel is used for synchronous communication via audio/video conference
    • A link to the channel is included in the description for the #incident-management Slack channel
  10. Alert mechanisms:

Framework Mapping