Skip to main content
Findings are security issues identified across your assets and pentest runs. Everything Mjolnir discovers, plus any issues surfaced through black-box testing or manual triage, lands here.
Odin findings dashboard showing a list of security findings with severity indicators

​
Severity levels

Each finding is assigned a severity based on exploitability and impact:
SeverityDescription
CriticalImmediate exploitation risk. Requires urgent remediation.
HighSignificant risk with a realistic exploitation path. Address promptly.
MediumReal issue but harder to exploit or lower impact. Plan remediation.
LowMinor issue or defence-in-depth improvement. Fix when practical.

​
Finding status

Each finding moves through a status lifecycle:
  • New: just identified, not yet reviewed
  • In progress: remediation is underway
  • Solved: fix has been applied and verified
  • Ignored: acknowledged but accepted as a known risk

​
What’s inside a finding

Every finding includes the detail your engineering team needs to take action:
  • Title and description: a clear summary of the vulnerability
  • Severity rating: Critical, High, Medium, or Low
  • Affected asset: the domain, endpoint, or resource where the issue was found
  • Reproduction steps: exact steps to reproduce the vulnerability
  • Suggested fix: actionable remediation guidance
  • Source: whether the finding came from Mjolnir, black-box testing, or manual triage
Use the filters at the top of the Findings page to narrow down what you see:
  • Severity: focus on Critical and High first
  • Status: show only New findings, or hide Ignored ones
  • Source: filter by Mjolnir, black-box, or manual findings
  • Asset: scope findings to a specific domain or endpoint
Bookmark a filtered view (the URL updates as you filter) to quickly return to the findings that matter most to your team.

​
Bulk operations

Select multiple findings to act on them at once. Use the checkboxes on each row, or navigate with j/k and toggle selection with x. When findings are selected, a bulk action bar appears at the bottom of the page:
  • Update status — set all selected findings to Mitigating or Mitigated in one action
  • Export selected — download the selected findings as a CSV with key columns (title, severity, CVSS, status, and discovery date)
Status changes sync automatically to connected integrations — if a finding has a linked Linear, Jira, or GitHub issue, the external issue is updated too.
Bulk operations require the Member role or higher.

​
Exporting findings

Click the Export button in the page header to download your current findings view. The export respects any active filters, so you can narrow down by severity, status, or source before exporting. Three formats are available:
FormatDescription
CSVSpreadsheet-friendly format with columns for title, severity, CVSS, status, description, business impact, details, remediation, and timestamps
JSONMachine-readable format with the same data, useful for scripting or importing into other tools
MarkdownHuman-readable format with each finding as a section, including metadata tables and full descriptions
Use the CSV export to share a findings summary with stakeholders who don’t have access to Odin, or to import findings into a spreadsheet for custom reporting.

​
Pushing findings to your issue tracker

If you’ve connected Linear, Jira, or GitHub Issues, you can push any finding directly to your issue tracker with one click. The finding title, description, severity, and suggested fix are all included. You can also enable auto-ticketing to create issues automatically when new findings are reported. Set up your integration at Management > Integrations.

Set up integrations

Connect your issue tracker