Capability architecture
Run the right collection or validation method for the target.
Scanning orchestration coordinates approved tools, scope and timing while preserving results as evidence rather than merging them into an opaque score.
01Why it matters
- Continuous validation needs orchestration that can balance coverage, speed and production safety.
- Security teams need repeatable scans without losing control over scope or intensity.
- Automation must be observable, pausable and auditable.
02ThreatCanary approach
- Support fast, normal and thorough profiles for discovery and testing.
- Coordinate tools, agents and workflows through event-driven execution.
- Record scan history, raw outputs, observations and status for audit and reprocessing.
03What it validates or reveals
- Scan coverage and progress.
- Out-of-scope prevention and safe execution.
- Repeatable workflows that can be scheduled, paused, resumed and retested.
04Evidence produced
- Tool, configuration, scope and execution record.
- Normalised result with original evidence retained.
- Coverage, failure and retry status.
