Imperva takes great care in helping customers deploy Imperva products as effectively and efficiently as possible, continuously enhancing them with new features and technologies which protect against the latest threats. To assist our customers, Imperva has established an End-of-Life Policy for all Imperva customer managed software and hardware products to deal with new software releases that are launched on a regular basis.
After a certain period of time, a major architectural change might be required, in which case, Imperva will announce the End-Of-Life (EOL) of the existing product, and might introduce a successor product. To help customers efficiently manage product EOL-transitions, Imperva will announce the dates for the End-of-Life and Last Order Date (for hardware) along with the available migration path according to the table below. Imperva aims to maintain its products in line with the statements given herein. However, due to the ever-increasing pace of cybersecurity and evolution of technology, Imperva might not always be able to follow it.
During its lifecycle a product will pass through the following milestones until it reaches its final End-of-Life state:
New major version releases will be introduced when significant changes occur, such as operating system changes or infrastructure changes. The introduction of major versions is not tied to a specific timeline
but rather to the requirements and changes in the software.
The major version is the first number in the release format. The minor version is denoted by the second digit, and the patch release is denoted by the last digits.A new major or minor version might have new
features, as well as bug fixes. A new patch release typically includes bug fixes. For example, 14.2.0.xx ⇐ xx is the patch identifier.
Public Patches, including new functionalities alongside bug and vulnerability fixes, are thoroughly tested before release, and users are recommended to install them on an ongoing basis for software security
and functionality. When a critical vulnerability or significant software issue is found, a Critical Patch based on the latest public patch version is released and specifically tested for the scope of the
discovered issue, with immediate installation recommended to ensure system integrity. Private Patches, or Debug Patches, are customized for specific issues, acting as temporary solutions or for debugging until a
permanent fix is available in a Public Patch. These patches are essential for addressing particular problems and should be installed as advised.
EOL is the period during which a release enters a limited support phase before reaching EOS. The minimum EOL period will be 1 year. During limited support, the release will not be available for download, and
private patches will be provided based on the latest available minor release or the most recent patch version. EOS marks the point at which no support of any kind will be provided.
A minor version release will receive support for at least one year from its release date. After this period, it enters the End of Life (EOL) phase, followed by End of Support (EOS). Software updates may be
issued for the latest minor version. The End of Life or End of Support dates will be communicated through our website. Once EOL is announced, the software will be removed and will no longer be available for
download.
Once a minor release is declared LTS, it will enter an LTS cadence which is different from the standard minor version cadence. An LTS release will be supported for a minimum of two years prior to entering
the End of Life (EOL) phase, followed by End of Support (EOS). During the lifecycle of a major version, there will be at least one LTS release. Patch versions released as part of LTS release will include bug
fixes and security patches. New features will not be added to an LTS Patch version. LTS patches will be released as needed. LTS release is designed to be very stable, so there may not be a need for a regular
patch cadence. An EOS announcement will be provided a minimum two years prior to the LTS release becoming EOS.
Q1: What is the release cadence for new major versions?
A1: New major versions are released in response to significant changes, like operating system or infrastructure updates. The timing isn’t fixed but depends on the software’s evolving requirements and changes.
Q2: How does versioning work in this policy?
A2: The version format consists of major, minor, and patch numbers. Major versions (first number) and minor versions (second Number) may introduce new features and bug fixes. Patch releases (last Number) typically include bug fixes.
Q3: What is the End of Life (EOL) and End of Support (EOS) policy?
A3: EOL is a phase where a release receives limited support before reaching EOS. The minimum EOL period is 1 year. During this, the release won’t be available for download, and private patches will be based on the latest minor or patch release. EOS marks the end of all support.
Q4: What is the support timeline for minor and patch versions?
A4: Minor versions are supported for at least one year from release. After this, they enter EOL, then EOS. Updates may be issued for the latest minor version. EOL or EOS dates are communicated via our website. Once EOL is announced, the software is removed from download.
Q5: How does the Long Term Support (LTS) cadence work?
A5: LTS releases are supported for a minimum of two years before EOL, followed by EOS. During a major version’s lifecycle, there’s at least one LTS release. LTS patches, released as needed, include bug fixes and security patches without new features. EOS announcements for LTS releases are made at least two years in advance.
Q6: What is the policy for End of Support for Third-Party Products?
A6: Imperva products, compatible with various databases and operating systems, follow the third-party end-of-support dates. Post these dates, while Imperva software may continue to operate with unsupported third-party products, there will be no error corrections, bug fixes, agent upgrades, updates, or new feature development for operation with these third-party products.
Q7: Will new features be added to LTS Patch versions?
A7: No, new features will not be added to LTS Patch versions. These versions focus on stability and include only bug fixes and security patches.
Q8: How will users be informed about EOL or EOS dates?
A8: EOL and EOS dates will be communicated through our website, ensuring users are informed in advance about the support status of their software versions.
Q9: Is there a regular patch cadence for LTS releases?
A9: No, there is not a regular patch cadence for LTS releases since they are designed for high stability. Patches will be released as needed.
Imperva hardware appliance models reach end of product life due to market requirements, technological innovations, or replacement by products with new, more advanced technology. Imperva reserves the right to revise the policy at any time and customers are requested to stay updated with the latest policy published in the Imperva customer support guide.
To ensure a smooth migration to new Imperva hardware platforms, Imperva will continue to support hardware based on the stated end of life milestone of sixty (60) months after the announced End of Sale date.
Accordingly, the EOL policy for Appliances is:
Note: The duration and specific milestones mentioned in this policy may be subject to change at the discretion of the vendor. It is recommended that customers regularly review Imperva customer support guide for any updates or changes to the End of Life policy for their hardware appliance.
Imperva products are designed for use with multiple databases, operating systems and other third-party products, up to their respective end-of-support dates as identified by the third-party vendor. Although Imperva products may continue to function with the unsupported product of the third-party vendor, Imperva will not be able to provide support for that third-party product, even if that third-party vendor offers extended support. Please contact your vendor representative to confirm the end-of-support dates for that vendor’s respective third-party products.
Only customers with Imperva products that are currently covered by a valid Support contract are entitled to the benefits set forth by the End-of-Life Policy. Imperva may continue offering Support services beyond the standard EOL date and reserves the right to charge additional fees for continuing Support services on any EOL products. Imperva reserves the right to reduce or amend Support services offerings available for renewal under this policy at any time in its sole discretion, with or without notice.
* Subjected to change based on the release date of the last supported version