To provide content and tools to support the best possible assessment at the earliest possible moment.
For more details about the vision for this area of the product, see the Secure stage page.
We will never knowingly compromise the security posture of your application.
We will give back to the Open Source community We will provide Responsible Disclosure We will share our knowledge and findings at public speaking events
The Secure team works on GitLab's Secure stage.
The following people are permanent members of the Secure Section:
| Person | Role |
|---|---|
| Todd Stadelhofer | Director of Engineering, Secure |
| Person | Role |
|---|---|
| Olivier Gonzalez | Engineering Manager, Secure:Composition Analysis |
| Fabien Catteau | Staff Backend Engineer, Secure:Composition Analysis |
| Tetiana Chupryna | Backend Engineer, Secure:Composition Analysis |
| Can Eldem | Backend Engineer, Secure:Composition Analysis |
| Mo Khan | Senior Backend Engineer, Secure:Composition Analysis |
| Adam Cohen | Senior Backend Engineer, Secure:Composition Analysis |
| Igor Frenkel | Senior Backend Engineer, Secure:Composition Analysis |
| Person | Role |
|---|---|
| Thomas Woodham | Engineering Manager, Secure:Static Analysis |
| Lucas Charles | Senior Backend Engineer, Secure:Static Analysis, Defend |
| Ross Fuhrman | Backend Engineer, Secure:Static Analysis |
| Daniel Searles | Senior Backend Engineer, Secure:Static Analysis |
| Zach Rice | Backend Engineer, Secure:Static Analysis |
| Saikat Sarkar | Senior Backend Engineer, Secure:Static Analysis |
| Person | Role |
|---|---|
| Seth Berger | Engineering Manager, Secure:Dynamic Analysis |
| Avielle Wolfe | Backend Engineer, Secure |
| Cam Swords | Senior Backend Engineer, Secure:Dynamic Analysis |
| Philip C. | Senior Backend Engineer, Secure:Dynamic Analysis |
| Craig Smith | Backend Engineer, Secure:Dynamic Analysis |
| Person | Role |
|---|---|
| Neil McCorrison | Frontend Engineering Manager, Secure |
| Sam Beckham | Senior Frontend Engineer, Secure |
| Paul Gascou-Vaillancourt | Frontend Engineer, Secure |
| Fernando Arias | Senior Frontend Engineer, Secure |
| Mark Florian | Senior Frontend Engineer, Secure, Defend |
| Dave Pisek | Senior Frontend Engineer, Secure |
| Dheeraj Joshi | Senior Frontend Engineer, Secure |
The following members of other functional teams are our stable counterparts:
| Person | Role |
|---|---|
| Achilleas Pipinellis | Senior Technical Writer, Create, Package, Monitor, Secure, Defend |
| Annabel Dunstone Gray | Product Designer, Secure |
| Valerie Karnes | UX Manager, Secure & Defend |
| Philippe Lafoucrière | Distinguished Backend Engineer, Secure, Defend |
| Tanya Pazitny | Quality Engineering Manager, Secure & Enablement |
| David DeSanto | Director of Product, Secure and Defend |
| Sam Kerr | Principal Product Manager, Secure:Attack Surface |
| Nicole Schwartz | Product Manager, Secure:Composition Analysis |
| Taylor McCaslin | Senior Product Manager, Secure:Static Analysis |
| Derek Ferguson | Senior Product Manager, Secure:Dynamic Analysis |
| Kyle Mann | Senior Product Designer, Secure |
| Camellia X. YANG | Senior Product Designer, Secure |
| Tali Lavi | UX Researcher, Secure |
| Will Meek | Senior Software Engineer in Test, Secure:Composition Analysis (primary) & Secure:Exposure Analysis (secondary) |
The Secure Team (previously known as the Security Products Team) is responsible for the security checks features in the GitLab platform, and maps to the secure transversal stage. You can learn more about our approach on the Secure Vision page.
The features provided by the Secure Team are mostly present at the pipeline level, and mostly available as Docker images. This particularity shapes our processes and QA, which differs a bit from the other backend teams.
We still refer to "Security Products" as the tools developed by the Secure Team. Hence the home of our projects in GitLab: https://gitlab.com/gitlab-org/security-products/
SAST (Static Application Security Testing) refers to static code analysis. GitLab leverages the power of various opensource tools to provide a wide range of checks for many languages and support. These tools are wrapped inside docker images which ensure we get a standard output from there. An orchestrator, developed by GitLab, is in charge of running these images, and gathering all the data needed to generate the final report.
DAST (Dynamic Application Security Testing) is used to hit a live application. Because some vulnerabilities can only be detected once all the code is actually running, this method complements the static code analysis. DAST is relying on OWASP Zed Attack Proxy Project, modified by GitLab to enable authentication.
Dependency Scanning is used to detect vulnerabilities introduced by external dependencies in the application. Because a large portion of the code shipped to production is actually coming from third-party libraries, it's important to monitor them as well. Dependency Scanning is relying mostly on the Gemnasium engine.
Container Scanning is used when the application is shipped as a Docker image. It's very common to build the final image on top of an existing one, which must be checked like every other portion of the application. For that, Container Scanning is relying on the clair scanner.
License Compliance helps with the licenses introduced by third-party libraries in the application. Licence management relies on the LicenseFinder gem.
If you are submitting an issue about a Secure Stage feature, use ~devops::secure and one of the following group labels to get the issue in front of the most appropriate team members.
| Label | Use |
|---|---|
~devops::secure |
All issues related to the Secure Stage |
~group::static analysis |
SAST, Secret Detection |
~group::dynamic analysis |
DAST, IAST, Fuzzing and Security Dashboard related |
~group::composition analysis |
Container or Dependency Scanning, Vulnerability Database, License Management |
Additional labels should be added according to the Workflow Labels Documentation.
Our release process is specified in this project. The vulnerability database is updated on a regular basis.
Because we have a wide range of domains to cover, it requires a lot of different expertises and skills:
| Technology skills | Areas of interest |
|---|---|
| Ruby on Rails | Backend development |
| Go | SAST, Dependency Scanning, Container Scanning |
| Python | DAST |
| SQL (PostgreSQL) | Dependency Scanning / all |
| Docker | Container Scanning / all |
Our team also must have a good sense of security, with at least basic skills in application security.
We provide tools for many different languages (ex: sast, dependency scanning, license compliance). It means our team is able to understand the basics of each of these languages, including their package managers. We maintain tests projects to ensure our features are working release after release for each of them.
Our release project also defines our QA process.
500 errors on gitlab.com are reported to Sentry. Below are some quick links to pull up Sentry errors related to Secure.
Our team occasionally schedules synchronous brainstorming sessions as a method of deep-diving on a specific topic. This approach can be useful in breaking down complexity and deriving actionable steps for problems that lack definition.
We tend to schedule these on a weekly cadence with a rotating timeslot to accommodate team members in different timezones. If a topic is not agreed upon prior to a given week, the slot is canceled to avoid unnecessary meetings. These slots can be viewed on the Secure Stage Team Calendar.
These are purposefully freeform to allow for creative problem solving. When possible, time should be reserved for a list of actions to be taken from the open discussion.
Brainstorming Sessions Doc (Internal): https://docs.google.com/document/d/179JL5RzbgSIz2XZewbYn79cuX7_vUtte_TcoLwUUC5o/edit#
Examples of previous brainstorming topics:
As the product evolves, it is important to maintain accurate and up to date documentation for our users. If it is not documented, customers may not know a feature exists.
To update the documentation, the following process should be followed:
~Documentation label, outline in the description of the issue what documentation is needed, and assign a Backend Engineer and Technical Writer(TW) to the issue (find the appropriate TW by searching the product categories).~Px label.Since we are a remote company, having daily standup meetings would not make any sense, since we're not all in the same timezone. That's why we have async daily standups, where everyone can give some insights into what they did yesterday, what they plan to do today, etc. For that, we rely on the geekbot slack plugin to automate the process.
description in backquote + [link to issue](#)" format when mentioning issues in your standup report.What did you do since yesterday? to denote the current state:
for successfully accomplished tasks (:ci_passing: emoji)
for tasks that were due on some period of time but were not accomplished (:ci_failing: emoji)
for tasks currently in progress (:ci_running: emoji)
for paused or postponed tasks (:ci_pending: emoji):ci_... icon you find applicableExample:
What did you do since yesterday?
Accomplished the Spotbugs java analyzer compareKey is not unique https://gitlab.com/gitlab-org/gitlab-ee/issues/10860 Still working on Allow guests to create an issue from a vulnerability https://gitlab.com/gitlab-org/gitlab-ee/issues/7813 Catch-up on all emails and threads after the vacationSlack Channels:
As our teams focus on different areas, we have Geekbot configured to broadcast to separate channels in addition to our common one at #s_secure-standup.
Our important meetings are recorded and published on YouTube, in the GitLab Secure Playlist. They give a good overview of the decision process, which is often a discussion with all the stakeholders. As we are a remote company, these video meetings help to synchronize and take decisions faster than commenting on issues. We prefer asynchronous work, but for large features and when the timing is tight, we can detail a lot of specifications. This will make the asynchronous work easier, since we have evaluated all edge cases.
New hires should go through these steps and read the corresponding documentation when onboarding in the Secure Team. Every new hire will have an assigned onboarding issue that will guide them through the whole process.
Secure uses a workflow based on the Product Development Flow with some additions under experiment.
Specific deadlines of this workflow are defined in the Product Development Timeline.
To maximize our velocity and meet our deliverables, we also follow a grooming process for all issues.
The Product Development Flow implies the existence of queues identified with workflow:: labels and depending on your role in the group, you may be involved in different queues.
| Queue | PM | UX | EM | Engineer |
|---|---|---|---|---|
| validation backlog | X | |||
| problem validation | X | X | ||
| design | X | X | X | X |
| solution validation | X | X | ||
| planning breakdown | X | X | X | X |
| scheduling | X | X | ||
| ready for development | X | X | X | |
| In dev | X | |||
| In review | X | |||
| verification | X |
The Product Development Flow guideline explains each step in details but here are some clarifications/additions:
workflow::design: when requested by PM and UX, the engineering team will be involved in the design step. As this can represent a significant amount of work, it is important to apply the ~backend and/or ~frontend labels to the issue as early as possible. EM will then assign Engineers and roughly weight the issue (or timebox it) so that this effort is taken into account when doing capacity check. Engineers assigned to workflow::design issues collaborate with PM, UX and EM to provide a practical solution to the problem.workflow::solution validation: the engineering team is NOT involved in solution validation since we assume the design step already delivered a viable solution from engineering perspective.workflow::planning breakdown: PM, UX, and EM break down the solution into smaller implementation issues. These issues represent deliverable chunks of the solution, from a user perspective. This often means that an epic is created and an MVC is defined with follow-up issues in further iterations to deliver the complete solution. EM can delegate this to engineers when necessary. When implementation issues are created, they can be groomed by the engineers.workflow::scheduling: PM priotize issues in this queue to be picked up in upcoming milestones by EM. Issues remaining in this queue after EM has reached their team's capacity for a given milestone must be moved to the next one(s).workflow::ready for development: EM applies this label to issues that the engineering team commit to work on for a given milestone based on capacity and other constraints.workflow::In dev: Engineers apply this label when starting to work on an issue. If the issue involves multiple Merge Requests, it stays in this queue untill they are all created and in review.workflow::In review: Merge Requests are being reviewed by reviewers and maintainers. If the issue involves multiple Merge Requests, it stays in this queue untill they are all merged.workflow::verification: Changes have been merged and engineers are waiting for them to be deployed on the different environments (staging, canary, and production). Once deployed, engineers enable the feature flag (if any) and validate it's working as expected.To work with these queues we leverage issue boards and relevant filters. We value asynchronous communication but it is also highly recommended to have a weekly sync meeting between PM, UX, and EM to review these queues: design, solution validation. planning breakdown, and scheduling. This ensures we keep moving issues forward to constantly have items to work on in each step of the process.
milestone filter with the current milestone +1 (the current milestone is already released).