Imperva Products Lifecycle Policy

Software

Life cycle milestone definitions:

• Release Cadence

  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.

• Versioning

  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.

• Patch types

  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.

• End of Life (EOL) and End of Support (EOS) Milestones

  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.

• Minor and Patch Version Cadence

  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.

• Long Term Support (LTS) Cadence

  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.

Hardware

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:

Milestone 1: Last Order Date (LoD)

• Last Order Date (LoD) defines the period during which customers may continue to purchase the generation of hardware appliances and its addons referenced in the LoD notification. LoD notification is provided to customers 90 days before the End Of Sale (EOS) date.

Milestone 2: End of Sale (EOS)

• This milestone marks the end of the availability for purchase of the hardware appliance and all related addons. After the EOS date, customers will no longer be able to purchase the hardware appliance or its addons.
• Imperva will continue to support a hardware appliance for sixty (60) months after its End of Sale Date.
• During that sixty (60) month period, repair services or replacement parts will be available for an Appliance pursuant to the applicable agreements.
• During that sixty (60) month period, all standard technical support services, including access to the Imperva Customer Support Portal, and to phone support, will be available to customers with existing Support Contracts.

Milestone 3: End of Software Update (EOSU)

• The EOSU milestone defines the last supported software and date for a specific hardware appliance. This final version will be specifically stated in the hardware end-of-life schedule on the Imperva website.
• The appliance will continue to support software versions released prior to the EOSU in accordance with the software end-of-life schedule.
• Between the End of Sale (EOS) and the EOSU, new software versions may be released.
• New features or software releases post-EOSU may require a hardware upgrade.
• After the EOSU, customers will continue to receive releases for the last supported software version.
• These releases will be provided in accordance with the software end-of-life schedule.

Milestone 4: End of Software Maintenance (EOSM)

• Occurs either 4 years after the Last Order Date or at the end of the support period for the latest version supported by the appliance, whichever comes first.
• Marks the end of maintenance support for the software, meaning no new patches or fixes will be released after this date.
• After EOSM, customers will still have access to basic support services. This includes assistance with usage, configuration, and troubleshooting based on the existing software and its last updates.

Milestone 5: End of Support Life (EOSL)

• This milestone marks the end of support life for the appliance.
• It is reached 5 years after EOS, and customers will no longer receive any support for the appliance after this milestone.

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.

Software

Release cadence:

• New major versions are introduced when significant changes occur (e.g., operating system or infrastructure changes, or a major new feature). Timing is driven by business and technical requirements rather than a fixed schedule.
• New minor versions will typically be introduced at a fixed cadence, which is semi-annually currently, but is subject to change.

Release milestones:

During its lifecycle, a release passes through the following milestones until it reaches its final EOS state.

Release Schedule and Support Time Frame

A minor version is designated either as a Feature Release (FR) or Long-Term Support (LTS) Release.

• Feature Release support:
  A minor version will be supported for two years from its release date before reaching EOS. Within this two-year period, a minor version will be in active support for the first 12 months, followed by a 12-month period of continued support.
• Long-Term Support (LTS) support:
  Once a minor release is declared LTS, it will be supported until a new LTS is available. LTS release cadence is expected to be between a 2–3-year time frame from the release of the last LTS. LTS release is designed to be very stable and therefore LTS patches contain only bug and security fixes and are released as needed. Customers are recommended to always patch their systems to the latest available LTS patch. These patches will be released until a new LTS is available (expected cadence is every 2-3 years from release of the last LTS). Continued support will be available for the next 12 months, after which, that LTS version will be EOS.
• Patch version support:
  Patches for both Feature and LTS releases are supported as long as the associated version is supported. Customers are recommended to always patch their systems to the latest available patch. Minor version patches will be EOS when the associated minor version is EOS.

The following table summarizes the EOS policy as detailed above:

*LTS release cadence is expected to be between a 2–3 year time frame from the release of the last LTS, unless technical reasons necessitate an earlier LTS release.

Release Support Time Frame Examples

Feature Release

