Uptycs
Connect Uptycs to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Uptycs 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 Uptycs:
- Sign in to your Uptycs tenant (for example https://<tenant>.uptycs.io).
- Go to Configuration › API Keys and download your API key JSON file. It contains key, secret, customerId, domain and domainSuffix.
- On older consoles: go to Configuration › Users, click Edit on your user name, then create and download the User API key.
Where to find the other values:
- Base URL (optional): Your tenant address, https://<tenant>.uptycs.io; the downloaded API key JSON also gives domain and domainSuffix.
- Account / Org / Workspace (optional): The customerId value in the downloaded API key JSON file.
Uptycs's public documentation does not cover every step.
Sourced from READMEs in Uptycs' official GitHub organizations (uptycslabs, Uptycs). The newer README names Configuration > API Keys; the older tools README names Configuration > Users > Edit > User API key, so the menu may differ by console version. The API key carries the permissions of the user it belongs to; no read-only role was found in a public source. Uptycs' user guide (docs.uptycs.com, linked from the README as the 'how to create one' page for API access) did not respond to fetches, so the full in-console steps and whether the secret can be downloaded again were not verified.
Source: raw.githubusercontent.com, raw.githubusercontent.com, raw.githubusercontent.com, checked 2026-10-07.
-
On Compliance › Connectors, open Uptycs, 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
Uptycs 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