Deep Audit · live scan timeline
Module-by-module progress for an in-flight audit (recon iterations, crawl complete, JS endpoint discovery, fuzzbox phases, every scanner module's start + complete).
Last updated Jun 9, 2026
What it is
Every Deep Audit scan has a live activity panel on the scan detail page. It streams the JupiterSec runtime’s milestone events in real time, with a phase label, severity colour, and a brief description.
The panel polls every 2 seconds while the scan is running and auto-scrolls so the newest event is always visible. When the scan finishes the timeline freezes as a complete record of what happened.
What you see
| Event class | Example |
|---|---|
| Scan lifecycle | Scan started against php.target.com |
| Recon | Crawl complete · 36 URLs discovered · Recon iteration 1 complete · 60 URLs |
| Discovery | JS endpoint discovery · 12 files analysed · Hidden parameter found: name |
| Fuzzing | Wordlist fuzzing · phase 1 starting · Fuzzbox iter 1 phase 1 complete |
| Scanner modules | Module started: SQL Injection · Module complete: Cross-Site Scripting |
| Phase boundaries | Phase 1 complete · exit 0 · 3343s |
| Triager | ✓ confirmed SQLi @ /api/search · ✗ rejected verbose-error @ /login |
| Explorer | Phase 4 · AI Explorer starting (Tier 1+2+3) |
A pulsing “currently working on…” line sits below the latest event when the scan is running. It reads the latest event and prints a present-tense activity description (“fuzzing wordlist against discovered routes…”, “Triager judging next finding…”), so the panel never looks frozen between events.
Why it matters
Buyers running a paid scan want to see motion. A traditional DAST tool runs for an hour and produces one log line. Deep Audit gives the operator hundreds of meaningful milestones: every module start + complete, every recon iteration, every Triager judgement.
For the operator running multiple audits in parallel, the panel is also a fast way to spot a stuck scan (no events for >10 minutes) or a partial-coverage outcome (a phase that exits with a warning).
What’s not in the timeline
Internal errors, daemon restarts, S3 transfer details: anything that’s plumbing rather than scan progress is omitted on purpose. Operators get a clean, progress-only narrative.