Cybereason
Connect Cybereason to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Cybereason to collect endpoint detection & response evidence with automated compliance tests, switched on per workspace.
| Category | Endpoint Detection & Response |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Cybereason's guide | nest.cybereason.com |
Connect with an API token
-
In Cybereason, create the credential for Password with
read-only analyst. Cybereason's guide: nest.cybereason.com. Cybereason does not publish these steps; its support team can confirm them. -
On Compliance › Connectors, open Cybereason, click Connect, choose API token and fill in:
Field What to enter Host Required. An address under cybereason.net. Username Required. Password Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Cybereason 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.8, CC7.2, CC7.3, CC7.4 | 5 |
| ISO/IEC 27001 | Automated tests | A.5.26, A.8.1, A.8.7, A.8.16 | 5 |
| HIPAA Security Rule | Automated tests | 164.308(a)(5), 164.308(a)(6) | 5 |
| PCI DSS | Automated tests | 5.2.1, 5.3.1, 12.10.1 | 5 |
| NIST CSF 2.0 | Automated tests | DE.AE-02, DE.CM-09, PR.PS-01, RS.MI-02 | 5 |
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