devguard - Your Compliance Platform
PlatformSolutionsFrameworksDevelopersPricing
devguard

One workspace for your whole ISMS — Swiss-hosted, one control set, mapped to every framework you run.

All systems operational
Product
PlatformFeaturesSolutionsFrameworksPricing
Developers
API & CLIIntegrationsDocumentationChangelogSwiss hosting
Company
AboutBlogCompare
© 2026 devguard AG. All rights reserved.
Terms of servicePrivacy policySite noticeTrust centerLLM info
Swiss Made Software
Integrations · Security

Have I Been Pwned
compliance checks, automated

devguard queries the Have I Been Pwned domain search for your domain and turns breach exposure into evidence: the API connects, your domain is monitored, and new breaches surface as findings.

The checks

What devguard checks in Have I Been Pwned

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”.

API key authenticates to Have I Been Pwned

Confirms the API key authenticates and has domain-search access by listing subscribed domains. A 401 or 403 is reported as an invalid key or a missing domain-search subscription rather than a silent error.

api-connectivity

info

Domain is subscribed and verified

Coverage guard: fails if the configured domain is not among the account's subscribed, verified domains, which would let the breach check pass vacuously. Guards against asserting on a domain HIBP is not actually monitoring.

domain-under-monitoring

medium

No breached accounts on the domain

Fails if any account on the domain appears in a known breach. HIBP returns HTTP 404 when no accounts on the domain are breached (the clean, passing state) and HTTP 200 with an alias-to-breaches object when there are — that 200 is the failing state. A 401/403 is a hard error (not swallowed), so an auth or verification problem never reads as clean.

no-breached-accounts

high

Bring your current platform's test list — we'll map it against these checks, gap by gap

How it connects

Connected by you, scoped by you

Setup is minutes, not a migration project — and every step stays on your side

01

Create a read-only credential

Create the credential in Have I Been Pwned 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.

02

Checks run on a schedule

The first run starts right after connecting, then repeats on a schedule. Results are timestamped, so your evidence has a history, not a snapshot.

03

Evidence lands on the control

Passing results attach as evidence to the controls they support; failures become findings you triage. When the audit comes, the proof is already connected.

Related

More from your stack

Open any page for its full check register.

Read-only, revocable, Swiss-hosted

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.

FAQ

Questions about Have I Been Pwned

Is the Have I Been Pwned access read-only?

Yes. The checks authenticate with a credential you create and scope yourself, and only ever read configuration. devguard holds no write access to Have I Been Pwned and remediates nothing silently.

What happens when a check fails?

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.

Where do the results live?

Checks run from Swiss infrastructure, and results and evidence are stored in Switzerland. Everything is exportable — your evidence stays yours.

Connect Have I Been Pwned and see the evidence land

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.

Book a conversation
Book a conversation
Snyk
3 checks
SonarCloud
4 checks
See all integrations
Book a conversation
Sign in
Start for free
Book a conversation
Start for free