GitLab Recon

In CE to make our security product more popular.

The ideal flow is: enter a domain name 'example.com' and get a list of vulnerabilities with the most likely ones on top (sorted by signal to noise ratio).

To do this there are two components, Recon (this issue) and DAST https://gitlab.com/gitlab-org/gitlab-ee/issues/3956

The first iteration user flow will be:

  1. Create a new project with the 'Recon' GitLab CI template.
  2. Enter the TARGET_DOMAIN environmental variable.
  3. Receive a list of subdomains in a yaml compatible format.

Rest of the workflow, not part of Recon:

  1. Copy (part of) that list to the clipboard
  2. Create a new project with the 'DAST' GitLab CI template.
  3. Past the list into the .gitlab-ci.yml file to run the DAST in parallel against all subdomains.
  4. Get a list of vulnerabilities with the most likely ones on top

The GitLab Recon CI template has two stages:

  1. Running a number of subdomain discovery tools in parallel.
  2. Running a task that aggregates their output and deduplicates it.

The subdomain discovery tools would be based on https://news.ycombinator.com/item?id=15676951 Example commands:

/cc @kathyw @dzaporozhets @bikebilly @markpundsack

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.

Edited by 🤖 GitLab Bot 🤖