WP End Of Life Policy | Imperva

Home > EOL policy 

Imperva products end-of-life policy

Imperva End-of-Life Support Policy

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:

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. An EOS announcement will be provided a minimum two years prior to the LTS release becoming 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. 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.

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.

 

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-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.

 

 

Imperva Software End-of-Life Schedule

App Sec affected

Imperva mobile app
WAF Gateway
WAF Management Server (MX)
WAF Management Server Manager (SOM)
WAF Gateway
WAF Management Server (MX)
WAF Management Server Manager (SOM)
WAF Gateway
WAF Management Server (MX)
WAF Management Server Manager (SOM)
WAF Gateway
WAF Management Server (MX)
WAF Management Server Manager (SOM)
WAF Gateway
WAF Management Server (MX)
WAF Management Server Manager (SOM)
WAF Gateway
WAF Management Server (MX)
WAF Management Server Manager (SOM)
WAF Gateway
WAF Management Server (MX)
WAF Management Server Manager (SOM)
WAF Gateway
WAF Management Server (MX)
WAF Management Server Manager (SOM)

Software version

4.6.x LTS
4.5.x
4.4.x LTS
4.3.x
4.2.x
4.1.x
4.0.x
3.14.x
Latest
V15.3
V15.2
V15.1
V15.0
V14.7-LTS
V14.6
V14.5
V14.4

End of support date

TBD
October 31, 2025
October 31, 2026
October 31, 2024
October 31, 2024
October 31, 2024
March 31, 2021
October 31, 2024
May 17, 2024
November 9, 2026
May 31,2026
March 2, 2026
August 31, 2025
February 12, 2026
April 30, 2024
February 05, 2024
June 30, 2023

Data Sec affected

Cloud Data Security (CDS)
DAM Management Server & Agent Gateway
DAM Management Server & Agent Gateway
DAM Management Server & Agent Gateway
DAM Management Server & Agent Gateway
DAM Management Server & Agent Gateway
DAM Management Server & Agent Gateway
DAM Management Server & Agent Gateway
DAM Agent
DAM Agent
DAM Agent
DSF Hub & Agentless Gateways (previously Sonar)
DSF Hub & Agentless Gateways (previously Sonar)
DSF Hub & Agentless Gateways (previously Sonar)
Data Risk Analytics (previously offered as CounterBreach)
Data Risk Analytics (previously offered as CounterBreach)
Data Risk Analytics (previously offered as CounterBreach)
Data Risk Analytics (previously offered as CounterBreach)
Imperva Data Masking

Software version

All versions
V14.11, V14.12, V14.13, V14.14, V14.15, V14.16
V14.9, V14.10
V14.8
V14.7 LTS
V14.6
V14.5
V14.4
V14.6, V14.8, V14.9
V14.5
V14.4
V4.10, V4.11, V4.12, V4.13, V4.14, V4.15, V4.16, V4.17
V4.3, V4.4, V4.5, V4.6, V4.8, V4.9
V4.2 and Below
V4.X
V3.X
V2.X.x
V1.X
All Versions

End of support date

October 15, 2024
TBD
March 29, 2025
June 30, 2024
TBD
September 30, 2023
June 30, 2023
March 31, 2023
TBD
October 30, 2025
November 30, 2024
TBD
September 28, 2024
June 10, 2023
TBD
October 24, 2023
May 31, 2021
June 13, 2018
January 15, 2023

SecureSphere affected

SecureSphere Web Application Firewall, Database Firewall, SharePoint Protection and the MX Management Server
SecureSphere Web Application Firewall, Database Firewall, and File Security Products, SharePoint Protection and the MX Management Server
SecureSphere File Security Products and SharePoint Protection
Imperva WAF Gateway
Imperva WAF Management Server
Imperva WAF Gateway
Imperva WAF Management Server
DAM
DAM

Software version

v13.x (v13.0 to v13.6)
Long Term Support only available for v13.6
v12.x (v12.0 to v12.6)
Extended Support only available for v12.6 (see technical bulletin)
All Versions
V14.3
V14.1, V14.2
V14.3
V14.1, V14.2

End of support date

End of Life: September 30, 2023
End of Long Term Support (relevant only for v13.6): March 31, 2024
FAM and SharePoint Protection: January 31, 2022
End of Life: Feb 05, 2021
End of Extended Support:
Feb 5, 2023
January 31, 2022
December 31, 2023
June 30, 2023
December 31, 2023
June 30, 2023

Imperva Hardware End-of-Life Schedule

Appliance

M180, X2030, X2530, X4530, X6530, X8530, 10K3
M170, X2520, X4520,X6520 X8520, 10K2
M120, X1020, X2020
M160, X2510, X4510, X6510, X8510, X10K
M110, X1010, X2010

LoD / EoS

N/A
May 1, 2024
December 31, 2021
July 06, 2020
October 25, 2017

EOSU

N/A
May 04, 2026*
December 31, 2024*
July 08, 2024*
N/A

EOSM

N/A
N/A
N/A
N/A
N/A

EOSL

N/A
April 30, 2029
December 31, 2026
July 6, 2025
October 25, 2022

Supported Software Matrix

N/A
v14(WAF/DAM), v15(WAF)
v14(WAF/DAM), v15(WAF)
v14(WAF/DAM), V15(WAF)
N/A

* Subjected to change based on the release date of the last supported version