A history of every run
Every assessment executed against a scan target is logged: when it ran, how long it took, which target it covered and what it found. That history is what makes a Security Score change explainable — it is tied to a specific, inspectable run.
Recurring, not one-off
Assessment schedules keep evidence current without someone remembering to trigger a re-run. A scan target can be evaluated on a recurring cadence, so the score reflects the third party's environment as it changes, not as it looked at onboarding.
- On-demand assessments for immediate re-evaluation after a fix
- Recurring schedules per scan target
- Real-time progress while an assessment is running
