ESET Protect
Connect ESET Protect to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect ESET Protect 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 |
| ESET Protect's guide | help.eset.com |
Connect with an API token
-
In ESET Protect:
- Sign in to ESET PROTECT Hub as a Superuser.
- Go to Users and add a new user for Safeguard.
- Set the user's permissions to the read-only permission set your organization uses (assign custom permission sets in ESET PROTECT if needed).
- Under Permissions, enable the toggle next to Integrations.
- Click Next, then Create.
- The new user receives an invitation email and must finish the account creation process, then sign in to ESET PROTECT Hub at least once before Safeguard uses it.
- If you use ESET Business Account or ESET MSP Administrator 2 instead: sign in as Superuser (or Root), create the user in User management, enable the toggle next to Integrations under Access Rights, and click Create.
ESET Protect's public documentation does not cover every step.
Only the Root or Superuser can create a user with API access, and API access cannot be granted to the ESET Business Account Superuser, ESET MSP Administrator 2 Root user or ESET PROTECT Hub Superuser accounts. Not found on the fetched pages: the name of a read-only permission set, what to enter as the Username, and how to tell which Region your account is in.
Source: help.eset.com, help.eset.com, checked 2026-10-07.
The permissions Safeguard needs:
read-only permission set. -
On Compliance › Connectors, open ESET Protect, click Connect, choose API token and fill in:
Field What to enter Region Required. Username Required. Password Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read ESET Protect 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 | 4 |
| ISO/IEC 27001 | Automated tests | A.5.26, A.8.1, A.8.7, A.8.16 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(5), 164.308(a)(6) | 4 |
| PCI DSS | Automated tests | 5.2.1, 5.3.1, 12.10.1 | 4 |
| NIST CSF 2.0 | Automated tests | DE.AE-02, DE.CM-09, RS.MI-02 | 4 |
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