Our release notes provide information on changes and enhancements in each release.

Note: Unless otherwise specified, the changes described here are rolled out throughout the week and may not be immediately available in all accounts.

In this release:

DDoS Protection for Networks: Self-service add network range

As part of the ongoing move toward self-service configuration, you can now add a network range via the Cloud Security Console. Previously, this was performed only by Imperva.

This new capability joins the existing self-service configuration of GRE tunnel connections and flow exporters.

What changed: This feature was previously provided on the basis of Early Availability, and required you to contact Imperva Support to enable it for your account. It is now enabled by default for all accounts subscribed to the DDoS Protection for Networks service. After you are onboarded to the service, you can add additional ranges to Imperva independently.

Where it’s located: In the Cloud Security Console, navigate to Network > Network Protection > Protection Settings > Add range.

After adding the range, you can track its onboarding status in the Cloud Security Console. As each validation step is completed, the status is updated and a notification email is sent.

For more details on this feature, see Add a Network Range.

New usage management service

In this release, we are starting to migrate customer accounts to the new usage management service.

Benefits:

  • Usage Report: An enhanced Usage Report allows better tracking of service usage, including upgrades and product trials.

  • Usage API (v3): The new Usage API (v3) enables improved tracking of previous usage periods, where API requests are based on monthly usage records and not on user-specified start and end dates.

  • Subscription details: A newly designed Subscription page more clearly displays your licensed services.

  • Advanced Bot Protection usage and overages are displayed in the Usage Report and included as part of the monthly usage summary.

What to expect:

  • The migration is expected to be seamless, and no action is required on your part.

  • Detailed usage data (drill down into 5 minute buckets) will now be available for a period of 155 days, as opposed to the current 365 days. However, data for Cloud WAF throughput rates for the full 365 days will be available using the v1 API until April 2024, when data retention will be limited to 155 days.

Rollout plan:

  • The migration is expected to continue through March. If you would like the new service enabled for your account at an earlier date without waiting for the rollout, contact your account manager or Imperva Support to make the request.

  • This migration applies to direct customers only. Details for partners and their end-user accounts will be communicated separately.

For more information, see the documentation:

Change in CNAME for onboarding websites to Imperva

When onboarding a website to Imperva, you are given a CNAME that is used to point your website traffic to the Imperva network.

The domain used for this purpose was recently changed from impervadns.net to ng.impervadns.net. Websites onboarded after this change was implemented are provided with a CNAME from the new domain.

Note that the structure of the domain used for CNAMEs is subject to change, and should not be relied on for automation purposes.

For details on DNS settings for your website, see Website General Settings.

Recently mitigated CVEs

Mitigation for new Common Vulnerabilities and Exposures (CVEs) is added weekly by Imperva Research Labs.

To view the latest CVEs for which coverage was added, see Recently Mitigated CVEs.

 

 

More about the release notes

  • Tip: Open the latest release notes directly from the Cloud Security Console's Help menu.

  • Subscribe: Choose one of these options to subscribe to updates about weekly releases: