Table 15. Changes to Assessment and Discovery policies (continued)
If you... | Then you... |
|
|
Modify the configured settings | Cannot save the policy. Therefore, the |
| changes apply to only that ad hoc scan and |
| do not affect configured background scans. |
|
|
Scan Control policy
You cannot configure refresh cycles or scan windows for ad hoc scans because they are not included in the ad hoc Scan Control policy. The following table describes how refresh cycles and scan windows from the background Scan Control policy affect ad hoc scans:
Table 16. Ad Hoc Scan Control policy
Option from Background Scan Control |
|
policy | Impact on ad hoc scans |
|
|
Scan Windows | You can choose whether to run an ad hoc |
| scan only during the open scan windows |
| defined for background scans and to pause |
| when the windows close. |
|
|
Refresh cycles | Ad hoc scans are never bound by the refresh |
| cycles that apply to background scans. Ad |
| hoc scans continue to scan until they finish |
| or until you stop them. Ad hoc scans pause |
| when scan windows close if you select the |
| option to run the scans only during open |
| scan windows. |
|
|
Scan window and refresh cycle examples
Assume the following points:
vYour scanning refresh cycle is every two days.
vScanning windows run from 8:00 P.M. until midnight and from 1:00 A.M. until 4:00 A.M. each day.
Table 17. Examples of scan windows and refresh cycles with ad hoc scans
| You start an ad hoc scan that takes three |
| hours. The scan runs from 11:00 P.M. until |
At 11:00 P.M. on the... | midnight, and then the scan runs from... |
|
|
First night of a refresh cycle | 1:00 A.M. until 3:00 A.M. on the second day |
| of the same refresh cycle. |
|
|
Second night of a refresh cycle | the scan runs from 1:00 A.M. until 3:00 A.M. |
| on the first day of the next refresh cycle. |
|
|