Jira
Collect Jira project and change-ticket evidence through read-only Jira REST endpoints.
Generic connector
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.
- Project inventory
- Jira Cloud issue evidence when JQL searches are provided
- Customer-configured Jira Cloud/Data Center evidence endpoints
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.
- API base URL
- Auth header value(secret credential)
- Auth header name
- JQL searches
- Issue fields
- Evidence endpoints (JSON)
Required
Optional
Where this evidence goes
Which frameworks this evidence supports
Jira 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 Jira evidence
Get a guided demo, or start by scanning any domain for free.