跳到正文
DEV Community· Nexus Foundry·· 13 小時前AI 評分30

Bastion 提交至 Codegeist:在 Jira 內即時分流 CVE

I submitted Bastion to Codegeist: live CVE triage inside Jira

AI 導讀

Bastion 是提交至 Codegeist 2026 的駭客松作品,結合 Rovo 智能體、MCP 工具及 Jira 問題面板,利用即時 NVD 數據處理安全問題。Jira 面板會偵測 CVE 提及及易受攻擊的套件,並提供 0–100 風險評分和建議;Forge 應用程式已部署為 Bastion v2.2.0。這是駭客松作品,作者尚未有正式用戶提供工作流程的實際意見。

正文

Security findings usually live in scanners, feeds, and chat threads. Engineering work lives in Jira. Bastion is my attempt to close that gap for the Codegeist 2026 hackathon: a Rovo agent + MCP tools + Jira issue panel that answers security questions with live NVD data instead of guesses.

Submission is live on Devpost: https://devpost.com/software/bastion-om3npy

The problem I kept seeing

A ticket says "log4shell" or "CVE-2024-3094" and then nothing happens. Someone has to context-switch to a vulnerability feed, check whether the affected product is actually in the stack, decide severity, and file work. By the time that happens, the signal is stale.

Bastion keeps the security context next to the work item:

  • Jira issue panel — a Security tab detects CVE mentions and vulnerable-package references, runs a scan, and shows a 0–100 risk score with recommendations.
  • Rovo agent — ask "Is CVE-2024-3094 relevant to us?" or "Scan PROJ-123 for security risk" and it calls live NVD-backed tools, not memory.
  • MCP tools — the same lookup/scan/posture actions are exposed for Rovo Studio and MCP-compatible clients.
  • Daily sweep — a scheduled Forge trigger labels recently updated issues that mention unlabelled CVEs so they stop slipping through.

Design choices that mattered

Live data or silence. Every CVE answer comes from the NVD API at request time. If NVD has no record, Bastion says so — it does not fabricate CVSS scores or affected products.

Deterministic scoring. The risk score is severity-weighted and explainable. That matters for security UX: an agent can summarize, but the number should come from rules a reviewer can audit.

No content rewriting. The daily sweep only adds labels. It never edits ticket text, which keeps the automation boring enough to trust.

Honest status

This is a hackathon submission, not a revenue claim. The Forge app is deployed as Bastion v2.2.0 on a Jira site, the Devpost page shows it submitted to Codegeist 2026, and the demo video is linked. What I do not have yet is production users telling me where the workflow breaks.

If you work on Jira-heavy teams, the failure mode I want feedback on is false confidence: a clean scan should mean "no obvious CVE/package signal in this ticket," not "this system is secure." I tried to make that distinction explicit in the UI copy, but real tickets will teach me more than my own testing.

Related kits

The same security-triage instinct shows up in the NEXUS store as smaller digital kits: Sigma detection rules, an incident-response runbook, and a forensics evidence-collection checklist. Store: https://e74eb3fab8202e.app.lhr.life

Free starter checklist: https://e74eb3fab8202e.app.lhr.life/free

If your team tracks security work in Jira, where does the process break first: detection, triage, or follow-through?

來源:DEV Community · dev.to