Complimentary 90-day, on-prem license available for entities involved in Covid19 response.

24/5 Hotline Support Service

+44 (0)20 3588 3841

Open a Support Ticket

Integrating Netsparker Standard with GitLab

GitLab is a web-based application that covers the entire DevOps lifecycle from idea to production. It provides a Git-repository manager providing wiki, issue-tracking and CI/CD pipeline features.

This topic explains how to configure Netsparker Standard to send a detected vulnerability to GitLab.

For further information, see Configuring the User Interface for Custom Send To Actions in Netsparker Standard and Configuring Auto Send To Actions in Netsparker Standard and What Systems Does Netsparker Integrate With?.

GitLab Fields

This table lists and explains the GitLab fields in the Send To Actions tab.




Click to add an integration.


Click to delete the integration and clear all fields.

Create Sample Issue

Once all relevant fields have been configured, click to create a sample issue.


This section contains general fields about the Send to Action.

Display Name

This is the name of the configuration that will be shown on menus.


This section contains fields that must be completed.


This is the personalized access token of the user.

Project ID

This is the project identifier in which to create an issue.


This section contains fields with vulnerability details.

Body Template

This is the template file that is used to create description fields.

Title Format

This is the string format that is used to create the vulnerability title.


This section contains optional fields.

On-Premise Base URL

This is the issue that can be sent to on-premises with your base URL.

Assignee ID

This is the assignee identifier.

Milestone ID

This is the issue milestone ID.


This is the value of the weight.

Due Days

This is the number of days from the date the issue was created to the date it's due.


These are the issue labels.

How to Integrate Netsparker Standard with GitLab

  1. Open Netsparker Standard.
  2. From the Home tab on the ribbon, click Options. The Options dialog is displayed.
  3. Click Send To Actions.

  1. From the Add dropdown, select GitLab. The GitLab fields are displayed.

  1. The Display Name field is already populated.
  2. In the Mandatory section, complete the connection details:
    • Access Token
    • Project ID
  3. In the Vulnerability section you can change the Body Template and Title Format.
Body templates are stored in %userprofile%\Documents\Netsparker\Resources\Send To Templates. If you use your own custom templates, store them in this location.
  1. In the Optional section you can specify:
    • On-Premise Base URL
    • Assignee ID
    • Milestone ID
    • Weight
    • Due Days
    • Labels
  2. Click Create Sample Issue to confirm that Netsparker Standard can connect to the configured system. The Send To Action Test dialog is displayed.

  1. In the Send To Action Test dialog, click the Issue number link to open the GitLab issue in the default browser.

How to Export Reported Vulnerabilities to Projects in GitLab

Please ensure that you have first configured GitLab integration (see How to Integrate Netsparker Standard with GitLab).
  1. Open Netsparker Standard.
  2. From the ribbon, select the File tab. Local Scans are displayed. Doubleclick the relevant scan to display its results.

  1. In the Issues panel, right click the vulnerability you want to export to GitLab and select Send to GitLab. (Alternatively, from the ribbon, click the Vulnerability tab, then Send to GitLab.) A confirmation message and link is displayed at the bottom of the screen.

  1. Click the GitLab Send to Action is executed for the selected vulnerability. link to view the newly-created issue in GitLab.
  2. The vulnerability is automatically exported to GitLab. You can view it in the GitLab Issues tab.


Dead accurate, fast & easy-to-use Web Application Security Scanner