Ticketing
GitLab Issues
The CVE to fix lands as a GitLab issue, on gitlab.com or your own instance, and its closing flows back into the case.
What the connector does
TechWatchAlert opens an issue in the chosen GitLab project, on gitlab.com or a self-hosted instance, from an alert's page or through a workflow. The issue carries everything needed to fix, with a link back. Its state comes back into the case through a webhook, and through regular re-reads.
What comes into TechWatchAlert
- One issue per CVE and per project, never two, with severity, EPSS, exploitation, component, fixed versions and description
- A task checklist, a link back to the alert and the labels of your choice
- The status in the case: issue closed, the case moves to “Fixed”, pending verification by the inventory
- Optionally, the issue commented and closed once the fix is verified
Setup
- In the project settings, Integrations › Ticketing tools, add GitLab
- Enter the instance address (gitlab.com by default), the project (group/project) and a project access token with the “api” scope, then “Test and save”
- Optional: add the webhook (issue events) to the project with the address and secret token provided by TechWatchAlert
In the same family
JiraA complete Jira ticket for every CVE to fix, without copying a single line, and its status flowing back into the case.View connector →GitHub IssuesThe CVE to fix lands as a GitHub issue, in the repository of the team that fixes it, and its closing flows back into the case.View connector →GLPI (tickets)The CVE to fix lands as a GLPI ticket, with an urgency that follows the decision, and its resolution flows back into the case.View connector →ServiceNow (incidents)A ServiceNow incident, or a Vulnerability Response vulnerable item, for every CVE to fix, and its state flowing back into the case.View connector →
Connectors
Plug in your tools in minutes
Start with a repository, a fleet or a scan report: your first targeted alerts arrive with the first sync.
Free plan, no credit card · hosted in France