Fireworks AI
Connect Fireworks AI to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Fireworks AI 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 |
| Fireworks AI's guide | docs.fireworks.ai |
Connect with an API token
-
In Fireworks AI:
- Install and sign in to Fireworks' firectl CLI.
- Create a service account, assigning its role with the --role flag:
firectl user create --user-id "my-service-account" --service-account --role=<role>(Fireworks' Managing users page lists the available roles; the default service account role is user). - Create an API key for it:
firectl api-key create --service-account "my-service-account"and copy the key it prints.
Where to find the other values:
- Account ID: Your Fireworks account ID is the account part of resource names; for example, Fireworks shows service accounts as my-service-account@<account-id>.sa.fireworks.ai.
Fireworks AI issues this credential through its API or its support team, not through its admin screens.
Source: docs.fireworks.ai, checked 2026-10-07.
The permissions Safeguard needs:
admin role (an admin service account). Fireworks AI issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time. Needs the API key of an admin, best an admin service account (firectl user create --service-account --role admin), and your account ID. Listing every user's keys needs the admin role. -
On Compliance › Connectors, open Fireworks AI, click Connect, choose API token and fill in:
Field What to enter API key Required. Stored encrypted and never shown again. Account ID Required. For example: acme-prod -
Click Connect with token.
Frameworks
Safeguard's automated tests read Fireworks AI 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, CC7.2 | 10 |
| 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, A.8.15 | 10 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.308(a)(5), 164.312(b), 164.312(d) | 8 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5, 8.4.2, 8.6.3, 10.2.1 | 8 |
| NIST CSF 2.0 | Automated tests | DE.CM-09, GV.OC-03, PR.AA-01, PR.AA-03, PR.AA-05 | 10 |
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