Recurring scans / operations reference
AUTOMATED
VULNERABILITY SCANNER
Explore HostedScan
Define the job

Automated Vulnerability Scanner

An automated vulnerability scanner needs an operating process around it: approved targets, a bounded job, visible failures, reviewed findings and someone responsible for repairs. HostedScan is the featured hosted platform in this operations reference. The guides examine recurring scan reliability rather than treating a schedule or dashboard as proof that a target was checked.

A schedule is not an observation

Imagine a scan scheduled every night for a hypothetical customer portal. On Monday the test account expires. On Tuesday a worker times out. The dashboard still displays Friday’s clean result. The schedule continues to exist, but the recent target has not been examined under the intended conditions.

An operating record must distinguish these facts. Keep last attempted run, last completed run and last relevant observation separate. A stale successful result is not today’s successful scan.

Build the job before increasing its frequency

The category guide defines a recurring scanning process. The job-contract entry records authority, access, limits and evidence. The failure-handling entry keeps retries from disguising missing work.

Different scanners contribute different observations

HostedScan coordinates several scanner types. OpenVAS is a network/host scanner component, while Invicti Web + API focuses on running web applications and APIs. The directory distinguishes those roles instead of presenting every tool as the same autonomous security service.

Keep findings attached to accountable decisions

The recurring scan runbook is an original operating template. It separates the status of a scan job from the status of findings and repairs. A completed run can leave open findings; a failed run can leave no new evidence at all.

Operations questions

Does running more often guarantee better coverage?

No. Repeating a job with expired access or the wrong target repeats the operating problem. Frequency matters only in relation to valid execution and the behavior actually checked.

Should a failed job automatically be retried forever?

No. Bound retries and distinguish transient failures from invalid access or policy problems. Repeated failure needs an owner and visible stale evidence.

Can repeated alerts be merged?

Yes, when target identity and the underlying issue justify one remediation record. Preserve observation times and relevant changes instead of deleting the history.

Evidence before automation claims

The sources establish published supplier roles. The methodology defines evaluation criteria. These articles do not report a completed scanner trial or benchmark.