01
Create a read-only credential
Create the credential in SendGrid 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 checks your SendGrid account posture: sending domains authenticated with SPF and DKIM, and API keys scoped to least privilege rather than full access.
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 API key authenticates and reads the account object (HTTP 200). A non-200 (e.g. 401) indicates an invalid or under-scoped key.
account-connectivity
Fails if any authenticated sending domain is not valid (SPF/DKIM records not resolving). Also fails if no domains are returned, to avoid a vacuous pass. Reads up to 100 domains in one page (the endpoint uses numeric offset paging, which the check DSL cannot express).
domain-authentication-valid
Fails if the key in use carries broad mutating scopes beyond a review need (specifically `mail.send` or `user.account.update`), and equally if the key's scope list is empty or cannot be read: a key whose privileges cannot be established cannot be shown to be least-privilege. Supports a least-privilege review of the monitoring credential.
api-key-least-privilege
Access-review check: fails if the number of teammates with admin access (`is_admin` true) exceeds the approved maximum. Reads up to 100 teammates in one page (the endpoint uses numeric offset paging, which the check DSL cannot express).
teammate-admin-review
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 SendGrid 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 SendGrid 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.