The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Create protections against abusive activity within a GitLab instance. This includes abuse, spam, and other activity for users within a GitLab instance.
Protect GitLab instances from user behavior that disrupts productivity or an organization's ability to build and deploy code.
This group will help eradicate fake accounts, proactively identify and remove bad actors, and help GitLab better understand our legitimate users. This group will directly protect the stability, performance, and scalability of GitLab for millions of users across the world ensuring they can effectively use GitLab for their daily development needs.
The Anti-Abuse group is currently made up of two product categories:
We make abuse manageable.
Our goal is not to completely eradicate abuse. Barriers to stopping abusive behavior have an exponentially diminishing rate of return. The more barriers that you impose to stop abuse the more you discourage legitimate usage. As a result, efforts to stop abuse become more costly than the abuse itself. Our goal is to surface abuse before it causes disruption and allow our automated systems, the Trust and Safety team, or the admin of the self-managed instance to take the correct action for that abuse – or correct any action that was taken in error
Several issues are intentionally confidential despite our value of transparency. This is because we don't want to make it obvious to abusers the exact details of our controls. We aren't relying on "security by obscurity"; however, we also don't want to make it easier for the abusers.
Anti-abuse is a group in the Govern stage. There are two categories in the group and details on the direction can be viewed on the following individual category pages:
| Priority | Name | DRI | Size | Target release |
|---|---|---|---|---|
| 1 | Confidential | TBD |
M |
16.11 |
| 2 | Bug: New accounts in GitLab.com created with same email as deleted accounts are blocked | TBD |
S |
16.11 |
| 3 | Confidential | TBD |
S |
16.11 |
| 4 | Iteration 1: Instance Resiliency v2 Vision | @eugielimpin |
L |
17.1 |
| 5 | Iteration 2: Instance Resiliency v2 Vision | @imand3r |
L |
17.3 |
| 6 | Cells 1.0 - Anti-abuse feature compatibility | TBD |
L |
TBD |
| 7 | Bug: Delayed user deletion does not consider elevated roles in subgroup for immediate deletion | TBD |
S |
TBD |
| 8 | Iteration 3: Instance Resiliency v2 Vision | TBD |
L |
TBD |
| 9 | Iteration 4: Instance Resiliency v2 Vision | TBD |
L |
TBD |
*This page may contain information related to upcoming products, features and functionality.
It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes.
Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.*
Slack: #g_govern_anti-abuse channel
Last Reviewed: 2024-03-05
Last Updated: 2024-03-05
