1. You are here:
2. IR.1.01 - Incident Response Plan Control Guidance

On this page

• IR.1.01 - Incident Response Plan
  • Control Statement
  • Context
  • Scope
  • Ownership
  • Additional control information and project tracking
    • Policy Reference
  • Framework Mapping

IR.1.01 - Incident Response Plan

Control Statement

Incident Response Guidance is available in the Handbook that outlines GitLab's security incident response process. It also provides information to internal and external users on how to report breaches, security and availability failures, incidents, concerns, identified vulnerabilities and other security complaints to appropriate personnel.

Context

The purpose of this control is to ensure GitLab creates, implements, and maintains an effective plan to identify, resolve, and prevent security incidents within its application, systems, and services. By having an organized and continually evolving security incident response plan, GitLab can maintain the availability, reliability, performance, and confidentiality offered to GitLab customers, GitLab team-members, and partners. This control can be tested by first proving that GitLab has sufficient documentation in place for an efficient Incident Response plan. This can include documentation pertaining to the handbook pages, Merge requests, and issues opened in reference to and in adherence to the IR plan. It can then be confirmed that any security incident that was reported (if applicable) followed the IR plan documentation.

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

• Control Owner: Infrastructure
• Process owner(s):
  • Security Operations
  • Infrastructure

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:

• Provide copies of the Incident Response pages, which are linked to and described below
• Provide sample reports and other outputs of the various functions listed below, such as Infrastructure and/or Security incident issues

Policy Reference

1. Procedures for the identification and management of incidents:
   • Incident management documented in the GitLab Handbook
   • Incident Management for Self-Managed Customers
2. Procedures for the resolution of confirmed incidents.
   • Security issue triage process
   • Security severity labelling
   • Major Incident Response Workflow
   • Additional documentation on using the panic email and a procedure for the security team's response to those alerts
3. Key incident response systems:
   • Incident management documented in the GitLab Handbook
4. Incident coordination and communication strategy:
   • S1 and S2 Incidents. Information about our most critical incident severities.
   • Incident Steps. Defines the steps involved with handling an incident.
   • Communication. Describes communication procedures during an incident.
   • CMOC and IMOC checklist. A checklist of actions for the CMOC and IMOC response roles to perform.
   • Incident runbooks are available and maintained in the runbooks project
   • Database-specific runbooks
   • Additional runbooks
5. Contact method for internal parties to report incidents
   • Process for engaging security on-call
   • Security operations on-call guide
6. Support team contact information
   • Incident Management Support
   • On-Call Runbooks.
7. Notification to relevant management in the event of a security breach
   • Security Incident Comms Plan
8. Provisions to contact support team
   • Support Team function in the handbook
   • Support page contains information to contact the 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:
    • Security Incident and Alert Lifecycle in GitLab

Framework Mapping

• SOC2 CC
  • CC4.2
  • CC7.3
• PCI
  • 11.1.2
  • 11.5.1
  • 12.10
  • 12.10.1
  • 12.10.4
  • 12.10.5
  • 12.10.6