Skip to main content

Scanning Lifecycle

Purpose​

Describe how a scan moves from request to findings and reports.

Validity Note​

  • Status: CONFIRMED
  • Basis: Lifecycle claims are validated internally against current implementation and operational behavior.

High-Level Flow​

  1. Authentication + org context
  2. Scan creation (target, scan_type)
  3. Discovery/scan jobs executed by workers
  4. Findings persisted and exposed via API/UI
  5. Reports generated from scoped findings

Phase Model​

Common phase progression includes:

  • Discovery
  • Port/service scan
  • Vulnerability scan

Exact orchestration can vary by scan type and runtime configuration.

Job and Worker Behavior​

  • Work is pushed to queue-backed execution.
  • Workers consume jobs in parallel.
  • Progress and outcomes are tracked for UI/API visibility.

Progress and Visibility​

  • Scan list/detail endpoints expose status and phase-level context.
  • Findings endpoints expose actionable result data.
  • Report endpoints provide generation and download/stream access.

Failure and Recovery​

  • Failed jobs are retried/recovered according to runtime policies.
  • Orchestration uses idempotency protections to avoid duplicate phase advancement.
  • Worker loss should not require full scan pipeline restart.

Next Action​

Continue with Integrations.