Action1
Connect Action1 to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Action1 to collect mdm evidence with automated compliance tests, switched on per workspace.
| Category | MDM |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Action1's guide | app.action1.com |
Connect with an API token
-
In Action1, create the credential for Client secret with
view_endpoints. Action1's guide: app.action1.com. Action1 does not publish these steps; its support team can confirm them. -
On Compliance › Connectors, open Action1, click Connect, choose API token and fill in:
Field What to enter Client ID Required. Client secret Required. Stored encrypted and never shown again. Region Required. Organization ID (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Action1 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 | 2 |
| ISO/IEC 27001 | Automated tests | A.8.1, A.8.8, A.8.9 | 2 |
| HIPAA Security Rule | Automated tests | 164.308(a)(5), 164.310(d)(1) | 2 |
| PCI DSS | Automated tests | 6.3.3, 12.5.1 | 2 |
| NIST CSF 2.0 | Automated tests | ID.AM-01, PR.PS-02 | 2 |
These tests are switched on per workspace by the Safeguard team.
Related
- MDM 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