Skip to content

Clarify use of identifiers for vulnerability tracking

Thiago Figueiró requested to merge docs/secure-integrations-tracking into master

What does this MR do and why?

Update two documentation sections in the same page:

Changes

  1. DRY-up information about finding deduplication by linking to the new section at https://docs.gitlab.com/ee/user/application_security/vulnerability_report/pipeline.html#deduplication-process
  2. Remove incorrect information "reported for the same commit" (findings are associated with a pipeline, not commits)
  3. Expand information about tracking by adding the missing "project id" and mentioning the uuid SHA-1 hash (UUIDv5 digest).

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports