Beanstalk
Connect Beanstalk to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Beanstalk to collect version control evidence with automated compliance tests, switched on per workspace.
| Category | Version Control |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Beanstalk's guide | api.beanstalkapp.com |
Connect with an API token
-
In Beanstalk:
- Sign in to Beanstalk as an administrator (the Find All Users API method requires admin privileges); an account owner must have API access enabled for the account.
- Generate an access token for your Beanstalk user (each user can generate up to 5 access tokens). The public API docs do not give the menu path.
- In Safeguard, use your regular Beanstalk username as Username and the access token as Access token.
Where to find the other values:
- Account: The subdomain in your Beanstalk address, https://<account>.beanstalkapp.com.
- Username: Your regular Beanstalk login username.
Beanstalk's public documentation does not cover every step.
Docs state only an account owner can enable API access and that listing all users needs admin privileges. The UI click path for creating the token is not in the public API docs.
Source: api.beanstalkapp.com, api.beanstalkapp.com, checked 2026-10-07.
The permissions Safeguard needs. Beanstalk shows the full user list only to administrators, so this credential must belong to one. Safeguard only reads with it. Beanstalk issues no read-only credential. Safeguard only reads with it, and you can revoke it at any time.
-
On Compliance › Connectors, open Beanstalk, click Connect, choose API token and fill in:
Field What to enter Account Required. The part before .beanstalkapp.com in your address. Username Required. Access token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Beanstalk 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
- Version Control 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