



FortiOS 7.2 reached end of support on 30 September 2026. If any FortiGate in your estate still runs a 7.2.x build, the next vulnerability found in that branch will not get a fix for it. The advisory will simply tell you to move to a newer release.
Nothing dramatic happened on 1 October. Traffic kept flowing and dashboards stayed green. That quiet is why FortiOS 7.2 end of support slips down the list in so many Indian IT teams, sitting behind the ERP upgrade, the branch rollout and the audit observations from last quarter.
Our conversations about it with IT heads are rarely technical. They’re about budget, downtime windows and one awkward question: can the hardware you already own even run the next release?
The short answer: if the FortiGate is still inside its hardware support dates and appears on the supported-models list for FortiOS 7.4 or 7.6, upgrade in place this quarter. If the unit is near its own end of support or cannot run 7.4, budget a replacement now. Staying on 7.2 is a stopgap, never a plan.
Fortinet runs every FortiOS branch on a published lifecycle. According to Fortinet’s product life cycle note, a release gets 36 months of engineering support from its general availability date, followed by 18 months of “must fix” support, where only serious defects and security issues are addressed. FortiOS 7.2 became generally available at the end of March 2022, so the arithmetic lands on September 2026. FortiOS 7.0 went the same way a year earlier.
After that date there are no more 7.2 patch builds. A new PSIRT advisory affecting 7.2 will list fixed versions in 7.4 and 7.6 only. Expect Fortinet TAC to ask you to move to a supported build before it digs deep into a problem on 7.2, and expect your auditor to treat the version string as a finding on its own.
Here’s the part people forget. Edge firewalls are the devices attackers probe first, because they sit on the internet with an admin interface and a VPN portal attached. An unpatched build there is worse than one on an internal server.
The software date is only half the picture. Each FortiGate model has its own hardware lifecycle: an End of Order date when Fortinet stops selling it, a Last Service Extension Date when you can no longer extend the support contract, and a hardware End of Support date. The same Fortinet note says hardware support generally ends about 60 months after End of Order, and the last extension date sits 12 months before that.
So you can have three situations in one rack: a young unit that will happily run 7.6, a supported unit missing from the 7.4 and 7.6 model lists (7.2 was its last stop), and a unit already past its hardware support date, where the firmware question is moot.
If even one device already runs 7.4, look at it. Fortinet added hardware end-of-support warnings to the 7.4 GUI. Fabric devices past their date show in red under System > Firmware & Registration with the status “EOS – Unable to upgrade”, and the Security Rating report fails its End-of-Support check. That screen is a decent first pass at your replacement list.
For the full picture, build one sheet: model, serial number, current FortiOS build, site, HA role, FortiCare contract expiry, and the hardware dates from the support portal. FortiManager’s device list gives you the firmware column in a minute. Without it, someone logs in to each branch and runs get system status. Do it before anyone argues about budgets.
This is the right answer for most supported hardware, and cheaper than people expect: the cost is mostly engineering time and a maintenance window.
Our default is 7.4 for estates that value a mature, well-trodden build, and 7.6 where the model supports it and you want the longer runway. Per the lifecycle dates tracked on endoflife.date, 7.4 is supported until November 2028 and 7.6 until January 2030. FortiOS 8.0 arrived in April 2026; we’d let it mature through a few patch releases before it goes near a production perimeter. Jumping to the newest major release to “skip a cycle” is overrated. You’ll trade a known set of quirks for an unknown one.
Where it usually goes wrong is the branch with no local IT person, a single ISP link, and an upgrade scheduled for 11 pm with nobody on site to power-cycle the box. Stage those. Get an out-of-band path (a 4G modem on the console port is cheap) before you touch the firmware.
Replacement is the honest answer when the model can’t run 7.4, when it’s past the last service extension date, or when it’s already struggling. That last one is common. A firewall sized five years ago for plain routing and basic IPS often runs hot once SSL inspection is turned on for the traffic that matters, and a new major release won’t make it lighter.
Indian procurement timelines are the real constraint here. Between budget approval, three quotes, a purchase order and delivery, a quarter can disappear. If you’re a PSU or buying through GeM, add more. That’s why we’d open the replacement conversation now, while you still have options on timing, rather than in February when the financial year is closing.
Migration itself is manageable. Configs convert to newer models with Fortinet’s own tooling, but interface names and VDOM layouts change between models, so treat the converted config as a draft. Our firewall migration team spends more time on the policy clean-up than on the conversion. A replacement is the cheapest moment you’ll ever get to delete those 200 rules nobody can explain.
Sometimes the replacement is on a truck and the plant can’t take downtime until the next shutdown. Fine. Run 7.2 for a short, defined period and shrink the exposure meanwhile.
Our guide to FortiGate NGFW hardening covers these controls in more depth. Then write a one-page risk acceptance: which devices, why, the compensating controls, the end date, and a signature from the CIO or CISO. The failure we see is a risk acceptance with no end date, re-signed at every audit until it becomes the architecture.
| Factor | Upgrade in place | Replace hardware | Stay on 7.2 (short term) |
|---|---|---|---|
| Upfront cost | Engineering time and a window | Hardware, licences, migration effort | Low now, higher later |
| Downtime | Short window per site | Planned cutover per site | None |
| Security exposure after | Back on a fixed branch | Supported hardware and software | Unpatched branch, partly offset by controls |
| Time to complete | Days to weeks | Weeks to a quarter | Only until the agreed end date |
| Audit position | Clean | Clean | Documented exception at best |
| Fits when | Model is on the 7.4 or 7.6 list and within hardware support | Model is dropped, past extension date, or undersized | Replacement is ordered and a shutdown window is booked |
One budgeting note: before buying new subscriptions, check what’s left on the old unit’s FortiCare and FortiGuard bundle, and align the new term with your financial year. The FortiGate licence renewal conversation is a lot easier when it isn’t happening in a hurry.
In a multi-site Indian estate, the hard part of an end-of-support cycle is rarely the upgrade command. It’s knowing what you have, and confirming nothing broke afterwards, across firewalls, switches and WAN links from more than one vendor. That’s the problem PrahiX Ora is built for. It’s a unified SecOps platform built by PrahiX Tech Pvt Ltd, and the platform we deploy and operate for clients as its primary field deployment and operations partner.
The NMS pillar does most of the work here. It gives the NOC one observability view across firewalls, switches, access points and WAN or SD-WAN links, and builds topology from LLDP and CDP discovery, so the branch box nobody remembered shows up on the map. Network path tracing lets the team confirm that traffic is taking the expected route after a cutover. ML-based anomaly detection flags a link or device that behaves differently after the change, and auto-healing policies handle the routine fixes.
Three other pillars cover the rest of the window. The SIEM ingests logs from many sources with correlation rules mapped to MITRE ATT&CK, reconstructs attack storylines as a graph, and keeps data in hot, cold and archive tiers. That continuity matters when CERT-In’s direction expects 180 days of logs kept in India, and a firewall swap shouldn’t leave a gap. SOAR playbooks with pre-built connectors can push blocklists to FortiGate automatically, which buys time on a 7.2 unit awaiting replacement and makes CERT-In’s 6-hour reporting window more realistic. For plants and retail chains, video surveillance (VMS) brings ONVIF, Hikvision and Dahua cameras, with video analytics, into the same operations view as the network.
If you want to see how that would map to your own sites, our team can walk you through it.
No. The firewall keeps forwarding traffic and enforcing policy. What ends is the supply of fixes for that branch, so every new vulnerability disclosed for 7.2 stays open on your device. Treat the date as the start of a growing exposure, not a switch-off.
Sometimes, but the supported route depends on your exact build and model, and it often passes through intermediate releases. Use Fortinet’s upgrade path tool rather than guessing. Before you commit to 7.6, check it’s on the supported-models list for your hardware, and check that every feature you depend on still exists in the same form there.
No. A FortiCare contract covers the hardware and entitles you to firmware and TAC support, but it doesn’t extend the life of a software branch. Outside specific long-term support arrangements Fortinet announces for particular builds, the renewal gives you access to the newer releases you’re expected to move to, not more 7.2 fixes.
Most frameworks don’t name firmware versions, but they do expect technical vulnerability management. ISO 27001:2022 has a specific control for it, and RBI, SEBI and IRDAI inspections routinely ask how unsupported software is handled. A documented, time-bound exception will usually be accepted for a short period. An undocumented one tends to become an observation. Check the exact wording with your auditor.
Before anyone debates budget or downtime, get the list: every FortiGate, its model, its current build and its hardware support dates, in one sheet. That document decides which units upgrade, which get replaced, and which need a signed exception.
If you’d like a second pair of hands, our engineers handle FortiOS upgrades and FortiGate replacements with 24×7 monitoring across head offices and branch networks. Share your device list and we’ll come back with a site-by-site recommendation.