Trust & Safety Team
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.
Mission
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 achieve this by building a culture of care, protection, and a respect for privacy. We aim to stop the “bad” while also enabling the “good”.
Vision
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.
Our Responsibilities
- Detect user generated Abuse on gitLab.com
- Review reported accounts for abusive activity on GitLab.com.
- Remove user generated content on GitLab.com that violate of our Terms of Service.
- Mitigating malicious user generated activity on GitLab.com.
- Review Account Reinstatement requests.
- Review DMCA (Digital Millennium Copyright Act) and Trademark Infringement notices.
- Reporting malicious activity impacting GitLab.com to the relevant service providers.
The Team
Person | Role |
---|---|
Joanna Rubi | Security Engineer, Trust & Safety |
Shawn Sichak | Security Engineer, Trust & Safety |
Westley van den Berg | Security Analyst, Trust & Safety |
Aaron Lindby | Security Analyst, Trust & Safety |
Ruby Nealon | Security Engineer, Trust & Safety |
Charl de Wit | Security Manager, Trust & Safety |
Reporting Abuse
- To report abusive activity, see our Abuse on Gitlab.com page.
- Copyright and Trademark infringements, see our Intellectual Property on Gitlab.com page.
- Frequently Asked Questions, see our FAQ page.
Working with GitLab Trust and Safety Team
-
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
abuse@gitlab.com
. 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:
- Gitlab.com,
- GitLab CE and;
- GitLab EE;
You can tag @gitlab-com/gl-security/security-operations/trust-and-safety
and @gitlab-org/modelops/anti-abuse
to review the gitlab issue.
GitLab team members can reach Trust and Safety via:
- Slack:
#abuse
channel using the team Slack handle:@trust-and-safety
- Non-urgent queries should be created in our Operations Tracker or tag us (
@gitlab-com/gl-security/security-operations/trust-and-safety
) in the issue and notify us in the#abuse
slack channel. - For
URGENT
issues that require the immediate attention of the Trust and Safety team you can page the Trust and Safety On-call by completing the Create New Incident form in PagerDuty.URGENT
Trust and Safety issues are defined as instances of user generated abuse :- that is or has a high probability of resulting in service degradation or outages of
GitLab.com
and/or its features. - on
GitLab.com
that has the potential of causing significant legal, financial or reputational damage or liability to the company.
- that is or has a high probability of resulting in service degradation or outages of
Non GitLab team members.
- Non GitLab members should use the
report Abuse
button to report abuse. - More detailed abuse reports can be sent to abuse@gitlab.com
Abuse DIY
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.
Intellectual property on gitlab.com
Trust & Safety Team Frequently Asked Questions
Trust & Safety, Do It Yourself
69f17a79
)