Nucleus Security
Connect Nucleus Security to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Nucleus Security 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 |
| Nucleus Security's guide | api-docs.nucleussec.com |
Connect with an API token
-
In Nucleus Security:
- As a Nucleus organization administrator, navigate to Global Dashboard › Global Administration › Users.
- In the top row, click Add API Account and enter an API Account Username (this account only has API access).
- Select the project(s) the account should read and, for each project, assign a Role with read-only permissions (see Defining new roles to create one).
- Click Create Account.
- Find the new account in the Users list, click the View API Key For Account icon under Actions, click Show API Key, copy the key, and click Close.
Where to find the other values:
- Instance URL: The URL of your Nucleus console.
- Project ID (optional): The project's ID; see the API docs (Help › API Docs in the Nucleus console).
Alternative: a user with API Access can generate a personal key under the User icon › User Profile › Generate API Key. A key stays valid until regenerated or the user is deleted/disabled. The key is sent in the x-apikey header. The exact read-only role name is defined per organization.
Source: help.nucleussec.com, api-docs.nucleussec.com, checked 2026-10-07.
The permissions Safeguard needs:
read-only access to the projects. -
On Compliance › Connectors, open Nucleus Security, click Connect, choose API token and fill in:
Field What to enter Instance URL Required. Your own server: an https address reachable from the internet. API key Required. Stored encrypted and never shown again. Project ID (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Nucleus Security 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