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

Define the contract for an automated scan job

A job contract states what a recurring scan may do, what it must produce and what happens when prerequisites fail. It is an operational record, separate from a supplier’s commercial terms.

Identify the approved work

Record target identifiers, environments, owner, access mode, selected policy and trigger. Split jobs where their access or operating boundaries differ. An unauthenticated external check and an internal credentialed scan may need separate contracts even when one platform runs both.

For an illustrative portal, name the application release path and the approved account role. If a job targets a changing asset group, record how membership is controlled and reviewed. Discovery does not automatically authorize checks against every discovered address.

Define prerequisites and outputs

List required access, connectivity, representative data and evidence storage. Give each prerequisite an owner. Record the output format and retention needed for triage, while keeping credentials out of reports.

Specify what a successful execution establishes. Avoid a success definition based only on process exit or file creation if those signals do not show relevant checks completed.

Set limits before scheduling

Include execution duration, concurrency, request or resource constraints supported by the tool, restricted operations and stop conditions. Agree how a later configuration change is reviewed. Increasing frequency or target scope can change operational effects even when the scanner executable is unchanged.

Use bounded retries for appropriate transient failures. Invalid access, scope rejection and explicit stop instructions should lead to attention rather than an endless retry loop.

Assign failure and result owners

An operations owner restores a broken job; a security reviewer interprets observations; a system owner repairs the affected service. One person may fill several roles, but the responsibilities remain distinct.

The failure guide addresses stale results, and the runbook provides the contract fields alongside run and remediation records.

Continue reading

Cite this entry

Automated Vulnerability Scanner. “Define the contract for an automated scan job.” Reviewed 2026-11-16.
https://automatedvulnerabilityscanner.com/scan-job-contract/