As the title says, with the recent UI update to the site configuration screen, you can no longer utilize asset groups to scan a subset of devices if the site was configured only with subnets. This was useful from a license management perspective, as what I would do is scan all IPs for discovery, and then do a vulnerability scan against assets that had been tagged and place into groups. I also used the exclusion groups for this too, I would exclude SQL servers from the normal audit, and use a different schedule to scan just those using a different scan template.
Based on my current workflow I am going to need to create an extra site for every existing site configured with asset groups so I can keep having scans configured the way I do today. Essentially a site for discovery and a site for vulnerability scans.
The documentation has been updated to reflect this change, so it doesn’t appear to be a bug but an intentional change. Please reconsider!
I have already opened a Critical Ticket on this, apparently i was the first to report This and also you can no longer add a single IP or a Group of IP addresses in a NEW schedule with the INCLUDE only option.
They are aware that something is BROKE, and internally they are apparently reviewing it… at least this is what i have been told
Yes, they closed it with a RUN command fix to revert back, and they also patched it and fixed already as well… If this is not the case on your end, let me know…