Webroot
Connect Webroot to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Webroot 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 |
| Webroot's guide | unityapi.webrootcloudav.com |
Connect with an API token
-
In Webroot:
- Contact your Webroot representative to acquire credentials (Client ID and Client Secret) for the Webroot Unity API.
- Use the username and password of a Webroot console user with view-only access to the site; Safeguard exchanges them, with the Client ID and Client Secret, for an access token that needs the Console.GSM scope.
Webroot issues this credential through its API or its support team, not through its admin screens.
Webroot's Getting Started page says: 'Please contact your Webroot representative to acquire credentials for accessing the Webroot Unity API.' The API reference names the Console.GSM scope and username/password authentication. Where the GSM key and Site ID are shown in the console was not found on the fetched pages. Webroot has no narrower grant for these reads.
Source: unityapi.webrootcloudav.com, unityapi.webrootcloudav.com, checked 2026-10-07.
The permissions Safeguard needs:
View-only site access,Console.GSM. Webroot has no narrower grant for these reads. Safeguard only reads with it. -
On Compliance › Connectors, open Webroot, click Connect, choose API token and fill in:
Field What to enter GSM key Required. Stored encrypted and never shown again. Site ID Required. Client ID Required. Client secret Required. Stored encrypted and never shown again. Username Required. Password Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Webroot 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 | 2 |
| ISO/IEC 27001 | Automated tests | A.8.1, A.8.7, A.8.16 | 2 |
| HIPAA Security Rule | Automated tests | 164.308(a)(5) | 2 |
| PCI DSS | Automated tests | 5.2.1, 5.3.1 | 2 |
| NIST CSF 2.0 | Automated tests | DE.CM-09 | 2 |
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