Docs: Illustrate the vulnerability management state flow
-
Start this issue's title with
Docs:orDocs feedback:.
Problem to solve
Illustrate the vulnerability management state flow.
A vulnerability's status can be influenced by many factors. A diagram that illustrates the state changes, and what it is that makes those changes, would supplement the docs.
- The simplest factor is the outcome of a pipeline - security reports.
- Other factors include:
- Continuous vulnerability scanning (only dependencies)
- Vulnerability management policy (can automatically resolve vulnerabilities)
Further details
There's an existing diagram at https://docs.gitlab.com/user/application_security/#vulnerability-management-cycle but it's lacking in detail.
Proposal
Illustrate the vulnerability management state flow.
Who can address the issue
Anyone with sufficient knowledge of the vulnerability management workflow.
Other links/references
Edited by 🤖 GitLab Bot 🤖