- Change vulnerability status
- Create a GitLab issue for a vulnerability
- Create a Jira issue for a vulnerability
- Link GitLab issues to the vulnerability
- Automatically remediate the vulnerability
Each security vulnerability in a project’s Vulnerability Report has an individual page which includes:
- Details of the vulnerability.
- The status of the vulnerability within the project.
- Available actions for the vulnerability.
- Any issues related to the vulnerability.
On the vulnerability’s page, you can:
- Change the vulnerability’s status.
- Create a GitLab issue.
- Create a Jira issue.
- Link issues to the vulnerability.
- Automatically remediate the vulnerability, if an automatic solution is available.
You can change the status of a vulnerability using the Status dropdown to one of the following values:
|Detected||The default state for a newly discovered vulnerability|
|Confirmed||A user has seen this vulnerability and confirmed it to be accurate|
|Dismissed||A user has seen this vulnerability and dismissed it because it is not accurate or otherwise not to be resolved|
|Resolved||The vulnerability has been fixed and is no longer valid|
A timeline shows you when the vulnerability status has changed and allows you to comment on a change.
To create a GitLab issue for a vulnerability:
- In GitLab, go to the vulnerability’s page.
- Select Create issue.
An issue is created in the project, prepopulated with information from the vulnerability report. The issue is then opened so you can take further action.
- Enable Jira integration for vulnerabilities. Select Enable Jira issues creation from vulnerabilities when configuring the integration.
To create a Jira issue for a vulnerability:
- Go to the vulnerability’s page.
- Select Create Jira issue.
An issue is created in the linked Jira project, with the Summary and Description fields pre-populated. The Jira issue is then opened in a new browser tab.
The option to create a Jira issue for a vulnerability is under development but ready for production use. It is deployed behind a feature flag that is enabled by default. GitLab administrators with access to the GitLab Rails console can opt to disable it.
To enable it:
To disable it:
You can link one or more existing GitLab issues to the vulnerability. This allows you to indicate that this vulnerability affects multiple issues. It also allows you to indicate that the resolution of one issue would resolve multiple vulnerabilities.
Linked issues are shown in the Vulnerability Report and the vulnerability’s page.
You can fix some vulnerabilities by applying the solution that GitLab automatically generates for you. Read more about the automatic remediation for vulnerabilities feature.