Ivanti Policy Secure End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Ivanti Policy Secure versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 9.1 | 9.1 | May 13, 2019 | Dec 31, 2024 | 610 days past EOL | EOL |
| 22.3 | 22.3 | Dec 12, 2022 | Nov 30, 2024 | 641 days past EOL | EOL |
| 22.4 | 22.4 | Apr 17, 2023 | Dec 31, 2024 | 610 days past EOL | EOL |
| 22.5 | 22.5 | Jul 17, 2023 | Dec 31, 2024 | 610 days past EOL | EOL |
| 22.6 | 22.6 | Oct 17, 2023 | Dec 31, 2024 | 610 days past EOL | EOL |
| 22.7 | 22.7 | May 21, 2024 | Jan 31, 2027 | 151 days remaining | Warning |
| 25.1.2 | 25.1.2 | Jul 31, 2026 | Apr 30, 2027 | 240 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/ivanti-policy-secure)
Ivanti Policy Secure lifecycle status — the real story
Ivanti Policy Secure (formerly Pulse Policy Secure) is the network-access-control companion to Ivanti Connect Secure — CISA’s KEV catalog files the 2024–2025 exploitation-wave CVEs against “Connect Secure and Policy Secure” jointly, so its lifecycle dates carry the same operational weight even though Ivanti notes the product is not intended to be internet-facing.
Per Ivanti’s EOL Timelines and Support Matrix: the 22.3–22.6 releases and the classic 9.1x line all reached End of Support by December 31, 2024; IPS 22.7 reaches End of Support on January 31, 2027 — the same date as Connect Secure 22.7/22.8, days before CISA BOD 26-02’s twelve-month decommission deadline — and 25.1.2 runs to April 30, 2027 (on new ISA hardware only). Ivanti’s matrix publishes Launch and End of Support dates for Policy Secure (no separate End of Engineering column).
The 9.1x classic line carries Ivanti’s standing declaration: “This product is now End of Life and there is no longer any development on that platform.”
Ivanti Policy Secure release and support pattern
Across the 7 release lines with a published release date, Ivanti Policy Secure has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 1.7 years from its release to its end-of-life date.
Of the 7 release lines tracked, 5 are past end of life and 2 are still within support. The newest line, 25.1.2, was released July 31, 2026. The next scheduled end of life is 22.7 on January 31, 2027 — 151 days from this build. The longest-supported line currently published is 25.1.2, to April 30, 2027.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Ivanti Policy Secure security intelligence
CISA KEV history: Ivanti Policy Secure is named in CISA's Known Exploited Vulnerabilities catalog 6 times, most recently on 2025-04-04, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does Ivanti Policy Secure end of life mean for your organization?
When a version of Ivanti Policy Secure reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Ivanti Policy Secure should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Ivanti Policy Secure reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Ivanti Policy Secure versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Ivanti Policy Secure has 5 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Ivanti Policy Secure is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."