Nuclei
Connect Nuclei to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Nuclei connection as vulnerability scanning evidence. Automated collection is not available for this provider yet.
| Category | Vulnerability Scanning |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Nuclei:
- Sign in to the ProjectDiscovery Cloud dashboard (https://cloud.projectdiscovery.io/).
- In the left navbar, go to Settings › API Key (https://cloud.projectdiscovery.io/settings/api-key).
- View and copy your API key.
Where to find the other values:
- Base URL (optional): Leave empty for ProjectDiscovery Cloud; the API is the ProjectDiscovery API v1 over HTTPS.
- Account / Org / Workspace (optional): Your ProjectDiscovery Cloud team, if you belong to more than one (the location of the team ID in the UI was not found in the fetched docs).
Nuclei itself is an open-source CLI; scan results are only available through an API when they are uploaded to ProjectDiscovery Cloud. The API key is a per-user key sent in the X-Api-Key header and has that user's access; ProjectDiscovery documents no read-only key scope.
Source: docs.projectdiscovery.io, checked 2026-10-07.
-
On Compliance › Connectors, open Nuclei, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
No automated compliance test reads Nuclei yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.
Related
- Vulnerability Scanning connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks