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 insider threat activiy within a GitLab instance. This includes abuse, spam, and other activity for users within a GitLab instance.
Protect GitLab instances from abuse and spam at scale. With the increased growth of the GitLab SaaS platform and customer base, we have seen increased abuse and spam activity across public projects. These events create not only bad customer experiences with problems like issue spam but also pose potential risk to perofrmance and stability of GitLab shared runners and .com experience.
Initially this category is focused on protecting GitLab instances from abuse and spam by registered users.
Read more about coming changes to GitLab.com to help mitigate Cryptomining abuse.
The Anti-Abuse group is made up of two categories presently:
A number of 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.
Last Reviewed: 2021-10-26
Last Updated: 2021-10-26