1. Acquire Workflow
pulls/accepts SARIF + lockfiles + SBOM, normalizes them, and indexes findings and dependency relationships.
Why Argonaut
Rationale, Judging Criteria, and Architecture Details
Security teams typically juggle SARIF outputs from multiple scanners, dependency lockfiles, SBOMs, threat intelligence feeds, and manual ticket creation across Jira/Slack. That workflow is brittle: the same vulnerability appears in multiple tools, reachability is unclear, and urgency is often guessed. Argonaut automates the full loop from evidence → context → action.
Argonaut reuses an existing local triage engine (Argus) for what it already does well—parsing SARIF, extracting dependencies from lockfiles/SBOMs, and computing reachability signals—then layers Agent Builder orchestration on top to make it an agent that "gets work done." Elasticsearch becomes the shared system-of-record and memory layer.
pulls/accepts SARIF + lockfiles + SBOM, normalizes them, and indexes findings and dependency relationships.
attaches threat intel context (KEV/EPSS/advisory flags) and reachability confidence.
joins findings + threat intel + reachability to compute a Fix Priority Score and returns the top fix-first set with explanations.
creates Jira tickets for the top items and posts a Slack summary that includes "why this is ranked #1," linking back to Kibana views.
Alignment with official hackathon criteria
Argonaut clearly demonstrates: Multi-step reasoning, Tool orchestration, Elasticsearch-first design, Real-world automation, Measurable impact, Explainable output, and Production-style architecture. This positions it strongly for Top 3 placement or at minimum Creative Award.