{"id":2273,"date":"2026-03-23T16:17:27","date_gmt":"2026-03-23T15:17:27","guid":{"rendered":"https:\/\/extendsclass.com\/blog\/?p=2273"},"modified":"2026-03-23T16:11:37","modified_gmt":"2026-03-23T14:11:37","slug":"fortigate-eol-what-it-means-which-models-are-affected-and-what-to-do-next","status":"publish","type":"post","link":"https:\/\/extendsclass.com\/blog\/fortigate-eol-what-it-means-which-models-are-affected-and-what-to-do-next","title":{"rendered":"FortiGate EOL: What it means, which models are affected, and what to do next\u00a0"},"content":{"rendered":"\n<p>Your&nbsp;firewall&nbsp;is the first line of defense between your network and the internet. But what happens when that&nbsp;firewall&nbsp;stops receiving security patches? For thousands of organizations running older FortiGate hardware, this is not a hypothetical \u2014 it is the current reality. In early 2025, a threat actor known as \u201cBelsen Group\u201d published stolen configuration data from approximately 15,000 FortiGate devices on the dark web, exposing IP addresses, credentials, and&nbsp;firewall&nbsp;rules. The source: unpatched vulnerabilities on devices that, in many cases, had already reached&nbsp;end&nbsp;of life. Understanding the FortiGate end-of-life lifecycle is not a procurement concern \u2014 it is a security imperative.&nbsp;<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_47_1 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"ez-toc-toggle-icon-1\"><label for=\"item-69df0cf4dd8be\" aria-label=\"Table of Content\"><span style=\"display: flex;align-items: center;width: 35px;height: 30px;justify-content: center;direction:ltr;\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/label><input  type=\"checkbox\" id=\"item-69df0cf4dd8be\"><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/extendsclass.com\/blog\/fortigate-eol-what-it-means-which-models-are-affected-and-what-to-do-next\/#What_FortiGate_EOL_actually_means\" title=\"What FortiGate EOL actually means\u00a0\">What FortiGate EOL actually means\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/extendsclass.com\/blog\/fortigate-eol-what-it-means-which-models-are-affected-and-what-to-do-next\/#Which_FortiGate_models_are_reaching_EOL\" title=\"Which FortiGate models are reaching EOL\u00a0\">Which FortiGate models are reaching EOL\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/extendsclass.com\/blog\/fortigate-eol-what-it-means-which-models-are-affected-and-what-to-do-next\/#Security_risks_of_running_EOL_FortiGate_hardware\" title=\"Security risks of running EOL FortiGate hardware\u00a0\">Security risks of running EOL FortiGate hardware\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/extendsclass.com\/blog\/fortigate-eol-what-it-means-which-models-are-affected-and-what-to-do-next\/#Planning_your_FortiGate_EOL_migration\" title=\"Planning your FortiGate EOL migration\u00a0\">Planning your FortiGate EOL migration\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/extendsclass.com\/blog\/fortigate-eol-what-it-means-which-models-are-affected-and-what-to-do-next\/#Conclusion\" title=\"Conclusion&nbsp;\">Conclusion&nbsp;<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_FortiGate_EOL_actually_means\"><\/span><strong>What FortiGate EOL actually means<\/strong>\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Fortinet uses a structured lifecycle framework with several distinct&nbsp;milestones, and&nbsp;conflating them is a common and costly mistake. Each milestone has different operational implications:&nbsp;<\/p>\n\n\n\n<ul>\n<li><strong>End of Order (EOO)<\/strong>&nbsp;is the last date a FortiGate model can be&nbsp;purchased&nbsp;as new hardware. Fortinet provides a minimum of 90 days advance notice before EOO. Once this date passes, the product is no longer commercially available, but existing units continue to receive support.&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li><strong>Last&nbsp;Service Extension Date (LSED)<\/strong>&nbsp;is&nbsp;perhaps the&nbsp;most overlooked milestone. It is the final deadline to renew or&nbsp;purchase&nbsp;support contract extensions for a discontinued product \u2014 occurring 12 months before the End of Support date. Once LSED passes, organizations can no longer extend contracts at any price, even if the device still has a year of official support&nbsp;remaining. Missing LSED locks organizations out of support for the remaining lifecycle period.&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li><strong>End of Engineering Support (EOES)<\/strong>&nbsp;applies primarily to&nbsp;FortiOS&nbsp;software versions. After EOES, Fortinet stops developing new features and fixing regular bugs. The software enters a \u201cmust-fix\u201d phase in which only critical PSIRT security vulnerabilities receive patches, for an&nbsp;additional&nbsp;18 months. EOES typically occurs 36 months after the software\u2019s General Availability (GA) date.&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li><strong>End of Support (EOS)<\/strong>&nbsp;is the final milestone. After EOS, Fortinet provides no support of any kind: no TAC tickets, no RMA hardware replacements, no bug fixes, no security patches. For hardware, EOS typically&nbsp;occurs&nbsp;60 months (five years) after EOO. For&nbsp;FortiOS&nbsp;software, EOS occurs approximately 54 months after GA.&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li><strong>EOSL (End of Service Life)<\/strong>&nbsp;is terminology used by third-party vendors to describe the combined hardware and software end of all support \u2014 effectively equivalent to Fortinet\u2019s EOS milestone.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>For a&nbsp;consolidated&nbsp;reference on tracking these dates across affected models,&nbsp;<a href=\"https:\/\/aseva.com\/fortinet-eol\" target=\"_blank\" rel=\"noreferrer noopener\">Forti<\/a><a href=\"https:\/\/aseva.com\/fortinet-eol\" target=\"_blank\" rel=\"noreferrer noopener\">G<\/a><a href=\"https:\/\/aseva.com\/fortinet-eol\" target=\"_blank\" rel=\"noreferrer noopener\">ate EOL<\/a>&nbsp;resources can help organizations map their inventory against official Fortinet lifecycle milestones.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"560\" height=\"313\" src=\"https:\/\/extendsclass.com\/blog\/wp-content\/uploads\/2026\/03\/image-1.png\" alt=\"\" class=\"wp-image-2283\" srcset=\"https:\/\/extendsclass.com\/blog\/wp-content\/uploads\/2026\/03\/image-1.png 560w, https:\/\/extendsclass.com\/blog\/wp-content\/uploads\/2026\/03\/image-1-300x168.png 300w\" sizes=\"(max-width: 560px) 100vw, 560px\" \/><\/figure>\n\n\n\n<p><em>FortiGate EOL Lifecycle Timeline<\/em>\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Which_FortiGate_models_are_reaching_EOL\"><\/span><strong>Which FortiGate models are reaching EOL<\/strong>\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The D-series and E-series hardware families are currently at the center of the EOL wave affecting enterprise networks.&nbsp;<\/p>\n\n\n\n<p><strong>D-series models already past EOS:<\/strong>&nbsp;<\/p>\n\n\n\n<ul>\n<li>FortiGate-60D: EOS September 23, 2023&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>FortiGate-80D: EOS April 16, 2023&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>FortiGate-90D: EOS October 14, 2023&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>FortiGate-300D: EOS October 11, 2023&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>FortiGate-140E and FortiGate-91E: EOS reached in 2024&nbsp;<\/li>\n<\/ul>\n\n\n\n<p><strong>E-series and other models with recent or upcoming milestones:<\/strong>&nbsp;<\/p>\n\n\n\n<ul>\n<li>FortiGate-90E: EOS April 2025&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>FortiGate-1500D: EOS April 2025&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>FortiGate-240D: EOS July 2025&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>FortiGate-100E: LSED August 17, 2025 \u2014 EOS August 17, 2026&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>FortiGate-80E: LSED&nbsp;approximately August 2025&nbsp;\u2014 EOS&nbsp;approximately August 2026&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>FortiGate-30E: LSED March 31, 2026 \u2014 EOS March 31, 2027&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>Broader E-series (50E, 60E, 80E, 100E, 300E, 500E): LSED window July through November 2025&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>A particularly important case is&nbsp;the&nbsp;<strong>FortiGate&nbsp;30E<\/strong>. Although its EOS date is March 2027, it is hardware-capped at&nbsp;FortiOS&nbsp;6.2.x and cannot be upgraded to any 7.x firmware.&nbsp;<a href=\"https:\/\/community.fortinet.com\/t5\/FortiGate\/Technical-Tip-FortiOS-End-of-Life-support-overview\/ta-p\/433248\" target=\"_blank\" rel=\"noreferrer noopener\">FortiOS 6.2 reached full End of Support<\/a>&nbsp;in&nbsp;approximately September 2023. This means the 30E is running fully unsupported firmware \u2014 with no security patches available \u2014 despite not yet being officially end-of-life at the hardware level. It&nbsp;represents&nbsp;a&nbsp;dangerous&nbsp;false sense of security.&nbsp;<\/p>\n\n\n\n<p>On the software side,&nbsp;<strong>FortiOS&nbsp;7.2<\/strong>&nbsp;\u2014 one of the most widely deployed versions \u2014 passed End of Engineering Support on March 31, 2025. Devices running 7.2 no longer receive bug fixes.&nbsp;<strong>FortiOS&nbsp;7.0<\/strong>&nbsp;reached full End of Support in September 2025 with no patches of any kind available. Organizations still running either version are exposed.&nbsp;<\/p>\n\n\n\n<p>The current-generation&nbsp;<strong>F-series<\/strong>&nbsp;(40F, 60F, 80F, 100F, 200F) and the newer&nbsp;<strong>G-series<\/strong>&nbsp;(40G, 60G, 80G) have no announced EOL dates as of early 2026 and represent the standard replacement targets.&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Security_risks_of_running_EOL_FortiGate_hardware\"><\/span><strong>Security risks of running EOL FortiGate hardware<\/strong>\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The consequences of operating EOL FortiGate hardware are not theoretical. The 2024\u20132025 period produced some of the most actively exploited Fortinet vulnerabilities on record:&nbsp;<\/p>\n\n\n\n<ul>\n<li><strong>CVE-2024-21762 (CVSS 9.8 \u2014 Critical)<\/strong>&nbsp;is an out-of-bounds&nbsp;write vulnerability in&nbsp;FortiOS&nbsp;that allows&nbsp;unauthenticated&nbsp;remote code execution via HTTP requests.&nbsp;It was actively exploited by threat actors including suspected state-sponsored groups.&nbsp;A compromised FortiGate effectively means complete loss of network perimeter control.&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li><strong>CVE-2024-23113 (Critical \u2014 Format String RCE)<\/strong>&nbsp;was added by CISA to its Known Exploited Vulnerabilities catalog. As of October 2024, the&nbsp;Shadowserver&nbsp;Foundation&nbsp;identified&nbsp;over 87,000 internet-facing Fortinet devices still vulnerable to this flaw \u2014 allowing unauthenticated remote code and command execution.&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li><strong>CVE-2024-55591 (CVSS 9.6 \u2014 Authentication Bypass Zero-Day)<\/strong>&nbsp;was&nbsp;disclosed&nbsp;in January 2025 but had been exploited in the wild since November 2024. It allows attackers to escalate privileges to super-admin&nbsp;level&nbsp;without authentication. The&nbsp;<a href=\"https:\/\/therecord.media\/mora001-ransomware-gang-exploiting-vulnerability-lockbit\" target=\"_blank\" rel=\"noreferrer noopener\">Mora_001 ransomware group<\/a>&nbsp;\u2014 linked to&nbsp;LockBit&nbsp;\u2014 exploited this vulnerability to create rogue admin accounts,&nbsp;establish&nbsp;<a href=\"https:\/\/extendsclass.com\/blog\/vpn-protect-yourself\" target=\"_blank\" rel=\"noreferrer noopener\">VPN<\/a>&nbsp;tunnels,&nbsp;modify&nbsp;firewall&nbsp;policies, and move laterally across victim networks. A companion flaw,&nbsp;<strong>CVE-2025-24472<\/strong>, was exploited alongside it in early 2025 campaigns.&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>For organizations on EOL hardware or firmware, none of these patches are available. CISA has added multiple&nbsp;FortiOS&nbsp;vulnerabilities to its Known Exploited Vulnerabilities catalog, and the expectation that attackers will discover and exploit new flaws in unpatched devices is well-founded.&nbsp;<\/p>\n\n\n\n<p>Beyond direct compromise,&nbsp;<strong>compliance exposure<\/strong>&nbsp;is&nbsp;substantial. Running unsupported network security hardware typically conflicts with:&nbsp;<\/p>\n\n\n\n<ul>\n<li>PCI-DSS requirements for current security controls&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>HIPAA technical safeguard requirements&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>NIST SP 800-53 patch management controls&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>SOC 2 operational security criteria&nbsp;<\/li>\n<\/ul>\n\n\n\n<ul>\n<li>ISO 27001 asset management and vulnerability management clauses&nbsp;<\/li>\n<\/ul>\n\n\n\n<p>Auditors and regulatory bodies are increasingly flagging EOL network equipment during assessments. The combination of technical risk and compliance liability makes delayed action an increasingly difficult position to justify.\u00a0<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"560\" height=\"313\" src=\"https:\/\/extendsclass.com\/blog\/wp-content\/uploads\/2026\/03\/image-2.jpg\" alt=\"\" class=\"wp-image-2284\" srcset=\"https:\/\/extendsclass.com\/blog\/wp-content\/uploads\/2026\/03\/image-2.jpg 560w, https:\/\/extendsclass.com\/blog\/wp-content\/uploads\/2026\/03\/image-2-300x168.jpg 300w\" sizes=\"(max-width: 560px) 100vw, 560px\" \/><\/figure>\n\n\n\n<p><em>FortiGate Security Risks<\/em>\u00a0<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Planning_your_FortiGate_EOL_migration\"><\/span><strong>Planning your FortiGate EOL migration<\/strong>\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>A structured&nbsp;<a href=\"https:\/\/extendsclass.com\/blog\/the-importance-of-data-governance-during-migration\" target=\"_blank\" rel=\"noreferrer noopener\">migration<\/a>&nbsp;approach reduces both risk and cost. The following six-step process addresses the full scope of a FortiGate refresh:&nbsp;<\/p>\n\n\n\n<ol start=\"1\">\n<li><strong>Audit your inventory.<\/strong>&nbsp;Document every FortiGate model and firmware version in your environment. Cross-reference against the Fortinet Product Life Cycle page at support.fortinet.com (a free&nbsp;FortiCloud&nbsp;account is&nbsp;required). Third-party references such as&nbsp;endoflife.date\/fortios&nbsp;and Park Place Technologies\u2019 EOL lists provide quick&nbsp;lookup&nbsp;without an account. Flag any device meeting one or more of these criteria: past EOS date, running a&nbsp;FortiOS&nbsp;version past EOES, or with LSED within the next 12 months.&nbsp;<\/li>\n<\/ol>\n\n\n\n<ol start=\"2\">\n<li><strong>Prioritize by risk.<\/strong>&nbsp;Internet-facing devices on EOL hardware or firmware represent the highest attack surface and should be addressed first. Devices managing sensitive network segments \u2014 finance, HR, PCI-scoped environments \u2014 are next. Internal&nbsp;segmentation&nbsp;firewalls with no direct external exposure can follow. FortiGate devices sit at the perimeter; a compromise affects everything behind them.&nbsp;<\/li>\n<\/ol>\n\n\n\n<ol start=\"3\">\n<li><strong>Act on LSED deadlines&nbsp;immediately.<\/strong>&nbsp;If any&nbsp;device\u2019s&nbsp;LSED is approaching, renew support contracts before that date. Missing the LSED deadline means support cannot be extended at any price,&nbsp;eliminating&nbsp;the option to&nbsp;maintain&nbsp;coverage through the migration window.&nbsp;<\/li>\n<\/ol>\n\n\n\n<ol start=\"4\">\n<li><strong>Plan the firmware migration path.<\/strong>&nbsp;Target firmware for new or refreshed hardware should be&nbsp;FortiOS&nbsp;7.4 (EOS November 2027) or&nbsp;FortiOS&nbsp;7.6 (EOS January 2029). Use Fortinet\u2019s Upgrade Path Tool at docs.fortinet.com\/upgrade-tool to&nbsp;identify&nbsp;valid upgrade sequences.&nbsp;FortiConverter&nbsp;can automate configuration migration from legacy to new hardware, significantly reducing manual rework.&nbsp;<\/li>\n<\/ol>\n\n\n\n<ol start=\"5\">\n<li><strong>Choose the replacement path.<\/strong>&nbsp;The most common option is a like-for-like hardware refresh to current F-series or G-series equivalents \u2014 for example, replacing a FortiGate 60D or 80D with a FortiGate 60F or 60G, or a FortiGate 300D with a 200F or 400F. Fortinet\u2019s&nbsp;TradeUp&nbsp;Program offers up to 40% off new units with transfer of existing security subscriptions. For organizations modernizing toward cloud-first architectures, FortiGate Cloud and&nbsp;FortiSASE&nbsp;provide managed&nbsp;firewall&nbsp;and SASE options that&nbsp;eliminate&nbsp;hardware lifecycle concerns. Smaller organizations without dedicated security staff may&nbsp;benefit&nbsp;from working with a Fortinet-authorized MSSP that manages the EOL lifecycle on their behalf.&nbsp;<\/li>\n<\/ol>\n\n\n\n<ol start=\"6\">\n<li><strong>Test before cutting over.<\/strong>&nbsp;Validate replacement configurations in a lab or staging environment before production deployment. Verify all policy rules, VPN configurations, SD-WAN settings, and UTM profiles. Maintain a rollback plan for 24 to 48 hours after the production cutover.&nbsp;<\/li>\n<\/ol>\n\n\n\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" width=\"1\" height=\"1\" src=\"https:\/\/extendsclass.com\/blog\/wp-content\/uploads\/2026\/03\/image.png\" alt=\"\" class=\"wp-image-2274\"\/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span><strong>Conclusion<\/strong>&nbsp;<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>FortiGate end-of-life is not a distant concern for most enterprise networks \u2014 it is a present-day operational and security issue. The D-series and E-series hardware families that form the backbone of many network environments are cycling through their final support milestones now.&nbsp;FortiOS&nbsp;versions 7.0 and 7.2, still widely deployed, are either fully unsupported or past engineering support as of 2025.&nbsp;The vulnerabilities being actively exploited against these platforms \u2014 several with CVSS scores above 9.5 \u2014&nbsp;demonstrate that attackers are well aware of which devices are no longer receiving patches.&nbsp;<\/p>\n\n\n\n<p>The path forward requires a complete picture of your environment: which hardware models you are running, which&nbsp;FortiOS&nbsp;versions are installed, and where each&nbsp;sits&nbsp;in the Fortinet lifecycle. From that baseline, the LSED deadlines and EOS dates drive&nbsp;the prioritization. Organizations that plan 12 to 18 months ahead avoid both the compliance risk of running unsupported hardware and the operational disruption of a rushed emergency replacement.&nbsp;<\/p>\n\n\n\n<p>Proactive planning is the only effective response to a lifecycle process that moves on a fixed schedule regardless of operational readiness.&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Your&nbsp;firewall&nbsp;is the first line of defense between your network and the internet. But what happens when that&nbsp;firewall&nbsp;stops receiving security patches? For thousands of organizations running older FortiGate hardware, this is not a hypothetical \u2014 it is the current reality. In early 2025, a threat actor known as \u201cBelsen Group\u201d published stolen configuration data from approximately [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2282,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":""},"categories":[2],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/posts\/2273"}],"collection":[{"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/comments?post=2273"}],"version-history":[{"count":1,"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/posts\/2273\/revisions"}],"predecessor-version":[{"id":2285,"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/posts\/2273\/revisions\/2285"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/media\/2282"}],"wp:attachment":[{"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/media?parent=2273"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/categories?post=2273"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/extendsclass.com\/blog\/wp-json\/wp\/v2\/tags?post=2273"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}