Incident response procedures are in place that outline the response procedures to security events and includes lessons learned to evaluate the effectiveness of the procedures. The procedures are reviewed on a quarterly basis, or when major changes to the organization occur, to ensure they are effectively meeting the business objectives.
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.
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.
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:
#incident-managementSlack channel is used for synchronous incident communication via chat
Production-watchapp monitors the aforementioned
productionproject and notifies channel participants of the issue
Situation Roompermanent Zoom channel is used for synchronous communication via audio/video conference