The Trust and Safety team is a sub department of the Security Team at GitLab that forms part of the Security Operations subdepartment in Security at GitLab Inc and are tasked with the mitigation of Abuse on gitlab.com.
Our mission is to help build and maintain user trust, while keeping the GitLab platform safe and harm-free to help enable everyone to contribute.
We aim to acheive this by building a culture of care, protection, and a respect for privacy. We aim to stop the "bad" while also enabling the "good".
Our vision for GitLab Trust and Safety is to build a team and tooling capable of achieving both accuracy and scale in our work.
We want to make our corner of the internet a little safer, but also be the best internet citizens we can be by helping to detect and report abuse externally.
|Joanna Rubi||Security Engineer, Trust & Safety|
|Roger Ostrander||Security Engineer, Trust & Safety|
|Shawn Sichak||Security Engineer, Trust & Safety|
|Westley van den Berg||Security Analyst, Trust & Safety|
|Aaron Lindby||Security Analyst, Trust & Safety|
|Charl de Wit||Security Manager, Trust & Safety|
For Open Source Program Partners, Premium and Ultimate customers that would like to discuss, and potentially improve, your current abuse prevention and mitigation strategies, you can reach us at
firstname.lastname@example.org. Include any relevant information as to the abuse issue you are currently experiencing to help us provide the most relevant information.
Abuse prevention/mitigation feature requests or suggestions should be created in the Feature Proposal issue from the provided templates in the Project, add the
~Abuse Prevention label.
Feature proposals can be submitted for the following:
You can tag
@gitlab-org/modelops/anti-abuse to review the gitlab issue.
#abusechannel using the team Slack handle:
@gitlab-com/gl-security/security-operations/trust-and-safety) in the issue and notify us in the
report Abusebutton to report abuse.
If you are running your own GitLab instance and looking for some tips and tricks to manage abuse on your instance, have a look at our DIY page for more information.