Expected Scanning Behaviors For Ad Hoc Scans - IBM Proventia Network Enterprise Scanner User Manual

Expected Scanning Behaviors for Ad Hoc Scans

Introduction
Expected behaviors
IBM Proventia Network Enterprise Scanner User Guide, Version 1.3
This topic answers question you may have about what to expect from ad hoc scans in
different circumstances.
Expect the following with ad hoc scans:
When is an ad hoc scan scheduled in the Command Jobs window?
Q:
As soon as you start it as long as it runs without regard to scanning windows. If it
A:
runs only during scanning windows, it is not scheduled until a scanning window is
open.
When does an ad hoc scan start to run?
Q:
An ad hoc scan starts to run immediately after it appears in the Command Jobs
A:
window as follows:
You set up the scan to run at any time—not only during scan windows.
■
You set up the scan to run during scan windows, and a scan window is open.
■
You set up the scan to run during scan windows, but you have not defined a Scan
■
Window policy for the group. (This is not the same as having defined a Scan
Window policy without defining scan windows. See the next question.)
Why would and ad hoc scan not start to process?
Q:
You did not enable a discovery or an assessment scan when you started the ad hoc
A:
scan.
You did not define at least one IP address for a discovery scan.
A:
If you set up the scan to run during scan windows, but you have not defined Scan
A:
Windows for the group you are scanning.
This could happen if you define a Scan Window policy for the group, but you have
not defined any Scan Windows in the policy. The default for an unmodified Scan
Window policy is that scan windows are open at all times. If you open and save the
Scan Window policy for any other reason; however, the windows change to closed.
You must define scan windows for both discovery and assessment scans if you
modify the Scan Window policy.
Why does it take so long for an ad hoc scan to start?
Q:
An ad hoc scan may not start right away if both of these conditions are true:
A:
You initiate the scan during a closed scan window.
■
You configure the scan to run only during scan windows.
■
Why did my ad hoc scan continue to run even when the refresh cycle started again?
Q:
Refresh cycles do not apply to ad hoc scans, so ad hoc scans continue to run even if a
A:
new refresh cycle starts.
Expected Scanning Behaviors for Ad Hoc Scans
157