01
Create a read-only credential
Create the credential in Zendesk with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
devguard reads your Zendesk instance and verifies support-desk access: admins are reviewable, and agents sign in with two-factor authentication.
4 read-only checks, run on a schedule. Each failure becomes a finding linked to a control — every check is listed, none are “coming soon”.
Connectivity check: confirms the Basic API token reaches Zendesk and resolves the current user via /api/v2/users/me.json (HTTP 200). A non-200 (e.g. 401) indicates an invalid token or wrong subdomain.
account-connectivity
Access-review check: fails if the number of users with the admin role exceeds the approved maximum. Enumerates admins with page-number pagination.
admin-access-review
Fails if agent two-factor authentication is not enforced org-wide (`security_settings.authentication.agent.two_factor_enforce` is not true). Reads /api/v2/security_settings, which requires an admin token.
two-factor-enforced
Fails if the agent session timeout exceeds the approved maximum (in minutes; default 60). Reads /api/v2/security_settings, which requires an admin token.
session-timeout
Bring your current platform's test list — we'll map it against these checks, gap by gap
Setup is minutes, not a migration project — and every step stays on your side
Create the credential in Zendesk with the minimum read scope, paste it into devguard, and the connection is live. The integration page in the product spells out the exact permissions.
The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.
Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.
Open any page for its full check register.
You create and scope every credential yourself, and you can revoke it at any time. Checks only read; results and evidence are stored in Switzerland and stay exportable.
Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to Zendesk and remediates nothing silently.
A failed check becomes a finding linked to the control it supports, with the evidence attached. You decide the treatment — nothing pages your engineers and nothing is auto-remediated.
Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.
20 minutes on how you run certification today. Bring your current test or control list and we'll map it against these checks — honestly, gap by gap.