Safeguard Docs
Compliance ConnectorsSetup by categoryCommunications Platforms

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.

CategoryCommunications Platforms
Connect withAPI token
What a connection producesAutomated compliance tests
Webex's guidedeveloper.webex.com

Connect with an API token

  1. In Webex:

    1. Log in to the Webex Developer Portal (https://developer.webex.com) and select My Webex Apps from the menu under your avatar.
    2. At the top of the page, click Create a New App, then Create a Service App to start the wizard.
    3. 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.
    4. Finish registration. Copy the Client Secret from the page that follows: it is shown once only (it can be regenerated later).
    5. On the Service App details page, click Request Admin Authorization so the app becomes visible in your organization's Control Hub.
    6. 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.
    7. 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.

  2. On Compliance › Connectors, open Webex, click Connect, choose API token and fill in:

    FieldWhat to enter
    Access tokenRequired. Stored encrypted and never shown again.
  3. 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.

FrameworkEvidenceControlsTests
SOC2Automated testsCC6.2, CC6.33
ISO/IEC 27001Automated testsA.5.16, A.5.18, A.6.5, A.8.23
HIPAA Security RuleAutomated tests164.308(a)(3), 164.308(a)(4)3
PCI DSSAutomated tests7.2.2, 7.2.4, 8.2.53
NIST CSF 2.0Automated testsPR.AA-01, PR.AA-053

These tests are switched on per workspace by the Safeguard team.

On this page