Console

Added scan engine pooling support to support both nmap and masscan. Multiple scan engines can be assigned to a pool, and that pool can be assigned to a site. A site's targets will be evenly distributed between the number of scan engines in the pool.

Caveats are that it does not understand CIDR notation. If the targets are 10.0.0.0/24 192.168.1.0/24 10.1.2.3, it will not evenly distribute the 513 targets (256 + 256 + 1) evenly across the scan engines. If 3 scan engines are in the pool, engine1 will scan 10.0.0.0/24, engine2 will scan 192.168.1.0/24, and engine3 will scan 10.1.2.3.

Another caveat is that the separate scan files (both .xml and .json) for pooled scans are not combined to make a final merged file. That capability will be coming later, for now, the onus is on the user to combine them.

API Client

• The API client has not been updated to utilize the new /api/engine_pools endpoint.