Bitbucket
Collect workspace and repository evidence from Bitbucket Cloud APIs.
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
- Workspace repository inventory when a workspace is provided
- Repository branch restrictions when workspace and repository 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
- Workspace
- Repository slugs
- Evidence endpoints (JSON)
Required
Optional
Where this evidence goes
Which frameworks this evidence supports
Bitbucket 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 Bitbucket evidence
Get a guided demo, or start by scanning any domain for free.