Jira
上線開發人員Jira 連接器——唯讀、無代理
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.
我們掃描的內容
- 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
唯讀監控——除非您開啟自動修復並單獨授予寫入存取權，否則 Jira 資料中的任何內容都不會改變。
安全發現結果
每次 Jira 掃描時會執行 15 個偵測規則。每個發現結果都附帶純文字說明、背後的證據和修復步驟。
- 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
如何連接 Jira
步驟 1
登入 8200.dev 或建立帳戶
步驟 2
前往連接器 → Jira
步驟 3
按一下「連接」並透過 Jira 的同意畫面授權
步驟 4
8200.dev 自動掃描——結果在幾分鐘內出現
在幾分鐘內連接您的第一個來源——免費、唯讀、無銷售電話。