Jira

LiveDeveloper

Jira connector — read-only, agentless

Audits your Jira Cloud site — public projects and "Anyone on the web" filters/dashboards, admin sprawl and dormant users, permission schemes that grant sensitive actions to everyone, missing issue-security on security-labeled projects, insecure webhooks, unrecognized write-scoped apps, and automation rules that post data externally. Read-only.

Connect Jira ← Back to all connectors

What we scan

Projects and their visibility, permission schemes, issue-security schemes, workflows, webhooks, connected apps and scopes, automation rules, shared filters/dashboards, and the user directory (never record data)
Only the labels and identifiers of security-tagged issues, to flag exposure — never issue bodies or credentials

Read-only monitoring — nothing in your Jira data changes unless you turn on auto-remediation and grant write access separately.

Before you connect

• A Jira / site admin who can authorize 8200.dev via Atlassian OAuth (3LO)
• A Jira Cloud site (the connector reads via api.atlassian.com)

Typical first scan: 1–4 minutes depending on site size

Permissions requested

read:jira-workRead projects, project visibility, permission schemes, issue-security schemes, webhooks, automation rules, and the labels/security levels of issues — the access + configuration surface. Never issue contents; never write.
read:jira-userRead the user directory (display name, account type, active state) to distinguish members from portal customers and external guests and to flag admin sprawl and dormant accounts — the internal/external boundary.
offline_accessObtain a refresh token so the Connector Health Daemon can keep the read-only connection alive without re-prompting an admin — never grants any additional data access.

Security findings

15 detection rules run on every Jira scan. Each finding ships with a plain-language explanation, the evidence behind it and remediation steps.

CRITICALPublic exposure
Jira project is publicly visible
CRITICALPublic exposure
Jira filter or dashboard shared with "Anyone on the web"
HIGHMisconfig
Sensitive Jira project has no Issue Security Scheme
HIGHOver permission
Jira permission scheme grants a sensitive action to everyone
HIGHMisconfig
Jira webhook posts to a non-HTTPS endpoint
HIGHOver permission
Too many Jira administrators
MEDIUMExternal access
External user can access a sensitive Jira project
MEDIUMPublic exposure
Jira Service Management portal is public
MEDIUMMisconfig
Security-labeled Jira workflow has no approval step
MEDIUMShadow it
Unrecognized write-scoped app is connected to Jira
MEDIUMShadow it
Jira automation rule posts to an external URL
MEDIUMOver permission
Sensitive Jira issues are visible to all project members
MEDIUMMisconfig
Vendor AI-training data-contribution posture
LOWStale access
Stale (long-inactive) Jira user
LOWPublic exposure
Attachments exposed on a public Jira project

How to connect Jira

Step 1
Sign up or log in to 8200.dev
Step 2
Go to Connectors → Jira
Step 3
Click Connect and authorize via Jira's consent screen
Step 4
8200.dev scans automatically — results appear within minutes

Connect your first source in minutes — free, read-only, no sales call.

Connect Jira See all 23 connectors →