We want to use the Scan Assistant on some business-critical servers as an alternative to the usual authenticated scans. Our IT has asked if there is any official information on how much resources the scan assistant requires in idle mode and during scans. This is important for them in order to avoid operational disruptions and to allocate more resources to the target systems if necessary.
I have already installed the scan assistant on a rather less critical server and performed a test scan and did not notice any major increase in CPU load and memory usage. If I had something from the official side, I could push the utilization of the Scan Assistant further internally.
Hi. @david_altanian. Thanks for your interest in the Scan Assistant. As I am sure you can appreciate, there are a number of factors that can affect system resource utilization. However, I wanted to provide some representative guidance, based on our testing. The Scan Assistant will occupy approximately 20MB in memory. It will consume 0% CPU when idle. On different system configurations and Windows OS variants, we have observed CPU utilization ranging from 2.5% to 6% when the Scan Assistant is active (i.e. called upon to perform a scan by a Scan Engine), for a duration of 60 to 120 seconds while the scan is completed. This guidance would apply to Vulnerability scans, on a system that is at a reasonable patch level.
I hope this helps.
Thanks for your feedback. This coincides with my observation when I performed the test scan on a server. CPU usage barely moved and memory had very short spikes. But this also happens when I scan the same system without scan assistant.