Hugging Face
Connect Hugging Face to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Hugging Face to collect business applications evidence with automated compliance tests, switched on per workspace.
| Category | Business Applications |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Hugging Face's guide | huggingface.co |
Connect with an API token
-
In Hugging Face:
- Signed in as an organization admin, go to your settings and click the Access Tokens tab (huggingface.co/settings/tokens).
- Click New token.
- Choose the fine-grained role, name the token, and grant it access to your organization.
- Create the token and copy it (it starts with hf_).
Where to find the other values:
- Organization: Your Hugging Face organization's name.
Hugging Face's public documentation does not cover every step.
Tokens management (listing members' tokens) is a Team & Enterprise feature; Enterprise organizations can also issue fine-grained tokens from Service Accounts. Fine-grained tokens an org admin creates for their own organization are auto-approved even under a "Require administrator approval" policy. The fetched docs do not name the individual fine-grained organization permission checkboxes, so they are not listed. Hugging Face has no read-only admin credential.
Source: huggingface.co, huggingface.co, checked 2026-10-07.
The permissions Safeguard needs:
organization admin (fine-grained token),Team or Enterprise plan. Hugging Face issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time. Needs an access token of an organization admin (or an Enterprise service account) and the organization's name. Hugging Face shows members' emails and tokens only on Team and Enterprise plans. -
On Compliance › Connectors, open Hugging Face, click Connect, choose API token and fill in:
Field What to enter Access token Required. Stored encrypted and never shown again. Organization Required. For example: acme-ai -
Click Connect with token.
Frameworks
Safeguard's automated tests read Hugging Face 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 | C1.2, CC6.1, CC6.2, CC6.3, CC6.5 | 8 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.17, A.5.18, A.5.34, A.6.5, A.8.2, A.8.5, A.8.10 | 8 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.308(a)(5), 164.312(d) | 7 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5, 8.4.2, 8.6.3 | 7 |
| NIST CSF 2.0 | Automated tests | GV.OC-03, PR.AA-01, PR.AA-03, PR.AA-05 | 8 |
These tests are switched on per workspace by the Safeguard team.
Related
- Business Applications 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