Labels

A label to let users know that this issue is a suitable beginner issue for devs learning python and the AIGW.

Pertains to all Sec Section groups https://about.gitlab.com/direction/security/

Issues of interest for Analyst Relations

Issues related to analytics, like feature usage, graphs and data we can display in GitLab UI

Good issues for onboarding to technical aspects of product intelligence domain

Ansible

Issues related to the GitLab API: https://docs.gitlab.com/ee/api/

Issues relating to api/webhook inconsistencies

Issues related to additional coverage in the GitLab API

Issues related to the Merge Request approvals feature: http://doc.gitlab.com/ee/workflow/merge_request_approvals.html

A label applied to Merge Requests that were later identified as having introduced a vulnerability during a security release. This label is used for tracking review coverage metrics and should be applied retroactively to the original Merge Request when a vulnerability is discovered. The purpose of this label is to help measure the Application Security team's effectiveness in preventing vulnerabilities through code review by tracking which vulnerability-introducing changes went through security review gitlab-com/content-sites/handbook!11439

A label applied to Merge Requests in which a vulnerability was identified and prevented going into production if it was fixed before being merged. This label is used for tracking review coverage metrics. The purpose of this label is to help measure the Application Security team's effectiveness in identified vulnerabilities through code review.

This label is applied by an AppSec team member when all findings from AppSec's SAST rules have been reviewed. See https://gitlab.com/gitlab-com/gl-security/appsec/sast-custom-rules