Webex
Connect Webex to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Webex to collect communications platforms evidence with automated compliance tests, switched on per workspace.
| Category | Communications Platforms |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Webex's guide | developer.webex.com |
Connect with an API token
-
In Webex:
- Log in to the Webex Developer Portal (https://developer.webex.com) and select My Webex Apps from the menu under your avatar.
- At the top of the page, click Create a New App, then Create a Service App to start the wizard.
- Enter the service app's name, description and logo (admins see these in Control Hub), and select the scopes spark-admin:people_read and spark-admin:roles_read only.
- Finish registration. Copy the Client Secret from the page that follows: it is shown once only (it can be regenerated later).
- On the Service App details page, click Request Admin Authorization so the app becomes visible in your organization's Control Hub.
- A Full Admin then signs in to Control Hub (https://admin.webex.com), goes to Management › Apps › Service Apps, clicks the service app, reviews the requested scopes, and clicks Authorize followed by Save.
- Back on the Service App details page in the Developer Portal, go to the Org Authorizations section, select your organization from the drop-down list, paste the client secret into the provided field, and retrieve and copy the access token.
The authorizing admin must be a Full Admin (read-only and device admins are not enough). In a free (unpaid) org, Webex says to request a developer sandbox to get an admin who can authorize. Service app access tokens follow integration token policy: typically 14 days for the access token and 90 days for the refresh token, so the access token must be refreshed or re-copied from Org Authorizations. The client secret is shown once; the page does not say whether the access token can be re-read later, so one_time_display is left null for the token itself. Viewing all people in the org requires an admin token with spark-admin:people_read (People API reference).
Source: developer.webex.com, developer.webex.com, checked 2026-10-07.
The permissions Safeguard needs:
spark-admin:people_read,spark-admin:roles_read. -
On Compliance › Connectors, open Webex, click Connect, choose API token and fill in:
Field What to enter Access token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Webex 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.2, CC6.3 | 3 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2 | 3 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4) | 3 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5 | 3 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05 | 3 |
These tests are switched on per workspace by the Safeguard team.
Related
- Communications Platforms 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