When we have a start time for the scan job to start eg. 4am for 4 hours, we notice that the scan job starts at 4:15am instead of hard start 4am, is that they way its supposed to or is there a way to configure the hard start?
The scan job is scheduled on the platform side. Once it hits 4a, the scan job would be created for a scanner to pick up but you have to wait for a scanner to pick up the job before it would start so there can be a delay. You can check the polling interval on your scanner appliances to see how often the appliances check in. Because of the way Qualys is architected (no inbound connectivity to scanners, scanners initiate all communication with the cloud), there is always some delay between starting a scan and when it actually starts.
Thank you Jordan
Retrieving data ...