Inspiration

Security findings live in scanners and CVE feeds. Engineering work lives in Jira. Every week, teams burn hours context-switching: a CVE drops, someone mentions it in a ticket, and it sits unlabelled for days until a scanner report or an incident forces attention. We wanted security context to be ambient - every issue carrying its own risk assessment, with an agent that does the enrichment work humans should not have to do.

What it does

Bastion is a Rovo agent that brings live CVE intelligence into the Jira workflow:

  • Jira issue panel - every issue gets a Security tab showing detected CVE mentions, one-click scanning, a 0-100 risk score, and per-CVE detail (CVSS, severity, affected products, references) pulled live from the NVD API.
  • Rovo agent - ask Bastion in chat: "Is CVE-2024-3094 relevant to us?", "Scan PROJ-123 for security risk", "Summarise our open security issues", or "File a security task for the log4shell exposure." It queries NVD in real time and answers with real data - never guesses.
  • Rovo MCP - the same four actions are exposed as MCP tools, connectable from Rovo Studio and any MCP-compatible AI client (Claude Desktop, Cursor, custom agents).
  • Daily sweep - a scheduled trigger scans recently-updated issues and auto-labels unlabelled CVE references, so nothing slips through.

How we built it

  • Forge modules: rovo:agent, rovo:mcp, four actions, jira:issuePanel (React), scheduledTrigger
  • Backend: Forge functions in Node.js - Jira issue fetch, ADF parsing, CVE/package extraction, live NVD enrichment with a 6-hour in-memory cache, deterministic risk scoring
  • Risk scoring: severity-weighted and capped - Critical CVE +40, High +20, +5 per CVE (max +20) giving a 0-100 score mapped to Low/Medium/High/Critical. Transparent, auditable, not AI-guessed.
  • Frontend: React panel via @forge/react + @forge/bridge - context-aware issue loading, scan trigger, risk badge, label toggle

Challenges

  • Forge's requestJira route builder does not support .query() chaining - had to construct query strings manually in the URL.
  • Panel resolver + React wiring needed an explicit resolver: reference in the manifest.
  • NVD rate-limits aggressively (HTTP 429) - implemented retry-with-backoff and caching.
  • Keeping the agent honest: every answer traces to live NVD data; the sweep only labels issues, never modifies content.

What is next

Marketplace listing, JSM/security-project templates, and digest reports - Bastion is designed to grow from triage into a full security-operations layer inside Jira.

Built With

Share this project:

Updates

Submission history