Unable to add Scope to Scan Job

Problem

When trying to add a scope to a scan job, the selected scope is not added when clicking on the update button.

Reproduction/Solution

An example of the identified problem is described below. A scope is created for a large subnet (in this case 64k+ IPs)

In the Scan job, the scope is selected by clicking on the check box and the update button is clicked.

The result is the Update is not accepted. The Scope is unticked and the warning above (yellow triangle) remains in place.

The problem is caused because the scope specified in the single range is greater that the 32K specified as maximum per scan job. This limit can be hit the IP scope limit if a single sub-range is used within a single scope (or the accumulation of multiple sub-ranges) exceeds this hard limit. The solution is to modify the Scope to include less than 32K IP address range. This may require that additional scan jobs are created to split the original range into smaller sub-ranges. The example below reduces the sub-range scope using the Mask value.

Finally, edit the ScanJob. Select the update scope. Click on the Update button. The scope is now accepted (a tick is now present on the scope).

The limit for 32K IPs is accumulated across all scopes assign to a scan job.