DSF Hub/DRA/FAM v15.2.0.10 and DAM v15.2.1.10, the latest feature releases, were made available on November 12, 2025. These releases will be under active support until November 11, 2026. During this period, customers will receive bug fixes and security updates for any identified issues. From November 12, 2026, until November 11, 2027, these releases will be under continued support. During this time, customers will no longer receive fixes for any issues they encounter with this release. They will still be able to contact support for troubleshooting configuration issues. At the end of continued support, these releases will be End of Support (EOS) on November 11, 2027. After this date, customers will no longer be able to receive support for these feature releases.

LTS Release

DSF Hub v4.19, the latest LTS release, was designated as the LTS release on May 7, 2025. This release will be under active support until the next LTS release is available. While the timeline for the next LTS isn’t fixed, it should be at least until May 6, 2027, and could extend at the latest until May 6, 2028. During this period of active support, customers will receive bug fixes and security updates for any identified issues. One year from these dates, i.e., until May 6, 2028, at the earliest or May 6, 2029, at the latest, this release will be under continued support. During this time, customers will no longer receive fixes for any issues they encounter with this release. They will still be able to contact support for troubleshooting configuration issues. At the end of continued support, this release will be EOS on May 6, 2028, at the earliest or May 6, 2029, at the latest. After this date, customers will not be able to receive support for this LTS release.

DAM 14.19, the latest LTS release, was designated as the LTS release on March 24, 2025. This release will be under active support until the next LTS release is available. While the timeline for the next LTS isn’t fixed, it should be at least until March 23, 2027, and could extend at the latest until March 23, 2028. During this period of active support, customers will receive bug fixes and security updates for any identified issues. One year from these dates, i.e., until March 23, 2028, at the earliest or March 23, 2029, at the latest, this release will be under continued support. During this time, customers will no longer receive fixes for any issues they encounter with this release. They will still be able to contact support for troubleshooting configuration issues. At the end of continued support, this release will be EOS on March 23, 2028, at the earliest or March 23, 2029, at the latest. After this date, customers will not be able to receive support for this LTS release

Patch

The various patches for both the feature release 15.2.0.10 and LTS release 4.19.0.10 will follow the release support phases (active and continued) timelines as mentioned above. All patches for both these releases will be EOS along with the respective release EOS.

Frequently Asked Questions (FAQ)

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 or a major new feature. 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 first number is the major version, the second is the minor version, the third is a product identifier – 0 for Sonar/DSF Hub, DRA and 1 for DAM, and the last two digits are the patch identifier (e.g., 15.1.0.xx).

Q3: What is the support timeline for minor feature release versions?
A3: A minor version will be supported for two years from its release date before reaching EOS. For more details, refer to the support table above.

Q4: How does the Long-Term support cadence work?
A4: Once a minor release is declared LTS, it will be supported until a new LTS is available. LTS release cadence is expected to be between a 2–3-year time frame from the release of the last LTS. For more details, refer to the support table above.

Q5: What is the policy for End of Support for third-party products?
A5: 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.

Q6: Will new features be added to LTS Patch versions?
A6: No, new features will not be added to LTS Patch versions. These versions focus on stability and include only bug fixes and security patches. For using newer features, customers will be required to upgrade to a feature release.

Q7: How will users be informed about EOS dates?
A7: To avoid any issues due to potential missed communication, customers are required to follow this EOS policy document regarding EOS dates for all releases. For email EOS notifications Q1 2026 onwards, customers must subscribe to DSF notifications on the support portal.

Q8: Is there a regular patch cadence for LTS releases?
A8: No, there is not a regular patch cadence for LTS releases since they are designed for high stability. Patches will be released as needed and will be supported until the associated release is supported. Customers are recommended to always patch their systems to the latest available patch. For more details, refer to the support table above.

Q9: Where can I find the EOS policy for hardware?
A9: This document caters to the EOS for software. EOS policy for hardware can be found at the following link – https://www.imperva.com/support/eol-policy/

End of Support Policy for Third-Party Products

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.

Disclaimer

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-Support Policy. Imperva may continue offering Support services beyond the standard EOS date and reserves the right to charge additional fees for continuing Support services on any EOS 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.