Sweeps
A Sweep tries one condition against every target in scope: every database, every certificate, every account, every site. One results table, with the targets it could not observe called out instead of counted as safe.
Sweep · every 6 h
Every business database has a backup from the last 24 hours
42
Tried
3
Missing a backup
33
Within window
6
Not observed
Since the last run
Newly missing1
Still missing2
Fixed1
Newly found2
Not observed is reported as its own result, never counted as safe.
Outcomes
Each target in a Sweep lands in exactly one outcome, with the reason attached.
Affected
The condition does not hold for this target. The reason and the owner come with it.
Clear
Tried and the condition holds. The value it observed is kept.
Not observed
Panaptico could not test this target, usually missing access. Shown as its own count, so coverage gaps stay visible.
Run over run
Every finished Sweep is compared with the one before it, so a new problem never hides inside a familiar number.
Targets that were clear last run and are not now. Usually where to start.
Known problems, with how long each has been open.
Targets fixed since the last run, with when they cleared.
Targets that joined the scope since last time, tried on their first run.
Scope
A collection step lists what's in scope from the source: every database in AWS and Azure, every certificate on your domains.
The same condition runs against every target, read-only, from the hosted sandbox or your own runner.
By system, owner, tier, or region, so each team sees its own share of the table.
Examples
Works with
Point a Sweep at a scope you already have. Panaptico finds the targets and returns one table you can act on.