{"id":9070,"date":"2026-11-20T17:17:28","date_gmt":"2026-11-20T11:47:28","guid":{"rendered":"https:\/\/www.anakage.com\/blog\/?p=9070"},"modified":"2026-11-20T17:17:28","modified_gmt":"2026-11-20T11:47:28","slug":"anakage-com-blog-air-gapped-patching-2027","status":"publish","type":"post","link":"https:\/\/www.anakage.com\/blog\/anakage-com-blog-air-gapped-patching-2027\/","title":{"rendered":"Air-Gapped Patching in 2027: Beyond WSUS Export and Import"},"content":{"rendered":"<p dir=\"ltr\">Air-gapped patching in 2027 means running a tested, evidence-backed offline workflow, not just copying WSUS updates onto a USB drive. WSUS still works, but Microsoft no longer adds features to it. Three deadlines need a plan now: Secure Boot certificates, Server 2016 end of support, and RBI&#8217;s 2026 patch rules.<\/p>\n<h2 dir=\"ltr\">Is WSUS Still Safe for Air-Gapped Patching in 2027?<\/h2>\n<p dir=\"ltr\">Yes, WSUS still works for disconnected networks, but plan around its status. Microsoft deprecated it in September 2024. That means no new features, though existing content and Configuration Manager support continue.<\/p>\n<blockquote dir=\"ltr\">\n<p dir=\"ltr\"><strong>Air-gapped network<\/strong> \u2014 a network that is physically isolated from the internet and every other outside connection.<\/p>\n<\/blockquote>\n<blockquote dir=\"ltr\">\n<p dir=\"ltr\"><strong>WSUS (Windows Server Update Services)<\/strong> \u2014 a Microsoft server role that downloads updates once and shares them with internal machines.<\/p>\n<\/blockquote>\n<p dir=\"ltr\">Microsoft has published no WSUS end date. Planning against the Windows Server 2025 lifecycle is the safe route. Mainstream support runs to 2029 and extended support to 2034.<\/p>\n<p dir=\"ltr\">Three details matter for offline teams:<\/p>\n<ul dir=\"ltr\">\n<li><strong>Windows Internal Database is deprecated.<\/strong> Move new WSUS builds to SQL Server Express or full SQL Server.<\/li>\n<li><strong>Driver sync stays.<\/strong> Microsoft postponed its removal in April 2025 after feedback from disconnected environments.<\/li>\n<li><strong>Server 2025 WSUS has an ESU gap.<\/strong> Since September 2025, legacy clients on Extended Security Updates cannot self-update their agent from it. Microsoft documents a workaround.<\/li>\n<\/ul>\n<p dir=\"ltr\">Your patch server is also a target. CVE-2025-59287 let an attacker run code on WSUS without logging in, and it scored 9.8 out of 10.<\/p>\n<p dir=\"ltr\">Microsoft shipped an out-of-band fix on 23 October 2025. Attackers exploited the flaw within days, and CISA added it to its exploited-flaw catalogue.<\/p>\n<h2 dir=\"ltr\">Why Is Air-Gapped Patching Harder in 2027?<\/h2>\n<p dir=\"ltr\">The patch window keeps shrinking, while offline cycles stay slow. Google&#8217;s Mandiant M-Trends 2026 report estimates mean time to exploit at minus seven days. That means attacks often start before a patch exists.<\/p>\n<p dir=\"ltr\">Verizon&#8217;s 2026 breach report covers 2025 data. Only 26% of known-exploited flaws were fully fixed, down from 38%. The median time to a full fix rose from 32 to 43 days.<\/p>\n<blockquote dir=\"ltr\">\n<p dir=\"ltr\"><strong>KEV (Known Exploited Vulnerabilities)<\/strong> \u2014 CISA&#8217;s catalogue of flaws that attackers are already using in real attacks.<\/p>\n<\/blockquote>\n<p dir=\"ltr\">Exploiting flaws became the top way into networks, at 31% of initial access. Verizon also found 60 to 70% of KEV flaws were still open after seven days.<\/p>\n<p dir=\"ltr\">A monthly offline cycle hands attackers weeks. When no patch exists yet, compensating controls buy time. Segmentation and disabled services are the usual choices.<\/p>\n<h2 dir=\"ltr\">What Changed for Secure Boot on Offline Windows Machines?<\/h2>\n<p dir=\"ltr\">The Microsoft Secure Boot certificates from 2011 began expiring in June 2026. The last one, Windows Production PCA 2011, expired on 19 October 2026. Sources give 24 or 27 June for the first two, so we say late June.<\/p>\n<blockquote dir=\"ltr\">\n<p dir=\"ltr\"><strong>Secure Boot<\/strong> \u2014 a firmware feature that only lets trusted, signed software start during boot.<\/p>\n<\/blockquote>\n<p dir=\"ltr\">Microsoft&#8217;s notice says devices without the new certificates lose the ability to install Secure Boot security updates. They also stop receiving Windows boot manager fixes after the October expiry.<\/p>\n<p dir=\"ltr\">Machines still boot. The risk is falling behind on boot-level protections, such as future revocations of vulnerable boot components.<\/p>\n<p dir=\"ltr\">Offline machines are the most exposed. They cannot pull the 2023 certificates from Windows Update. You must deliver them yourself.<\/p>\n<p dir=\"ltr\">Here is a practical way to handle it:<\/p>\n<ol dir=\"ltr\">\n<li><strong>Inventory Secure Boot state.<\/strong> Record firmware vendor, model and whether the 2023 certificates are present.<\/li>\n<li><strong>Install the latest cumulative update.<\/strong> Microsoft delivers the certificate change through monthly servicing on supported builds.<\/li>\n<li><strong>Apply firmware updates first.<\/strong> Some older BIOS versions block the certificate change.<\/li>\n<li><strong>Pilot on one model per vendor.<\/strong> A bad firmware combination can cause a boot failure.<\/li>\n<li><strong>Keep BitLocker recovery keys ready.<\/strong> Boot changes can trigger recovery prompts.<\/li>\n<\/ol>\n<p dir=\"ltr\">Where servicing does not apply the change, follow Microsoft&#8217;s published manual steps for the DB and KEK stores. Test any claimed offline shortcut on a spare device first.<\/p>\n<h2 dir=\"ltr\">How Do You Handle Windows Server 2016 End of Support Offline?<\/h2>\n<p dir=\"ltr\">Windows Server 2016 reaches end of extended support on 12 January 2027. Microsoft&#8217;s own Windows Server blog gives that date. The January 2027 security update is the last free one.<\/p>\n<p dir=\"ltr\">Servers keep running after that date. They stop getting new security fixes unless you buy Extended Security Updates, or ESU. Microsoft describes ESU for Server 2016 as delivered through Azure Arc.<\/p>\n<p dir=\"ltr\">That raises a question for air-gapped sites. Azure Arc needs connectivity. Ask Microsoft licensing now how a disconnected server gets ESU, and get the answer in writing.<\/p>\n<p dir=\"ltr\">Other dates land in your planning window:<\/p>\n<div dir=\"ltr\">\n<table>\n<thead>\n<tr>\n<th scope=\"col\">Product<\/th>\n<th scope=\"col\">Date<\/th>\n<th scope=\"col\">What it means<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Windows Server 2016<\/td>\n<td>12 Jan 2027<\/td>\n<td>Free security fixes stop<\/td>\n<\/tr>\n<tr>\n<td>SQL Server 2017<\/td>\n<td>12 Oct 2027<\/td>\n<td>Affects WSUS and ConfigMgr databases<\/td>\n<\/tr>\n<tr>\n<td>SQL Server 2016<\/td>\n<td>14 Jul 2026<\/td>\n<td>Already out of support<\/td>\n<\/tr>\n<tr>\n<td>Windows Server 2012 R2<\/td>\n<td>Final ESU year ended 13 Oct 2026<\/td>\n<td>Already out of coverage<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p dir=\"ltr\">Check your WSUS and ConfigMgr database versions now. Many offline sites run them on older SQL Server.<\/p>\n<h2 dir=\"ltr\">How to Patch an Air-Gapped Network: An 8-Step Workflow<\/h2>\n<p dir=\"ltr\">Good offline patching is a loop with checkpoints. Each step produces a record an auditor can read. This workflow works with WSUS or any other tool.<\/p>\n<ol dir=\"ltr\">\n<li><strong>Classify your offline segments.<\/strong> List what is truly isolated and what is not. Include engineering laptops that move between networks.<\/li>\n<li><strong>Build a connected staging server.<\/strong> Keep it hardened and separate from production. It downloads updates and third-party installers.<\/li>\n<li><strong>Verify every file.<\/strong> Check vendor signatures and SHA-256 hashes. On Windows 11 24H2 and later, download the checkpoint update as well as the latest cumulative update.<\/li>\n<li><strong>Transfer under chain of custody.<\/strong> Use authorised, scanned, write-protected media with a signed log. Record who carried it and when.<\/li>\n<li><strong>Import and stage on the offline server.<\/strong> Copy metadata and content together. Content copied late is a common cause of failed approvals.<\/li>\n<li><strong>Test in a pilot ring.<\/strong> Patch 5% of devices first, covering every hardware model. Wait 48 to 72 hours.<\/li>\n<li><strong>Deploy in rings.<\/strong> Move from pilot to the full fleet over days, not hours. Keep a documented rollback for each ring.<\/li>\n<li><strong>Verify and file evidence.<\/strong> Pull a report that shows installed, failed and pending patches per device.<\/li>\n<\/ol>\n<p dir=\"ltr\">Our team has seen step 8 skipped more than any other. Without it, you cannot prove a patch landed. That matters at audit time.<\/p>\n<p dir=\"ltr\">For the export and import commands, see our guide on <a href=\"https:\/\/www.anakage.com\/blog\/third-party-patching-air-gapped-networks\/\">third-party patching on air-gapped networks<\/a>.<\/p>\n<h2 dir=\"ltr\">What Do RBI&#8217;s 2026 Directions Say About Patching and USB Media?<\/h2>\n<p dir=\"ltr\">RBI issued its Commercial Banks Cybersecurity, Technology Risk, Resilience and Assurance Framework Directions on 31 July 2026. They took effect immediately and replace the 2016 framework. NBFC and urban co-operative bank versions also exist.<\/p>\n<p dir=\"ltr\">Four provisions matter most for patching:<\/p>\n<ul dir=\"ltr\">\n<li><strong>Paragraph 98:<\/strong> Banks need documented patch and change policies. They must assess business impact before applying or withholding a patch.<\/li>\n<li><strong>Paragraph 98(4):<\/strong> Banks need a way to recover from failed patch deployments.<\/li>\n<li><strong>Paragraph 58:<\/strong> Banks must track vendor patch releases and CERT-In advisories. Actively exploited flaws follow an emergency process.<\/li>\n<li><strong>Paragraphs 56 and 57:<\/strong> Banks need a central list of authorised software. They must control installs centrally and block the rest.<\/li>\n<\/ul>\n<p dir=\"ltr\">The directions set no fixed number of days. They say &#8220;timely&#8221; and &#8220;expeditiously&#8221;, so your policy must define those words.<\/p>\n<p dir=\"ltr\">Removable media matters just as much. Paragraphs 121 to 125 prohibit removable media by default. Each use needs specific authorisation for a defined purpose and period.<\/p>\n<p dir=\"ltr\">Media must also be scanned before anyone reads or writes to it. Your patch-transfer USB drive needs a named owner, an approval and a scan record. Auditors will ask for all three.<\/p>\n<p dir=\"ltr\">Incident reporting runs on a tight clock too. Banks report cyber incidents to RBI&#8217;s DAKSH platform within six hours. Verify paragraph numbers against RBI&#8217;s published text for your entity type.<\/p>\n<h2 dir=\"ltr\">What Happens After the Patch Lands on an Offline Endpoint?<\/h2>\n<p dir=\"ltr\">Delivering the patch is half the job. Failed installs, pending reboots and stopped services leave devices out of compliance. RBI paragraph 98(4) expects you to recover from those failures.<\/p>\n<p dir=\"ltr\">Here is what we see in our customer deployments across Indian BFSI and manufacturing. These results are customer-reported. Not every site was air-gapped, but each shows what post-patch repair and evidence look like at scale.<\/p>\n<ul dir=\"ltr\">\n<li><strong>A leading private bank.<\/strong> Manual work held compliance at 90 to 95%. Automated checks and self-heal lifted it to 99% and cut manual effort by 85%, with no PowerShell.<\/li>\n<li><strong>A BFSI insurer with 15,875 devices.<\/strong> Late patch rollouts caused repeat tickets. A compliance view now shows patch adherence, even offline, and fixes average under 11 seconds.<\/li>\n<li><strong>An automotive manufacturer.<\/strong> Delayed patch reboots and uneven antivirus enforcement created audit risk. Over 3,350 automated fixes brought essential services to 95% compliance.<\/li>\n<\/ul>\n<p dir=\"ltr\">The lesson is simple. Offline patching needs a repair loop, not only a delivery path.<\/p>\n<h2 dir=\"ltr\">Is Your &#8220;Air-Gapped&#8221; Network Really Air-Gapped?<\/h2>\n<p dir=\"ltr\">Often it is not. Action1 argued in January 2026 that most air gaps are &#8220;faux gaps&#8221;. Laptops, shared admin accounts and convenience exceptions quietly bridge the network.<\/p>\n<p dir=\"ltr\">A true air gap needs strict habits. That means no dual-homed machines, no laptops moving in and out, and no unlogged removable media. It also means no shared admin credentials.<\/p>\n<p dir=\"ltr\">Run a simple test:<\/p>\n<ol dir=\"ltr\">\n<li>List every device that has ever connected to both networks.<\/li>\n<li>Check whether any admin account works on both sides.<\/li>\n<li>Review the last 90 days of USB and media logs.<\/li>\n<li>Confirm your staging server cannot reach the offline network directly.<\/li>\n<\/ol>\n<p dir=\"ltr\">If any check fails, treat the network as low-connectivity, not isolated. Then patch it faster.<\/p>\n<h2 dir=\"ltr\">What Are the Alternatives to WSUS Export and Import?<\/h2>\n<p dir=\"ltr\">You have six realistic paths for disconnected Windows fleets. None is best for everyone.<\/p>\n<ul dir=\"ltr\">\n<li><strong>WSUS with a connected publisher.<\/strong> It is free and familiar. It needs steady manual effort and careful certificate handling.<\/li>\n<li><strong>Configuration Manager with a disconnected software update point.<\/strong> It suits large Microsoft estates. It is complex and needs skilled staff.<\/li>\n<li><strong>ManageEngine Patch Manager Plus.<\/strong> Its closed-network tool downloads patch data on a connected machine. You move it across, then scan, test, approve and deploy inside.<\/li>\n<li><strong>Patch My PC for third-party apps.<\/strong> It adds Chrome, Java and Adobe updates to WSUS or Configuration Manager.<\/li>\n<li><strong>WSUS Offline Update.<\/strong> The original tool is deprecated. A community fork on GitLab continues it, so verify downloads and check Windows 11 support first.<\/li>\n<li><strong>Anakage for the post-patch gap.<\/strong> It is one option worth considering. Its agents run fully offline, repair failed installs and report patch adherence.<\/li>\n<li><strong>Where it fits.<\/strong> It complements WSUS or Configuration Manager. It does not replace patch approval or scheduling.<\/li>\n<\/ul>\n<p dir=\"ltr\">Cloud tools such as Intune and Azure Update Manager need connectivity. They do not fit true air gaps. Ask every vendor one question: what still works with zero outbound access?<\/p>\n<h2 dir=\"ltr\">What Should You Do Before 2027 Starts?<\/h2>\n<p dir=\"ltr\">Use this short list in your next change window:<\/p>\n<ol dir=\"ltr\">\n<li>Audit Secure Boot certificate status on every hardware model.<\/li>\n<li>Decide your Server 2016 plan: upgrade, retire or buy ESU.<\/li>\n<li>Write patch timelines by severity into policy, and define &#8220;timely&#8221;.<\/li>\n<li>Authorise and log every removable-media transfer.<\/li>\n<li>Add a test ring, a repair step and an evidence report to every cycle.<\/li>\n<\/ol>\n<h2 dir=\"ltr\">FAQ<\/h2>\n<p dir=\"ltr\">Q: How do you patch an air-gapped network?<\/p>\n<p dir=\"ltr\">A: Download and verify updates on a connected staging server. Move them across on authorised, scanned media. Then test in a pilot ring and deploy to the fleet in stages.<\/p>\n<p dir=\"ltr\">Q: Is WSUS being discontinued in 2027?<\/p>\n<p dir=\"ltr\">A: No. Microsoft deprecated WSUS in September 2024, which means no new features. It still ships with Windows Server 2025, and no end date is published.<\/p>\n<p dir=\"ltr\">Q: Can you patch Windows offline without internet?<\/p>\n<p dir=\"ltr\">A: Yes. You can use WSUS export and import, the Microsoft Update Catalog, or a tool with a closed-network mode. Each needs a connected machine somewhere to fetch updates.<\/p>\n<p dir=\"ltr\">Q: What happens if Secure Boot certificates expire on offline machines?<\/p>\n<p dir=\"ltr\">A: They keep booting. They stop receiving new Secure Boot security updates and, after October 2026, boot manager fixes. Deliver the 2023 certificates through cumulative and firmware updates yourself.<\/p>\n<p dir=\"ltr\">Q: How often should you patch an air-gapped network?<\/p>\n<p dir=\"ltr\">A: Monthly at minimum, aligned with Patch Tuesday. Use a faster emergency process for known-exploited flaws. Faster cycles matter more as exploit windows shrink.<\/p>\n<p dir=\"ltr\">Q: Does RBI set a deadline for applying patches?<\/p>\n<p dir=\"ltr\">A: RBI&#8217;s 2026 directions say patches must be applied in a secure and timely way. They set no fixed number of days. Your board-approved policy sets the clock, and auditors check you meet it.<\/p>\n<p dir=\"ltr\">Q: Can you use USB drives to patch a bank network under RBI rules?<\/p>\n<p dir=\"ltr\">A: Only with authorisation. RBI prohibits removable media by default and requires scanning before use. Name an owner, log each transfer and keep scan records.<\/p>\n<p dir=\"ltr\">Q: How do you patch third-party software like Chrome and Java offline?<\/p>\n<p dir=\"ltr\">A: Download the installers on the staging server and verify their signatures. Publish them through WSUS with a tool like Patch My PC, or push them with an agent-based tool. Test each one before wider rollout.<\/p>\n<p dir=\"ltr\">\n<p dir=\"ltr\">Air-gapped patching in 2027 is a loop of verify, test, deploy, repair and prove, not a file copy. Fix Secure Boot, Server 2016 and your RBI policy wording first.<\/p>\n<p dir=\"ltr\">If your environment needs agents that run fully offline, Anakage offers a free 30 minute demo at <a href=\"https:\/\/www.anakage.com\/book-a-demo\">anakage.com\/book-a-demo<\/a>. It is worth a look if that matches your setup.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Air-gapped patching in 2027 means running a tested, evidence-backed offline workflow, not just copying WSUS updates onto a USB drive. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":9071,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_themeisle_gutenberg_block_has_review":false,"footnotes":""},"categories":[1],"tags":[],"coauthors":[88],"class_list":["post-9070","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"views":57,"_links":{"self":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts\/9070","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/comments?post=9070"}],"version-history":[{"count":1,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts\/9070\/revisions"}],"predecessor-version":[{"id":9072,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/posts\/9070\/revisions\/9072"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/media\/9071"}],"wp:attachment":[{"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/media?parent=9070"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/categories?post=9070"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/tags?post=9070"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.anakage.com\/blog\/wp-json\/wp\/v2\/coauthors?post=9070"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}