# Export to Securitm

> Automatic upload of infrastructure scan reports to SGRC Securitm.

Source: https://scansuite.eu/documentation/usage/working-with-scan-results/export-to-securitm
Last reviewed: 2026-10-19

Infrastructure scan reports can be uploaded automatically to SGRC Securitm after each scan of the team. These reports are sent:

| Scanner (Infrastructure Checks) | File sent |
|---|---|
| Nessus | The .nessus report |
| OpenVAS | The XML report |
| Network Discovery (Nmap) | The XML report |

Other scanners, the AI Pentest and reports imported with **Upload Report** are not sent.

## Set it up

You need the Operator or Team admin role, and a Securitm API token that may import vulnerability scan results.

1. > **A person does this step:** A Securitm administrator creates the API token in Securitm. Ask your Securitm administrator for a token that may push vulnerability scan files.
2. Open **Teams** (sidebar, Admin), the **Integrations** tab, and find the **Securitm** block of the **Issue trackers** card.
3. Fill in the fields and click **Save**.

   > **A person does this step:** A person types the API key into the form.
   >
   > An agent never asks for it in the chat.

   *Check:* the Securitm block shows as connected.

| Field | What it holds | Default |
|---|---|---|
| Address | The address of your Securitm instance, starting with https://. | Empty: nothing is sent |
| API key | The Securitm API token. Stored encrypted and never shown again; leave it empty when editing to keep the saved one. | Empty |

The card says *Leave a tracker empty to keep findings in ScanSuite only*: with either field empty, nothing is uploaded.

![Securitm configuration](https://scansuite.eu/static/assets/img/docs/usage/working-with-scan-results/export-to-securitm/01.png)

*The Securitm block of the Issue trackers card*

## Check that it works

There is no test button. Run a Nessus, OpenVAS or Network Discovery scan, open its page and read the scan log: for each file it shows *Uploading <file> to Securitm:* followed by Securitm's response.

![Securitm upload log](https://scansuite.eu/static/assets/img/docs/usage/working-with-scan-results/export-to-securitm/02.png)

*Upload confirmation in the scan log*

The vulnerabilities then appear in the respective Securitm section:

![Securitm vulnerabilities view](https://scansuite.eu/static/assets/img/docs/usage/working-with-scan-results/export-to-securitm/03.png)

*Vulnerabilities in Securitm*

If no upload line appears, check that both fields are saved. If Securitm answers with an error, the response in the log says why — usually the token's rights or the address.

> **Note:** For every other route findings can take, see [Reports and exports](https://scansuite.eu/documentation/usage/reports-and-exports).