Cisco Identity Services Engine End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Cisco Identity Services Engine versions. Dates read at the vendor's own lifecycle pages (cisco.com). Updated at every deploy.
Cisco Identity Services Engine 3.1 is supported until November 3, 2026, its end-of-support date. Active support for Cisco Identity Services Engine 3.1 ended on November 3, 2025; security fixes continue until that end-of-life date. The next Cisco Identity Services Engine version to reach end of life is 3.2, on November 3, 2026. 13 of 18 tracked Cisco Identity Services Engine versions are past end of life; the most recent to reach it, 3.0, did so on July 13, 2024. The full Cisco Identity Services Engine lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.0 | 1.0 | — | Apr 6, 2015 | 4223 days past EOL | EOL |
| 1.1 | 1.1 | — | Apr 6, 2015 | 4223 days past EOL | EOL |
| 1.2 | 1.2 | — | May 31, 2017 | 3437 days past EOL | EOL |
| 1.3 | 1.3 | — | Dec 31, 2017 | 3223 days past EOL | EOL |
| 1.4 | 1.4 | — | Sep 30, 2018 | 2950 days past EOL | EOL |
| 2.0 | 2.0 | — | Mar 17, 2020 | 2416 days past EOL | EOL |
| 2.1 | 2.1 | — | Sep 17, 2019 | 2598 days past EOL | EOL |
| 2.2 | 2.2 | — | Jun 8, 2021 | 1968 days past EOL | EOL |
| 2.3 | 2.3 | — | Dec 17, 2019 | 2507 days past EOL | EOL |
| 2.4 | 2.4 | — | Dec 26, 2021 | 1767 days past EOL | EOL |
| 2.6 | 2.6 | — | Jan 31, 2023 | 1366 days past EOL | EOL |
| 2.7 | 2.7 | — | Sep 22, 2023 | 1132 days past EOL | EOL |
| 3.0 | 3.0 | — | Jul 13, 2024 | 837 days past EOL | EOL |
| 3.1 | 3.1 | — | Nov 3, 2026 | 6 days remaining | Warning |
| 3.2 | 3.2 | — | Nov 3, 2026 | 6 days remaining | Warning |
| 3.3 | 3.3 | — | TBD | Supported | Active |
| 3.4 | 3.4 | — | TBD | Supported | Active |
| 3.5 | 3.5 | — | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/cisco-ise)
Cisco Identity Services Engine lifecycle status — the real story
Cisco Identity Services Engine (ISE) software per release, from Cisco's per-release End-of-Life bulletins (15 bulletins from the ISE EoS/EoL notice listing, read 2026-09-09 through a fetch proxy because cisco.com bot-blocks plain requests). ISE bulletins phase support differently from the ASA/FTD ones: routine maintenance ends first (after which Cisco publishes only severity-1 and security-vulnerability fixes), then software maintenance releases end altogether, then support ends. Mapping: support = the end of routine maintenance (security-only from then), eol = the end of software maintenance releases (the last day any fix ships), extendedSupport = the end of support. Where a bulletin has no security-only phase (1.2, 1.1, 1.0) support mirrors eol. Where a bulletin prints no end-of-support date, extendedSupport is false rather than an inferred date: the 1.3 bulletin says only that software maintenance for 1.3 and 1.3.X ends December 31, 2017 (sev1 and security fixes only from December 31, 2016), and the 1.1 and 1.0 bulletins say software maintenance ends April 6, 2015 and that Software Application Support contracts cannot be purchased or renewed after April 30, 2015. Until 2026-10-09 those three rows carried an extendedSupport date that Cisco never printed. End-of-Sale and the announcement date are carried where stated. Releases 3.3, 3.4 and 3.5 have release notes but no bulletin yet and are listed as current with no dates; release dates are not stated in the bulletins and are left null.
As read: 3.1 and 3.2 share one bulletin, re-read direct from cisco.com on 2026-09-09 and corrected. It does carry a security-only phase: Software Maintenance 2025-11-03, from which Cisco publishes only critical security vulnerability and severity-1 fixes, then End of SW Maintenance Releases 2026-11-03, then Last Date of Support 2027-11-30, with ISE 3.1 P10 and 3.2 P8 named as the last maintenance patches. The first read (through a fetch proxy) missed the Software Maintenance row, mapped the end of maintenance releases to support and left eol null, which is neither this file's mapping nor a value the API bundle accepts. End-of-Sale is the bulletin's stated last order date, 2026-11-03. 3.0 ended maintenance releases 2024-07-13 and support 2025-07-13. Hardware appliance bulletins (Secure Network Server 3xx5 series) are not modelled here.
KEV context (CISA catalog 2026.09.08): CVE-2025-20281 and CVE-2025-20337 under 'Identity Services Engine' (both added 2025-07-28), matched on the display name. No version scoping is asserted here.
Verification: cisco.com answers 403 to a bare User-Agent but serves these bulletins to a full browser header set, with no Cisco account and no Support API access — that is how 3.1/3.2 and 3.0 were re-read on 2026-09-09. Each line links its own bulletin and the notice listing is the index to re-read.
Cisco Identity Services Engine release and support pattern
Of the 18 release lines tracked, 13 are past end of life and 5 are still within support. The next scheduled end of life is 3.2 on November 3, 2026 — 6 days from this build. The longest-supported line currently published is 3.1, to November 3, 2026. Upstream also publishes an extended-support phase for 12 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Cisco Identity Services Engine security intelligence
CISA KEV history: Cisco Identity Services Engine is named in CISA's Known Exploited Vulnerabilities catalog 3 times, most recently on 2026-09-16. Derived from CISA's live catalog at every build.
What does Cisco Identity Services Engine end of life mean for your organization?
When a version of Cisco Identity Services Engine 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Cisco Identity Services Engine 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 Cisco Identity Services Engine 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 |
| Commercial extended support | Not available for Cisco Identity Services Engine from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →