Huntress
Connect Huntress to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Huntress to collect endpoint detection & response evidence with automated compliance tests, switched on per workspace.
| Category | Endpoint Detection & Response |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Huntress's guide | api.huntress.io |
Connect with an API token
-
In Huntress:
- Sign in to the Huntress Platform as a user with Admin privileges.
- Open the menu in the upper right corner and choose API Credentials.
- In the User API Credentials section, click Add.
- Select the user the key belongs to (pick a user with read-only access; the key mirrors that user's permissions), enter a Key Name such as Safeguard, and click Add.
- Copy the API Key and Secret from the box that appears, then click Ok.
Huntress shows the secret only once, so copy it before you leave the page.
The support article URL returned HTTP 403 to an anonymous fetch; the same article was read through Huntress's Help Center API (support.huntress.io/api/v2/help_center/en-us/articles/4416826761235.json) and supports every step. Huntress: 'The full key is shown only once after creation. Huntress cannot retrieve this key if it is lost.' The changelog confirms user keys mirror that user's permissions. The article says Account API keys are deprecated and provide read-only access to only part of the data.
Source: support.huntress.io, feedback.huntress.com, checked 2026-10-07.
-
On Compliance › Connectors, open Huntress, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. API secret Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Huntress 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 | CC6.8, CC7.2, CC7.3, CC7.4 | 6 |
| ISO/IEC 27001 | Automated tests | A.5.26, A.8.1, A.8.7, A.8.16 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(5), 164.308(a)(6) | 6 |
| PCI DSS | Automated tests | 5.2.1, 5.3.1, 5.3.5, 12.10.1 | 6 |
| NIST CSF 2.0 | Automated tests | DE.AE-02, DE.CM-09, PR.PS-01, RS.MI-02 | 6 |
These tests are switched on per workspace by the Safeguard team.
Related
- Endpoint Detection & Response 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