Site24x7
Connect Site24x7 to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Site24x7 to collect observability evidence with automated compliance tests, switched on per workspace.
| Category | Observability |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Site24x7's guide | site24x7.com |
Connect with an API token
-
In Site24x7:
- Open the Zoho Developer Console for your data center (api-console.zoho.com, or the api-console.zoho.eu, .in, .com.au, .jp, zohocloud.ca or other regional equivalent) and click Get Started Now › Self Client › Create Now.
- Open the self client, go to the Generate Code tab, enter the scopes Site24x7.Admin.Read,Site24x7.Account.Read, a description and a validity duration (3 to 10 minutes), and generate the code. Copy the grant code and the self client's client ID and client secret.
- POST client_id, client_secret, the code and grant_type=authorization_code to your data center's token endpoint. The response's access_token is the value for Safeguard's Access token field; it expires after expires_in seconds (typically 3600), and the refresh_token gets a new one.
Where to find the other values:
- Data center: The Zoho data center where your Site24x7 account lives (United States .com, Europe .eu, India .in, Australia .com.au, Japan .jp, Canada zohocloud.ca and so on), the same one whose Developer Console (api-console.zoho.*) you used.
Source: site24x7.com, checked 2026-10-07.
The permissions Safeguard needs:
Site24x7.Admin.Read,Site24x7.Account.Read. -
On Compliance › Connectors, open Site24x7, click Connect, choose API token and fill in:
Field What to enter Data center Required. Access token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Site24x7 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, CC7.2 | 4 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.2, A.8.16 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(b) | 4 |
| PCI DSS | Automated tests | 7.2.2, 7.2.4, 8.2.5, 10.4.1 | 4 |
| NIST CSF 2.0 | Automated tests | DE.CM-01, PR.AA-01, PR.AA-05 | 4 |
These tests are switched on per workspace by the Safeguard team.
Related
- Observability 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