← All integrations
Live integration

Jira Cloud

Ticketing · OAuth 2.0 · Daily

OAuth 2.0 (3LO). Pulls site project count, total + open ticket counts, and a sample of recently-resolved security tickets for change-management evidence.

Authentication
OAuth 2.0
Sync cadence
Daily
Stale threshold
Every 2 days
Category
Ticketing

Evidence this connector produces

Every sync writes typed evidence rows linked to the controls below. Evidence is immutable once attached to an approved assessment, fingerprinted for de-dup, and surfaced in the control coverage calculation on your dashboard.

SOC 2 CC8.1

How to connect

Create an OAuth 2.0 (3LO) integration in the Atlassian developer console. We'll redirect you to atlassian.com to authorize.

  1. 1
    Create the integration

    developer.atlassian.com → My apps → Create → OAuth 2.0 integration.

  2. 2
    Add Jira scopes + callback

    Permissions → Jira API → grant read:jira-work + read:jira-user. Authorization → callback URL: http://localhost:3000/api/integrations/jira/callback

  3. 3
    Copy credentials

    Settings → Authentication: copy the Client ID + Secret. The site URL (e.g. acme.atlassian.net) is required after authorization.

Security model

Every connector ships behind the same auditor-grade primitives — not just RBAC config, but architectural enforcement.

Credentials KMS-encrypted at rest

Tokens, client secrets, and service-account keys are encrypted under a per-tenant AWS KMS data key. The plaintext is never persisted, never logged, and never leaves the FastAPI process boundary.

Tenant-isolated by architecture

Every Connection, ConnectorRun, and emitted Evidence row carries an organization ObjectId. The scheduler never iterates without an org-scoped filter; cross-tenant evidence bleed is impossible at the data layer.

Audit log on every action

Connect, sync, sync-failure, re-auth, and revoke each write a row to the immutable AuditLog. The full lifecycle is reconstructable for any examiner.

Soft-delete on revoke

Revoking a connection sets deletedAt and clears the encrypted credential blob, but the historical evidence + sync log stays queryable for the retention window. Auditors can still trace what was attested when.

Stale-evidence degradation

If this connector hasn't synced in Every 2 days, control coverage degrades automatically and an alert fires. Auditors don't trust stale evidence — neither do we.

Least-privilege scopes only

We request the minimum read-only scopes needed for the listed evidence. No write scopes, no admin scopes, no scopes outside the documented set.

Ready to connect Jira Cloud?

Connect from Settings → Integrations — typically under 5 minutes. Or talk to us first.

Request a demoSign in to connect