01
Create a read-only credential
Create the credential in Exoscale 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 signs each request with Exoscale's HMAC scheme and checks the Swiss cloud's security posture: SSH keys are registered for key-based access, and no security-group rule opens SSH to the whole internet.
3 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 + inventory: fails if the key cannot list compute instances in the ch-gva-2 zone (any non-200 status).
instance-inventory-reachable
Fails if the organisation has no registered SSH keys, which suggests password-based instance access rather than key-based access.
ssh-keys-registered
Scans every security-group rule and fails if any ingress rule covering port 22 is open to 0.0.0.0/0 or ::/0. Zero-count framing over the full rule set, so a missing rules array can never produce a false pass.
no-ssh-open-to-internet
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 Exoscale 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 Exoscale 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.