Front
Connect Front to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Front to collect communications platforms evidence with automated compliance tests, switched on per workspace.
| Category | Communications Platforms |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Front's guide | dev.frontapp.com |
Connect with an API token
-
In Front:
- Sign in to Front as an admin and go to Settings › Developers.
- Go to the API Tokens tab and click Create API token.
- Specify an API token name.
- Choose the features, namespaces and permissions: enable Access resources, pick the namespace that holds teammates, and grant read only.
- Click Create. To get the token value, open the token from the API Tokens tab and click Reveal or Copy.
You must be an admin to create or manage API tokens; tokens are company-level and visible to all admins, who can later Reveal or Copy them. Namespaces offered are Global resources (company-level), Shared resources (workspace-level) and Private resources (individual teammates). Which namespace grants teammates:read was not stated unambiguously on the fetched page; Global resources is the likely choice for company teammates, but verify in the scope picker. The optional Access token field is an OAuth token from a Front app; not documented here.
Source: dev.frontapp.com, checked 2026-10-07.
The permissions Safeguard needs:
teammates:read. -
On Compliance › Connectors, open Front, click Connect, choose API token and fill in:
Field What to enter API token Optional. Stored encrypted and never shown again. Or, instead: Access token (optional).
-
Click Connect with token.
Frameworks
Safeguard's automated tests read Front 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.2, CC6.3 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 3 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- Communications Platforms 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