Table of Contents
Advertisement
Chapter 11: Managing Scans
160
When I run background scans for discovery and assessment, why does the assessment
Q:
scan run as a single job sometimes but as separate jobs for each group at other times?
The answer depends on how you set up your policies. Assume the following:
A:
You have defined a Scan Control policy for a parent group, and that policy is
■
inherited by the subgroups.
You have defined separate Discovery policies for each subgroup.
■
In that case, you can expect the following:
If you set up the Scan Control policy so
that the assessment scan...
waits for the discovery scan to finish before
the assessment scan begins
does not wait for the discovery scan to finish
before the assessment scan begins
Then, the assessment scan...
starts as a separate job for each subgroup as
soon as the discovery scan finishes. This
allows assessment scanning to begin for a
subgroup whose discovery scan has finished
without having to wait for the discovery scans
of all groups to finish.
starts as a single job. There is no need to
create a separate assessment job for each
subgroup since the assessment scan does
not have to wait for the discovery job to finish
before it can start.
IBM Internet Security Systems
Advertisement
Table of Contents
