Invicti
Connect Invicti to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Invicti to collect vulnerability scanning evidence with automated compliance tests, switched on per workspace.
| Category | Vulnerability Scanning |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Invicti's guide | invicti.com |
Connect with an API token
-
In Invicti:
- Log in to Invicti Enterprise as the user Safeguard will use.
- Select [Your Name] (top right of the window) › API Settings.
- Enter your Current Password (SSO users are not asked for a password), then click Submit to view your User ID and Token.
- Copy the User ID and the API Token.
Where to find the other values:
- User ID: [Your Name] › API Settings shows the User ID after you click Submit.
- Base URL (optional): Invicti Enterprise uses https://www.netsparkercloud.com/api/1.0; the docs also list regional URLs for United States 2, European Union and Canada.
The API token belongs to the user and carries that user's permissions; the read-only role assignment was not quoted on the fetched page. If SSO is enabled but the page still asks for a password, enable Enforce to authenticate only with single sign-on under Settings › Single Sign-On. Reset API Token invalidates the old token. Applies to Invicti Enterprise On-Demand and On-Premises.
Source: docs.invicti.com, checked 2026-10-07.
The permissions Safeguard needs:
read-only role. -
On Compliance › Connectors, open Invicti, click Connect, choose API token and fill in:
Field What to enter User ID Required. API token Required. Stored encrypted and never shown again. Base URL (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Invicti and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC7.1 | 4 |
| ISO/IEC 27001 | Automated tests | A.8.8 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1) | 4 |
| PCI DSS | Automated tests | 6.3.3, 11.3.1 | 4 |
| NIST CSF 2.0 | Automated tests | ID.RA-01, ID.RA-06 | 4 |
These tests are switched on per workspace by the Safeguard team.
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