Inspecting scan runs - Kikimora

Each scheduled scan definition acts as a container for its individual executions. Expanding a scheduled scan row reveals an inner table of that definition’s run history.

What an individual run represents

A run is a single execution of the scan against the target web application at one moment in time. Where the parent definition holds the recurring parameters, the run holds the snapshot: the vulnerabilities present during that execution, how long it took, and its log results.

Inner table columns

Column	Description
Run Status	State of this execution — `Finished`, `Running`, `Failed`, or `Canceled`.
Started Date	Exact date and time the run commenced.
End Date / Duration	When the run completed, plus total execution time.
Vulnerabilities Found	Findings from this run, broken down by severity.
Actions Menu (`...`)	Per-run actions such as View Results, Preview, Scan Again, and Delete.

Open a scan’s run history

Find the scheduled scan in the Scans table. Scheduled scan rows carry an expand arrow (>) next to the scan name.
Click the expand arrow (>) to open the inner runs table.

⌘I