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 · Developer tools

CircleCI
compliance checks, automated

devguard checks CircleCI's access surface: contexts that hold your secrets are restricted, and organization access is reviewable as evidence.

The checks

What devguard checks in CircleCI

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

Token authenticates to CircleCI

Confirms the personal API token authenticates and resolves to a valid user identity.

token-connectivity

info

Context is access-restricted

Fails if the shared context has no restrictions configured, meaning its secrets are usable by every project in the organization.

context-access-restricted

medium

Expected organization is reachable

Access-review attestation: fails if the expected organization slug is not among the collaborations the token can reach, flagging unexpected access drift.

organization-access-review

info

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 CircleCI 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 CircleCI

Is the CircleCI 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 CircleCI 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 CircleCI 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
Anthropic
4 checks
Buildkite
3 checks
Mailgun
3 checks
AI access
MCP server
See all integrations
Book a conversation
Sign in
Start for free
Book a conversation
Start for free