01
Create a read-only credential
Create the credential in Google Workspace 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.
Through the Admin SDK Directory API, devguard reads your Google Workspace tenant and verifies two-step verification posture user by user, the identity evidence auditors ask for by name.
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: fails if the impersonated service-account token cannot read the Workspace user directory.
directory-reachable
Fails if any active (non-suspended) user does not have two-step verification enforcement applied. Also fails if no users are returned, to avoid a vacuous pass.
two-factor-enforced
Enforcement without enrollment still leaves a gap. Fails if any active (non-suspended) user is not enrolled in two-step verification. Also fails if no users are returned, to avoid a vacuous pass.
two-factor-enrolled
Least-privilege check: fails if the number of users with super-admin rights exceeds the approved maximum (CIS recommends 2 or fewer). Also fails if no users are returned, to avoid a vacuous pass.
super-admin-count-limited
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 Google Workspace 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 Google Workspace 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.