Runs

The Runs page shows all your Mjolnir pentest assessments, past and present. Open it from Security testing > Full pentests > Pentest history in the sidebar. A stats bar under the header counts your Total Runs, how many are Active, and how many have Completed. Below it sit your scheduled assessments, then the run history itself.

​

Starting a run

Click Run Assessment in the top-right corner to launch a new Mjolnir run. A confirmation dialog opens warning that the run can’t be paused once started. Only one run can be active at a time, so the button is disabled while one is in progress. It is also disabled when no pentest is selected, or when the selected pentest has no Mjolnir configuration. Hover it to see which of those applies. If the configuration is what’s missing, fix that in the setup wizard. Once you confirm, Odin waits for the new run to appear and then opens its detail page. If the queue is slow, you get a message saying the assessment is queued instead, and it shows up in the run list shortly afterwards. To repeat a run later instead of starting one now, use Schedule Assessment next to it. That button stays disabled until you have at least one completed run to schedule from. See Scheduled assessments.

​

Run statuses

Each run has a status indicating where it is in its lifecycle: Active runs display a LIVE badge in the run list.

​

Run list

Run history is a list of cards, one per run. Each card shows:

• Target domain: the primary URL being assessed
• Repository: the source code repository used
• Started: when the run began
• Duration: how long it ran
• Findings: the number of findings discovered (once the run has a summary)

Where a run covered more than one repository or domain, the card carries a +2 repos or +1 domain badge for the extras. If the run has a report, the card also has a download icon, so you can get the PDF without opening the run. Click any run to view its details.

​

Run detail

The detail header shows the target domain, when the run started, and how long it has been going. Abort sits there while the run is active, and Download Report once a report exists. A run that failed or timed out says so in a banner under the header. Where the run covered extra repositories or domains beyond the primary ones, a Scope panel lists them all as badges. Below that are three tabs: Overview, Findings, and Attack surface.

​

Overview

The overview shows the phase stepper, a visual timeline of where the assessment is in its pipeline:

1. Analyse — initial code analysis
2. Map — crawling your application and cross-referencing with source code
3. Plan — generating test cases from the attack surface
4. Attack — running test cases against your targets
5. Report — compiling confirmed findings into a report

Below the phase stepper is a live event feed that streams events as they happen during an active run. Events include reconnaissance discoveries, test case execution, and finding confirmations.

​

Findings

Once a run produces findings, they appear in this tab with the same filtering and detail panel as the main Findings page. You can filter by status, view full finding details, update statuses, and export results. During an active run, this tab shows live finding cards as vulnerabilities are discovered in real time.

​

Attack surface

The Attack surface tab shows what Mjolnir discovered about your application and how much of it was tested. It populates live during a run — the technology stack appears first, during the initial code-analysis phase; endpoints then appear as reconnaissance finds them, and their coverage updates as the attack phase progresses — and stays available after the run completes. Endpoints lists every route Mjolnir found, with its method, path, whether authentication is required, known parameters, observed response codes, and a coverage pill: Use the filter buttons above the table to narrow it to a single coverage state. Alongside the table, two panels give context for the assessment:

• Technology stack — the languages, frameworks, databases, and any high-risk dependencies detected in your code, plus the attack categories Mjolnir prioritised as a result.
• Defences observed — the security controls Mjolnir saw while testing, such as WAF behaviour, Content-Security-Policy and CORS settings, security headers, and cookie flags. If no controls were observed, this panel says so.

Until Mjolnir has learned anything about your application, the tab shows a “Mapping your attack surface…” placeholder; the technology stack is usually the first thing to appear.

​

Aborting a run

While a run is in the Running state, click the Abort button in the run detail header. The run is cancelled and its underlying job terminated. You can start a new run afterwards.

​

Run summary

When a run completes, a summary bar shows:

• Duration: total time taken
• Total findings: the number of vulnerabilities discovered
• Severity breakdown: counts for Critical, High, Medium, and Low

​

Downloading reports

If a report was generated for a completed run, click Download Report in the run detail header to export a PDF containing all findings, reproduction steps, and remediation guidance.