CoreStack
Connect CoreStack to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your CoreStack connection as cspm evidence. Automated collection is not available for this provider yet.
| Category | CSPM |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In CoreStack:
- Sign in to CoreStack as ops_admin.
- Click the settings icon in the top-right corner and select Users.
- Click the + icon to add a new user and fill in the required details with a valid email address.
- Check Generate API Access, then click Create User.
- The new user receives an activation email and a separate email containing the API URL, Access Key and Secret Key.
- Exchange the Access Key and Secret Key for an authorization token with the AuthToken API (POST /v1/auth/tokens with access_key and secret_key) and paste the token into Safeguard's API token / Personal access token field.
Where to find the other values:
- Base URL (optional): The API URL in the email CoreStack sends to the API user; the documented API host is
https://api-discover.corestack.io. - Account / Org / Workspace (optional): Not shown in a documented UI location. The AuthToken response includes a tenants list, each tenant with an id and name.
CoreStack's public documentation does not cover every step.
The AuthToken reference says auth tokens are valid only for an hour, so a pasted token goes stale quickly. The AuthToken reference shows the endpoint on api.corestack.io while the API modules page names https://api-discover.corestack.io as the API host; use the API URL from the email. Not sourced: a read-only role for the API user.
Source: docs.corestack.io, docs.corestack.io, checked 2026-10-07.
-
On Compliance › Connectors, open CoreStack, click Connect, choose API token and fill in:
Field What to enter API token / Personal access token Required. Stored encrypted and never shown again. Base URL (optional) — Account / Org / Workspace (optional) — -
Click Connect with token.
Frameworks
CoreStack publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Attestation | CC7.1 | 1 |
| ISO/IEC 27001 | Attestation | A.8.8 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(1) | 1 |
| PCI DSS | Attestation | 6.3.3, 11.3.1 | 1 |
| NIST CSF 2.0 | Attestation | ID.RA-01 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- CSPM 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