Blackpoint Cyber
Connect Blackpoint Cyber to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Record your Blackpoint Cyber connection as endpoint detection & response evidence. Automated collection is not available for this provider yet.
| Category | Endpoint Detection & Response |
| Connect with | API token |
| What a connection produces | Connection record |
Connect with an API token
-
In Blackpoint Cyber, create the credential for API token / Personal access token, read-only where it offers that. Blackpoint Cyber does not publish these steps; its support team can confirm them.
-
On Compliance › Connectors, open Blackpoint Cyber, 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
Blackpoint Cyber 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 | CC6.8 | 1 |
| ISO/IEC 27001 | Attestation | A.8.7 | 1 |
| HIPAA Security Rule | Attestation | 164.308(a)(5) | 1 |
| PCI DSS | Attestation | 5.2.1 | 1 |
| NIST CSF 2.0 | Attestation | DE.CM-09 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Endpoint Detection & Response 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