Remote Sites with Narrow Bandwidth
If you have a remote site with narrow The definition of narrow band-width is not specifically defined here. The primary reason for this is that it is a relationship to the width of the pipe, the number of targets and the type of scanning that is required (e.g. windows based scanning over WMI typically has a higher overhead than SSH based scanning) bandwidth, we can approach these scans in a way that optimizes performance by doing the following:
- Enable scanning on these sites during agreed hours with a reduced thread count and manual supervision of the scan. This scan approach uses significantly fewer bandwidth resources.
- Install a remote scanning server in each site sending its data back to the primary SQL server. This allows control from one location and uses less bandwidth than the first option, as the only information being passed over the WAN connection would be the cleansed results going into the database. The network engineers can also limit the bandwidth available to this remote scanning server over the WAN.
- Install a full Scan Engine server on a server O/S to laptops or VMs which can be installed in each site. This will allow the scanning server to scan the site with no communication over the WAN except for an RDP session to the VM/laptop. The results would have to be managed separately and combined at a later stage.
However, customer specific site restrictions can be discussed by sending an email to the iQuate support team and they will be happy to assist you.