An illustrative walkthrough · 4 chapters

Schedule vulnerability scans and check what actually ran

A scan was scheduled for this month. Did it finish, and which targets did it cover? See how Sythe Labs schedules approved scans and records the outcome of each run.

1234
01 / Targets · operator-approved assets with saved scan definitions

Chapter 01

Get the targets approved for scanning.

Choose the monitored assets you want scanned and the saved scan definition for each one. Your assigned Sythe Labs operator must approve every selected asset before it can enter the schedule. Adding an asset to inventory alone doesn't authorize testing it.

01 / Targets · operator-approved assets with saved scan definitions

Chapter 02

Set the monthly schedule with your operator.

The operator chooses the day of the month and saves the full list of targets and scan definitions. When that list changes, they update the schedule too. This workflow runs on a monthly cadence; it doesn't continuously probe every system in your inventory.

02 / Schedule · a monthly day and an explicit target list

Chapter 03

Check for scans that failed or never started.

The operator inspects each run's findings and status. If a run exceeds the available scan allowance, only the scans that fit are dispatched; the rest are marked quota-blocked. Errors and incomplete scans need follow-up before anyone uses that run as evidence that all selected targets were checked.

03 / Results · completed scans, errors, and quota-blocked scans

Chapter 04

Attach completed scan results to the evidence record.

An authorized user can attach a completed vulnerability scan to an evidence record for review. Keep the scan's scope in mind when describing what it proves. If maintenance changes the plan for the next run, an operator can reschedule that occurrence or pause the recurring schedule.

04 / Evidence · the completed scan available for review

What you leave with

A monthly scan schedule and run records showing results or incomplete work.

Have a similar task on your team's list? Book a call to discuss how this workflow would fit your systems and who would need to be involved.

Book a call