Platform.sh
Connect Platform.sh to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Platform.sh to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.
| Category | Cloud Infrastructure |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Platform.sh's guide | docs.platform.sh |
Connect with an API token
-
In Platform.sh:
- Recommended: create a machine user (a separate account with its own email address) and give it only the access Safeguard needs.
- Log in to the Console as that machine user.
- Open the user menu (your name or profile picture) and click My profile.
- Go to the API tokens tab and click Create API token.
- Enter a name for the token and click Create API token.
- Click Copy to copy the token. After you close the API tokens tab you can't display it again.
Platform.sh shows the secret only once, so copy it before you leave the page.
Platform.sh's public documentation does not cover every step.
docs.platform.sh now redirects to Upsun's docs (fixed.docs.upsun.com). Platform.sh issues no read-only token; the token has the machine user's access. Where the Console shows the Organization ID was not found in the docs checked; Environment is the environment name shown in the project.
Source: fixed.docs.upsun.com, checked 2026-10-07.
The permissions Safeguard needs. Platform.sh issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time.
-
On Compliance › Connectors, open Platform.sh, click Connect, choose API token and fill in:
Field What to enter API token Required. Stored encrypted and never shown again. Organization ID Required. Environment (optional) — -
Click Connect with token.
Frameworks
Safeguard's automated tests read Platform.sh 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.1, CC6.2, CC6.3 | 4 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2, A.8.5 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(d) | 4 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5, 8.4.2 | 4 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-03, PR.AA-05 | 4 |
These tests are switched on per workspace by the Safeguard team.
Related
- Cloud Infrastructure 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