Vulnerability Response -- scan on resolved
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2023 11:14 AM
Is anyone using the scan_on_resolved integration instance parameter also running into concurrency errors in Qualys due to too may scan requests when vulnerable items are moved into a Resolved state?
Can this functionality be customized, so that if the discovered item related to the vulnerable item has a tag of 'Qualys Agent' the scan is not initialized? We use both Qualys agents as well as IP based scans, and are seeing lots of concurrency errors coming from Qualys due to ServiceNow initializing the scan request in Qualys.
We would rather the system not send the scan if the CI has the Qualys agent installed.
Any help or guidance on this issue is greatly appreaciated.