StackHawk
Connect StackHawk to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect StackHawk 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 |
| StackHawk's guide | docs.stackhawk.com |
Connect with an API token
-
In StackHawk:
- Sign in to the StackHawk platform as the user whose access Safeguard should use (API resources are only accessible to applications and organizations that user belongs to and is permissioned to access).
- Go to Settings › API Keys and create a new API key.
- Copy the key and store it securely; it is long-lived.
Where to find the other values:
- Organization ID (optional): Not given in StackHawk's API key documentation.
StackHawk's public documentation does not cover every step.
Use a personal API key, not a Service Key: StackHawk Service Keys have only the Scan Only role, which is deliberately narrow for CI/CD scanning (it cannot triage findings or manage users, teams or integrations). The API key is exchanged for an access token via GET /api/v1/auth/login with the X-ApiKey header. Button labels on the API Keys page, the role the user needs, and the UI location of the Organization ID were not in the fetched docs.
Source: docs.stackhawk.com, docs.stackhawk.com, checked 2026-10-07.
The permissions Safeguard needs:
Member. -
On Compliance › Connectors, open StackHawk, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. Organization ID (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read StackHawk 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 | 3 |
| ISO/IEC 27001 | Automated tests | A.8.8 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1) | 3 |
| PCI DSS | Automated tests | 6.3.3, 11.3.1 | 3 |
| NIST CSF 2.0 | Automated tests | ID.RA-01, ID.RA-06 | 3 |
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