CircleCI
Collect CircleCI account, context, and project environment-variable evidence through API v2.
Code, CI & delivery
Evidence coverage
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Authenticated user visibility
- Context inventory when an owner slug is provided
- Masked project environment-variable metadata when project slugs are provided
Least privilege
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Auth header value(secret credential)
- API base URL
- Auth header name
- Owner slug
- Project slugs
- Evidence endpoints (JSON)
Required
Optional
Where this evidence goes
Which frameworks this evidence supports
CircleCI evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in CircleCI evidence
Get a guided demo, or start by scanning any domain for free.