Custom Import Frequency Settings for Scanner Integrations

Summary

To address the challenges posed by Qualys' API rate limits currently, we have introduced a feature that allows partners and end clients to customize the frequency of auto-import checks. This feature is designed to optimize API usage and prevent exceeding the restrictive API limits set by Qualys, thereby enhancing integration efficiency.

Currently by default, all connected scanners are polled every 30 mins for new scan imports.

Key Enhancements

  1. Customizable Import Frequencies:

  1. New Scanner Management Page:

  1. Default and Individual Importer Settings:

User Stories

Platform Partners Utilizing Qualys: As a platform partner, I want to set a default import frequency for my clients that optimizes API usage, ensuring efficient operations without hitting API rate limits.

End-User Employing Qualys for Vulnerability Data Imports: As an end-user, I need to adjust the polling frequency to once or twice a day to stay within the entry-level API limits.

How to Use

  1. Access the Scanner Management Page:

image-20240712-111818.png

Only scanners set up by users with the Staff Role will be visible in this view, displaying exclusively 'Staff' scanners. This ensures the protection of clients who use their own scanners to import vulnerability data not managed by the partner.

  1. Set Default Import Frequency:

image-20240712-111642.png

  1. Customize Individual Importer Settings:

Enhancing Integration Flexibility

This feature significantly enhances the flexibility of our scanner integrations by allowing users to tailor the frequency of imports. By enabling efficient management of API utilization, we help ensure that our clients can maintain optimal operation of their vulnerability management processes without exceeding API limits. This also provides protection for any existing scanning providers that may impose these API restrictions.

Implement these settings today to optimize your scanner integrations and ensure efficient, uninterrupted operations.

Example: How the API Polling Works in Practice

When you create and save a new auto-import scanner for a client’s project and select an API import frequency that differs from the default (30 minutes), the polling mechanism functions as follows:

This behavior ensures that a newly created auto-import scanner quickly establishes a baseline of successful operation, after which it follows your custom polling interval to prevent exceeding any restrictive API limits.