Tenable.io API Rate Limit Enforcement Notice To ensure a...
Tenable.io API Rate Limit Enforcement Notice To ensure a great experience for all our customers, Tenable will introduce request rate limits to all our REST API endpoints that communicate with the Tenable.io platform. These changes will ensure over extensive API calls from one customer won't have any impact on the overall experience of others. Tenable.io will calculate the number of API calls it accepts from a single user per minute based on current processing load. Individual users are identified by the API key used in each request. If you send a request after the processing limit is reached, Tenable.io returns an HTTP response message with a 429 (Too Many Requests) code and a Retry-After header element that specifies the number of seconds to wait before retrying. The new limits will go in the effect on Wednesday, November 14th, 2018. We strongly encourage customers who use the REST API to modify their code to be able to handle these new sets of restrictions gracefully. Customers using the tenbale.io SDK or PyTenable don’t need to take further actions. Customers not using either library need to handle rate limits in their code. In python, for example, this can be done as follows: import requests from requests.packages.urllib3.util.retry import Retry retries = Retry( total=3, status_forcelist=[429, 501, 502, 503, 504], backoff_factor=1, respect_retry_after_header=True ) adapter = requests.adapters.HTTPAdapter(max_retries=retries) session = requests.Session() session.mount('https://', adapter) Please refer to our documentation for more details at https://cloud.tenable.com/api#/ratelimiting For more information, please contact support@tenable.com or log a Case.Tenable.io will undergo infrastructure upgrades to improve...
Tenable.io will undergo infrastructure upgrades to improve site performance and reliability throughout September. This planned maintenance window is scheduled to take no more than 4 hours to perform. If you have questions regarding the specific timing of the maintenance period, that affects you and you have not already received an email, please email your Customer Success Manager or create a Case with Tenable Customer Support or email support@tenable.com. This maintenance window only affects Tenable.io cloud and SecurityCenter customers who use Tenable.io to perform scans. During this time: Your Tenable.io URL will redirect you to a maintenance page, and you will not be able to access your Tenable.io account at https://cloud.tenable.com/. The Tenable.io API will be unavailable during this time. We expect most scans that are already running when the maintenance window begins to complete successfully after the window closes. We recommend that you verify this. Scans scheduled to start during the maintenance window are not likely to be initiated. Please check if they have run and if not, consider either scanning manually or at your next scheduled time. Agents will not be able to check into the Tenable.io platform during this time. Once services resume, agents will retain their data until the next check in. SecurityCenter management consoles with a Tenable.io scanner in their configuration will begin producing log messages indicating SecurityCenter cannot connect to the scanner. This will not impact SecurityCenter performance or stability, and the log messages will stop once the maintenance window is complete. This maintenance window does not affect Tenable.io on-prem, Nessus Home, Nessus Professional, Nessus Manager deployments or SecurityCenter consoles without a Tenable.io scanner. Please understand that routine maintenance and upgrades are a necessary part of our service delivery to you and we make every effort to perform these at the least disruptive times. We apologize for any inconvenience this planned maintenance outage may cause. We will do our absolute best to perform these upgrades as fast as possible and with minimal impact.