First Scan Task Guide

Create a target, select it in a task, then start a scan and review its report. The screenshots show demonstration devices or fictional form examples.

A target defines which hosts and ports to examine. A scan config defines the tests. A task combines those choices with a scanner and optional schedule or alerts. A report records one run. For all available settings, see the Vulnerability Scanner manual.

Before creating the task, confirm the hosts and scan window with the system owner. Review the available configurations under Vulnerabilities → Configuration → Scan configs. When creating the task, select the appropriate configuration in the Scan Config field. Vulnerabilities → Administration → Feed status shows the status of scanner reference-data updates. Scans can generate traffic and load; choose a scan window appropriate for the systems and their expected load.

Creating a Target

1. Open Vulnerabilities → Configuration → Targets and select Create target.
2. Enter a descriptive Name and optional Comment.
3. Enter the approved Hosts. Separate entries with commas, semicolons, or new lines. Use Exclude hosts for addresses within that scope that must be left out.
4. Select the Port list and Alive test. Review any saved SSH, SMB, or ESXi credentials needed for authenticated checks. A credential selection of -- leaves that credential unassigned.
5. Review the scope, then select Create. Cancel or X closes the draft without creating a target.

These addresses are examples. Replace them with the assigned addresses of the hosts you intend to scan. The screenshot excludes 192.0.2.20, leaving 192.0.2.10 in its example scope.

The target is a separate saved object. Return to Scans → Tasks after creating it; the task’s Scan target selector chooses from existing targets. For additional options, see Targets, ports, and credentials.

Creating a Schedule

A schedule is optional. For a first manual scan, leave the task’s Schedule at -- and continue to the next section.

To prepare recurring scans:

1. Open Vulnerabilities → Configuration → Schedules and select Create schedule.
2. Enter a Name, an optional Comment, the Start Date, Start Time, and Timezone. Confirm the time in the selected timezone.
3. Review Open End. When it is off, set the end date and time; the displayed duration summarizes the selected window.
4. Choose Recurrence: Once, Hourly, Daily, Weekly, Monthly, Yearly, or Custom. Custom exposes Every and Unit. Check the resulting calendar pattern rather than assuming monthly recurrence means the same weekday.
5. Select Create to save the schedule. Then assign it through the task’s Schedule selector. Saving the schedule itself does not select a task for it.

Review recurring assignments when copying or replacing a task so that two jobs do not run the same scan unintentionally. See Scanner schedules for the timing controls.

Creating a scan task

1. Open Vulnerabilities → Scans → Tasks and select Create task. The flyout is titled New Task.
2. Enter Name and Comment. Select the target you prepared under Scan target.
3. Select the Scanner and Scan Config. The demonstration form uses OpenVAS Default and Full and fast; review the configuration’s test scope before using it on your systems.
4. Leave Alerts unassigned if no notification is needed. Leave Schedule at -- for a manual first run, or select the schedule you prepared. Review Once if a selected schedule should execute only once.
5. Review Add results to Assets, Apply Overrides, Min QoD, report retention, and concurrency limits. The task field reference explains these controls.
6. Select Save to create the task. A task with an assigned schedule can run according to that schedule. Cancel or X abandons an unsaved draft.

To update a saved job, use All actions → Edit task as described in Altering Vulnerability Scans.

Start the scan and review its report

For a manual run, find the saved task and select its play icon or All actions → Start new scan. This requests the run immediately. Wait for the status to update rather than repeatedly selecting Start. Requested/Queued means waiting, Running means active, and Done means the run ended. Eligible interrupted jobs offer Resume task; active jobs offer Stop task.

Open All actions → View reports for that task, or go to Scans → Reports and choose the relevant date range. Open a report and review:

Done is not the same as a successful clean scan. The demonstration report above has Error severity, zero hosts, and zero results. An empty error-message tab does not make that evidence complete.

Vulnerability Scanner manual · Return to How to Guides

---