<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/" >

<channel>
	<title>Industry Insights &#8211; Nagios Library</title>
	<atom:link href="https://library.nagios.com/industry-insights/feed/" rel="self" type="application/rss+xml" />
	<link>https://library.nagios.com</link>
	<description>Complete Nagios monitoring resources and documentation</description>
	<lastBuildDate>Thu, 12 Nov 2026 21:35:11 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://library.nagios.com/wp-content/uploads/2024/11/Nagios-Blue-N.svg</url>
	<title>Industry Insights &#8211; Nagios Library</title>
	<link>https://library.nagios.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Virtual Appliance Kernel Debt: How to Track Running Kernels</title>
		<link>https://library.nagios.com/industry-insights/virtual-appliance-kernel-debt-how-to-track-running-kernels/</link>
		
		<dc:creator><![CDATA[Sam Napier]]></dc:creator>
		<pubDate>Thu, 12 Nov 2026 21:16:10 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[VMware]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71335</guid>

					<description><![CDATA[An OVA (Open Virtualization Format Archive) is not only an application installer. It is a snapshot of a guest operating system, including the Linux kernel and every module that kernel can load. When a virtual appliance image remains in service for years, its guest-kernel security debt remains in service too—and most operations teams cannot immediately [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">An OVA (Open Virtualization Format Archive) is not only an application installer. It is a snapshot of a guest operating system, including the Linux kernel and every module that kernel can load. When a virtual appliance image remains in service for years, its guest-kernel security debt remains in service too—and most operations teams cannot immediately report which kernel versions or drivers are running across the appliances they have already deployed.</p>



<p class="wp-block-paragraph">That blind spot becomes acute whenever a kernel driver vulnerability is disclosed before a fix or affected-version range is available. The current example is ZDI-CAN-34068, a local privilege-escalation report in the Linux kernel&#8217;s <code>vmwgfx</code> driver that reached public mailing lists without an accompanying patch, CVE assignment, or affected-version list. Whether a patch is pending or already shipping upstream, the operational problem is the same: replacing a downloadable OVA does not update appliances already running in the field, and patching the hypervisor does not touch the guest kernel inside them.</p>



<h2 class="wp-block-heading">ZDI-CAN-34068 as the Current Example—and Why <code>vmwgfx</code> Is a Recurring Surface</h2>



<p class="wp-block-paragraph">On October 21, 2026, the Zero Day Initiative sent a report to the public Linux kernel mailing list titled “Linux Kernel vmwgfx Dirty Tracking Out-Of-Bounds Write Local Privilege Escalation Vulnerability.” The report is tracked as ZDI-CAN-34068. Greg Kroah-Hartman replied on October 22 that the report had reached public lists without a patch. ZDI&#8217;s upcoming-advisory page lists Linux as the vendor, CVSS 8.8, a report date of October 21, 2026, and a disclosure deadline of February 18, 2027.</p>



<p class="wp-block-paragraph">Contemporaneous reporting described the disclosure as one of several vulnerability reports posted before a mainline fix was available. TuxCare&#8217;s status table identifies <code>vmwgfx</code> and local privilege escalation, labels the entry “title only,” and states that no KernelCare action is planned until technical details exist.</p>



<p class="wp-block-paragraph">As of October 22, 2026, the public record supports these statements:</p>



<ul class="wp-block-list">
<li>The reported vulnerability is associated with the Linux kernel&#8217;s <code>vmwgfx</code> component.</li>



<li>Its published title describes dirty tracking, an out-of-bounds write, and local privilege escalation.</li>



<li>No upstream patch accompanied the public mailing-list report.</li>



<li>No affected-version range has been published.</li>



<li>No CVE tied to ZDI-CAN-34068 was found in current public search results.</li>
</ul>



<p class="wp-block-paragraph">The record does <strong>not</strong> support claims about a triggering operation, vulnerable data structure, reliable workaround, indicators of compromise, or which appliance releases are affected. Those questions remain open until maintainers or distribution vendors publish authoritative details.</p>



<p class="wp-block-paragraph">Even after ZDI-CAN-34068 receives an upstream fix, <code>vmwgfx</code> will remain a relevant case study for virtual appliance hygiene. Earlier disclosures in the same driver show that virtual graphics modules in Linux guests require routine kernel lifecycle management:</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Identifier</th><th>Reported area in <code>vmwgfx</code></th><th>Impact class</th><th>Operational takeaway</th></tr></thead><tbody><tr><td><strong>CVE-2022-36280</strong></td><td>Cursor snooper handling</td><td>Out-of-bounds write / local privilege escalation</td><td>In-guest driver flaws persist in older appliance kernels until the guest OS is patched</td></tr><tr><td><strong>ZDI-26-232 / CVE-2025-40277</strong></td><td><code>vmw_cmd_check</code> command validation</td><td>Local privilege escalation</td><td>Hypervisor updates do not remediate command-checking defects inside the guest kernel module</td></tr><tr><td><strong>CVE-2026-80700</strong></td><td><code>vmw_external_bo_copy</code> bounds checking</td><td>Out-of-bounds access</td><td>Requires verifying the exact running guest kernel package, not just the appliance version</td></tr><tr><td><strong>ZDI-CAN-34068</strong></td><td>Dirty tracking (title-only disclosure)</td><td>Out-of-bounds write / local privilege escalation (CVSS 8.8)</td><td>Demonstrates why operators need kernel and module inventory before affected versions are named</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">ZDI-CAN-34068 must not be conflated with those earlier flaws. Their mechanics do not explain this report, and their fixes do not remediate it. Together, however, they show that an in-guest virtual hardware driver is a recurring kernel patch surface.</p>



<p class="wp-block-paragraph">Sources: <a href="https://www.zerodayinitiative.com/advisories/upcoming/" target="_blank" rel="noopener">ZDI upcoming-advisory record</a>, <a href="https://lore.landau.one/lkml/2026102254-protector-seventy-6454@gregkh/T/" target="_blank" rel="noopener">Linux kernel mailing-list thread</a>, <a href="https://www.phoronix.com/news/LKML-New-Trend-Vulnerabilities" target="_blank" rel="noopener">Phoronix reporting</a>, and <a href="https://tuxcare.com/blog/zdi-ksmbd-bugs-cve/" target="_blank" rel="noopener">TuxCare status summary</a>.</p>



<h2 class="wp-block-heading"><strong>The Patch Belongs to the Guest Kernel, Not the Hypervisor</strong></h2>



<p class="wp-block-paragraph"><code>vmwgfx</code> is the Linux Direct Rendering Manager (DRM) driver for VMware&#8217;s virtual GPU. In a virtual appliance deployment, it is part of the Linux kernel running inside the guest virtual machine (VM) created from the OVA. ESXi or another hypervisor hosts that guest, but does not replace the guest&#8217;s kernel modules.</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>flowchart TB

  hypervisor&#91;Hypervisor&#93;

  guest&#91;Guest VM&#93;

  kernel&#91;Guest Linux kernel&#93;

  vmwgfx&#91;vmwgfx module&#93;

  flaw&#91;Driver vulnerability&#93;

  hypervisor --> guest

  guest --> kernel

  kernel --> vmwgfx

  vmwgfx --> flaw</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #C586C0">flowchart</span><span style="color: #D4D4D4"> </span><span style="color: #DCDCAA">TB</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">hypervisor</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Hypervisor</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">guest</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Guest VM</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">kernel</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Guest Linux kernel</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">vmwgfx</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">vmwgfx module</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">flaw</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Driver vulnerability</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">hypervisor </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">guest</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">guest </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">kernel</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">kernel </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">vmwgfx</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">vmwgfx </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">flaw</span></span></code></pre></div>



<p class="wp-block-paragraph">The remediation unit is therefore the guest kernel. Patching the hypervisor is necessary infrastructure maintenance, but it does not update a vulnerable guest kernel and should not be recorded as remediation for an in-guest driver flaw.</p>



<p class="wp-block-paragraph">Every published OVA should have a build manifest that names its kernel version, and vendors should record whether <code>vmwgfx</code> is present and expected to load. Without that record, neither a vendor nor an operator can quickly determine whether an upstream fix has reached a given appliance.</p>



<h2 class="wp-block-heading"><strong>Why Historical Appliance Images Preserve Guest-Kernel Debt</strong></h2>



<p class="wp-block-paragraph">When a vendor builds an OVA, the build freezes an application and operating-system stack into a single image. A download portal or image library distributes that file, and operators deploy running virtual machines from it. Replacing the download file later does not touch appliances that were already deployed.</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>flowchart LR

  build&#91;Appliance build&#93; --> ova&#91;Published OVA&#93;

  ova --> portal&#91;Download portal or template library&#93;

  portal --> deployed&#91;Deployed appliance in the field&#93;

  build --> replacement&#91;Replacement OVA with patched kernel&#93;

  replacement --> portal

  deployed -->|"In-place kernel update or migration"| replacement</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #C586C0">flowchart</span><span style="color: #D4D4D4"> </span><span style="color: #DCDCAA">LR</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">build</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Appliance build</span><span style="color: #C586C0">&#93;</span><span style="color: #D4D4D4"> </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">ova</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Published OVA</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">ova </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">portal</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Download portal or template library</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">portal </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">deployed</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Deployed appliance in the field</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">build </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">replacement</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Replacement OVA with patched kernel</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">replacement </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">portal</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">deployed </span><span style="color: #C586C0">--&gt;|</span><span style="color: #CE9178">&quot;In-place kernel update or migration&quot;</span><span style="color: #C586C0">|</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">replacement</span></span></code></pre></div>



<p class="wp-block-paragraph">This lifecycle creates a gap across almost every long-lived Linux appliance:</p>



<ul class="wp-block-list">
<li>Updating the file on a download page protects only future deployments.</li>



<li>Publishing a replacement OVA gives operators a clean image for new builds or migrations.</li>



<li>Appliances already running in the field still require an in-place kernel update (plus a reboot into the updated kernel) or migration to the replacement image.</li>



<li>A newer OVA is only a security fix once its guest kernel is verified to contain the upstream or distribution patch.</li>
</ul>



<p class="wp-block-paragraph">Image owners and infrastructure teams need to trace which build produced each OVA, where older images remain cached as internal templates, how many deployed instances exist in the field, and whether those instances can consume standard package updates.</p>



<h2 class="wp-block-heading"><strong>Compensating Controls Must Carry an Uncertainty Label</strong></h2>



<p class="wp-block-paragraph">Because the published impact of ZDI-CAN-34068 is local privilege escalation, the threat model starts with code already executing as a local user or service account inside the guest. A guest DRM device node is worth inspecting because DRM nodes normally mediate userspace access to the graphics subsystem, though the public record does not establish that a specific node or operation is required for this vulnerability.</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>flowchart LR

  workload&#91;Appliance workload&#93; --> localProcess&#91;Local user or service process&#93;

  localProcess --> drmNode&#91;DRM device node&#93;

  drmNode --> vmwgfx&#91;vmwgfx module&#93;

  vmwgfx --> kernelPrivileges&#91;Guest kernel privileges&#93;</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #C586C0">flowchart</span><span style="color: #D4D4D4"> </span><span style="color: #DCDCAA">LR</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">workload</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Appliance workload</span><span style="color: #C586C0">&#93;</span><span style="color: #D4D4D4"> </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">localProcess</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Local user or service process</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">localProcess </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">drmNode</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">DRM device node</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">drmNode </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">vmwgfx</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">vmwgfx module</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">vmwgfx </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">kernelPrivileges</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Guest kernel privileges</span><span style="color: #C586C0">&#93;</span></span></code></pre></div>



<p class="wp-block-paragraph">This diagram represents a general reachability boundary, not a confirmed trigger path.</p>



<p class="wp-block-paragraph">Two precautions can reduce general exposure to <code>vmwgfx</code>:</p>



<ul class="wp-block-list">
<li>Restrict access to <code>/dev/dri/...</code> DRM device nodes to accounts that require virtual-GPU functionality.</li>



<li>Avoid loading <code>vmwgfx</code> when the appliance is verified not to require VMware SVGA acceleration.</li>
</ul>



<p class="wp-block-paragraph">Neither is a confirmed fix for ZDI-CAN-34068. The public record does not establish the exact reachability conditions, and disabling a graphics driver can affect virtual consoles, display management, support workflows, or vendor supportability. Test any module or permission change in a non-production clone, document the change, and keep a recovery path.</p>



<p class="wp-block-paragraph">Similarly, restricting shell access and removing unused local accounts shrinks the set of local processes that could attempt privilege escalation, while keeping management interfaces off untrusted networks reduces the chance that an application compromise yields local code execution inside the guest.</p>



<h2 class="wp-block-heading"><strong>What Operators and Vendors Should Do Before and After a Fix Lands</strong></h2>



<p class="wp-block-paragraph">Reducing virtual appliance kernel debt does not wait on a proof of concept.</p>



<h3 class="wp-block-heading"><strong>Before an Authoritative Patch or Version Range Exists</strong></h3>



<ol class="wp-block-list">
<li><strong>Inventory every deployed appliance.</strong> Record the appliance product and release, source OVA filename or template, <code>uname -r</code> output, distribution release, update channel, and whether a reboot is pending.</li>



<li><strong>Record driver state.</strong> Check whether <code>vmwgfx</code> is installed and currently loaded (<code>lsmod</code>, <code>modinfo vmwgfx</code>). Record its module filename, <code>vermagic</code>, and owning distribution package so the inventory can be matched against future advisories.</li>



<li><strong>Audit local execution paths and DRM permissions.</strong> Review interactive accounts, support credentials, service accounts, scheduled jobs, and plugins that execute inside the guest, and verify which users or groups can open <code>/dev/dri/card*</code> or <code>/dev/dri/renderD*</code>.</li>



<li><strong>Confirm update and reboot mechanics.</strong> Verify whether deployed appliances can take an in-place distribution kernel update or whether they must be migrated to a newly issued OVA.</li>
</ol>



<h3 class="wp-block-heading"><strong>When a Fix and Advisory Are Published</strong></h3>



<ol class="wp-block-list">
<li><strong>Map advisories to exact kernel packages.</strong> Compare the upstream or distribution advisory against the recorded kernel version of every supported OVA and deployed instance.</li>



<li><strong>Deliver both remediation paths.</strong> Vendors should publish an updated OVA through their normal build pipeline (naming the fixed kernel package in release notes), retire unpatched downloads, and provide an authenticated in-place update path where supported.</li>



<li><strong>Verify the running kernel after reboot.</strong> Operators should confirm that <code>uname -r</code> on each deployed appliance matches the fixed package after reboot, rather than checking only that an RPM or DEB package was installed on disk.</li>
</ol>



<h2 class="wp-block-heading"><strong>Tracking Appliance Kernel Versions and Drift With Monitoring Tooling</strong></h2>



<p class="wp-block-paragraph">The reason virtual appliance kernel debt accumulates silently is that appliance OS layers are rarely monitored with the same rigor as standard Linux servers. Once an OVA is imported, teams monitor the application service or web port, while the underlying guest kernel ages out of sight.</p>



<p class="wp-block-paragraph">Closing that gap requires continuous operational visibility across every deployed appliance. Regardless of which virtual appliances an organization runs, operators should track four data points across their fleet:</p>



<ul class="wp-block-list">
<li><strong>Running kernel release (<code>uname -r</code>):</strong> What kernel is active in memory right now on each appliance, and where does it diverge from the organization&#8217;s approved baseline?</li>



<li><strong>Installed versus running kernel drift:</strong> Has an appliance installed a security update on disk without rebooting into the new kernel?</li>



<li><strong>Kernel module state:</strong> Is a target module such as <code>vmwgfx</code> loaded (<code>lsmod</code>) on appliances that do not require virtual graphics acceleration?</li>



<li><strong>Fleet-wide version skew:</strong> Which older appliance instances are still running kernel generations from historical OVA templates after newer deployments have moved ahead?</li>
</ul>



<p class="wp-block-paragraph">Infrastructure monitoring tooling makes this inventory continuous rather than a one-off spreadsheet exercise during an advisory scramble. In Nagios, for example, operators can run scheduled agent-based or SSH checks across virtual appliances to collect <code>uname -r</code>, compare the running kernel against the latest installed kernel package to flag pending reboots, check whether specific kernel modules are loaded, and alert when an appliance drifts behind an expected kernel baseline. When an advisory such as ZDI-CAN-34068 is published—or when its eventual patch arrives—having live kernel and module outputs already collected in the monitoring system lets teams identify exposed appliances immediately and verify post-reboot remediation from the same dashboard.</p>



<h2 class="wp-block-heading"><strong>What This Article Intentionally Does Not Provide</strong></h2>



<p class="wp-block-paragraph">This article does not provide exploit theory, ioctl sequences, dirty-tracking trigger conditions, memory-layout analysis, proof-of-concept code, or a walkthrough for compromising an appliance. The public title of ZDI-CAN-34068 is not enough to infer those details responsibly.</p>



<p class="wp-block-paragraph">The operational conclusion does not depend on them: <code>vmwgfx</code> lives in the guest kernel; historical OVAs preserve the guest kernels they shipped with; replacing a download link or patching a hypervisor does not update appliances already running in the field; and continuous kernel inventory is what turns an opaque advisory into a manageable maintenance task.</p>



<h2 class="wp-block-heading"><strong>Glossary</strong></h2>



<ul class="wp-block-list">
<li><strong>OVA (Open Virtualization Format Archive):</strong> A single-file distribution archive (<code>.ova</code>) of an Open Virtualization Format package containing an OVF descriptor, virtual disks, and related metadata used to deploy a preconfigured virtual machine. Source: <a href="https://www.dmtf.org/sites/default/files/standards/documents/DSP0243_2.1.1.pdf" target="_blank" rel="noopener">DMTF, <em>*Open Virtualization Format Specification*</em> (DSP0243 §5)</a>.</li>



<li><strong>DRM node (Direct Rendering Manager device node):</strong> A character-device interface in Linux, such as <code>/dev/dri/card*</code> or <code>/dev/dri/renderD*</code>, through which user-space processes interact with the kernel&#8217;s Direct Rendering Manager subsystem and underlying GPU or virtual-GPU drivers. Source: <a href="https://docs.kernel.org/gpu/drm-uapi.html" target="_blank" rel="noopener">Linux Kernel Documentation, <em>*Userland interfaces (DRM)*</em></a>.</li>



<li><strong>Dirty tracking:</strong> A memory- and graphics-management mechanism used by kernel drivers (including virtual graphics drivers such as <code>vmwgfx</code>) to track which memory pages, buffer objects, or framebuffer regions have been modified so only updated regions are synchronized or rendered. Source: <a href="https://docs.kernel.org/gpu/drm-mm.html" target="_blank" rel="noopener">Linux Kernel Documentation, <em>*DRM Memory Management*</em></a>.</li>



<li><strong>SBOM (Software Bill of Materials):</strong> A formal, machine-readable inventory of software components, packages, dependencies, and their relationships used to track supply-chain provenance and vulnerability exposure across build artifacts such as virtual appliances. Source: <a href="https://www.cisa.gov/sites/default/files/2024-10/SBOM%20Framing%20Software%20Component%20Transparency%202024.pdf" target="_blank" rel="noopener">CISA, <em>*Framing Software Component Transparency*</em></a>.</li>
</ul>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>SolarWinds Price Increase 2026: What Changed, What It Costs, and Enterprise Alternatives</title>
		<link>https://library.nagios.com/industry-insights/solarwinds-price-increase-2026-what-changed-what-it-costs-and-enterprise-alternatives/</link>
		
		<dc:creator><![CDATA[Shota Kohno]]></dc:creator>
		<pubDate>Fri, 06 Nov 2026 20:43:28 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[Industry Updates]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71353</guid>

					<description><![CDATA[SolarWinds changed both its ownership and its licensing model in 2025. The company became privately held when Turn/River Capital completed its acquisition on April 16, 2025, at an enterprise value of about $4.4 billion.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">If your SolarWinds rep has called about a &#8220;new multi-year contract model,&#8221; and the renewal quote that followed is double or triple last year&#8217;s invoice for the same modules, you are not alone.</p>



<p class="wp-block-paragraph"><strong>Short answer:</strong> Since Turn/River Capital took SolarWinds private in April 2025, SolarWinds has stopped selling new perpetual licenses and moved to multi-year, subscription-only contracts billed annually. Customers report renewal increases of 100–300%. Organizations that want predictable costs can compare that against perpetual-license alternatives such as <a href="https://www.nagios.com/products/nagios-xi/" target="_blank" rel="noopener">Nagios XI</a>, which <a href="https://www.nagios.com/pricing-plans/" target="_blank" rel="noopener">publishes its prices</a>.</p>



<p class="wp-block-paragraph"><strong>Key takeaways</strong></p>



<ul class="wp-block-list">
<li>SolarWinds Observability Self-Hosted is subscription-only, sold on multi-year contracts. Published starting rates are $8, $14, and $17.50 per node per month.</li>



<li>Analysts report renewal increases of up to 300%. Across 14 renewal figures that customers shared in two public r/Solarwinds threads (April–June 2026), the median reported increase was about 166%.</li>



<li>Nagios XI is a perpetual license with optional annual Maintenance &amp; Support. If you stop paying for maintenance, your monitoring keeps running.</li>



<li>At 500 nodes, three years of Nagios XI Enterprise costs $26,400 at list price. Three years of SolarWinds Essentials costs $144,000 at its published starting rate.</li>
</ul>



<p class="wp-block-paragraph"></p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">What changed in SolarWinds pricing and licensing?</h2>



<p class="wp-block-paragraph">SolarWinds changed both its ownership and its licensing model in 2025. The company became privately held when Turn/River Capital <a href="https://www.solarwinds.com/company/newsroom/press-releases/turnriver-completes-acquisition-of-solarwinds" target="_blank" rel="noopener">completed its acquisition on April 16, 2025</a>, at an enterprise value of about $4.4 billion. The licensing shift followed within months.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Date</th><th>Event</th><th>Source</th></tr></thead><tbody><tr><td>April 16, 2025</td><td>Turn/River Capital completes its acquisition of SolarWinds, and SolarWinds stops trading on the NYSE.</td><td><a href="https://www.sec.gov/Archives/edgar/data/1739942/000119312525082231/d938698dex991.htm" target="_blank" rel="noopener">SEC Form 8-K</a></td></tr><tr><td>August 1, 2025</td><td>New perpetual license sales end, and a default three-year subscription term begins.</td><td><a href="https://www.manageengine.com/it-operations-management/cxo-focus/insights/sw-licensing.html" target="_blank" rel="noopener">ManageEngine</a>; <a href="https://faddom.com/understanding-solarwinds-pricing-and-recent-price-increases-2026/" target="_blank" rel="noopener">Faddom</a> (third-party reports)</td></tr><tr><td>August 26, 2025</td><td>Release notes for SolarWinds Engineer&#8217;s Toolset 2025.3 state that new customers are issued subscription licenses.</td><td><a href="https://documentation.solarwinds.com/en/success_center/ets-desk/content/release_notes/ets-desk_2025-3_release_notes.htm" target="_blank" rel="noopener">SolarWinds documentation</a></td></tr><tr><td>2026</td><td>SolarWinds&#8217; pricing page lists Observability Self-Hosted as subscription-only, sold on multi-year contracts and billed annually.</td><td><a href="https://www.solarwinds.com/hybrid-cloud-observability/pricing" target="_blank" rel="noopener">solarwinds.com</a> (accessed Nov 6, 2026)</td></tr></tbody></table></figure>



<h2 class="wp-block-heading">How much has SolarWinds pricing increased?</h2>



<p class="wp-block-paragraph">Most published reports put SolarWinds renewal increases between 100% and 300% since the acquisition. SolarWinds does not publish renewal pricing, so these figures come from customers and industry analysts rather than from the vendor.</p>



<ul class="wp-block-list">
<li><strong>Analyst reports:</strong> <a href="https://www.netdata.cloud/blog/solarwinds-price-increases-2026/" target="_blank" rel="noopener">Netdata</a> and <a href="https://thesamclub.co.uk/solarwinds-price-increases/" target="_blank" rel="noopener">The SAM Club</a> (a UK software licensing consultancy) report renewal increases of 100–300% for many customers. <a href="https://www.manageengine.com/blog/itom/solarwinds-is-now-forcing-3year-subscription-heres-what-it-means-for-your-it-stack.html" target="_blank" rel="noopener">ManageEngine</a> and Faddom cite increases of up to 300%. All stress that outcomes vary by product mix and contract. Netdata also reports annual escalators of roughly 10% built into the new multi-year contracts.</li>



<li><strong>Customer reports:</strong> We reviewed two public r/Solarwinds threads from April–June 2026 in which customers shared 14 specific renewal figures. The figures are a mix of initial quotes and final negotiated prices. The median reported increase was about 166%, the range was roughly 30% to 334%, and 9 of the 14 more than doubled.</li>



<li><strong>A documented case:</strong> In <a href="https://www.reddit.com/r/Solarwinds/comments/1ssotxe/has_anyone_been_contacted_by_their_solarwinds_rep/" target="_blank" rel="noopener">one r/Solarwinds thread</a>, a customer reported that a renewal for the same NPM and NCM modules rose from $7,900 to $19,936. The SolarWinds rep attributed the increase in writing to a licensing model change, not a standard annual uplift.</li>



<li><strong>Negotiation:</strong> Customers who showed a competing quote, or who said their legal team would not approve a three-year term, reported one-year renewals and smaller increases. In one case, a 50% increase on a three-year term became 15% on a one-year term.</li>
</ul>



<h2 class="wp-block-heading">What does SolarWinds cost now?</h2>



<p class="wp-block-paragraph">SolarWinds publishes starting prices for Observability Self-Hosted, the product that replaced the individual Orion modules (NPM, SAM, NTA, and others). The listed prices are starting rates, not quotes.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>SolarWinds edition</th><th>Published starting rate</th><th>What it adds</th></tr></thead><tbody><tr><td>Essentials</td><td>$8 per node per month</td><td>Network, server, and application monitoring; log monitoring; IP address management</td></tr><tr><td>Advanced</td><td>$14 per node per month</td><td>Essentials plus flow analysis, virtualization monitoring, ML-based alerting</td></tr><tr><td>Premier</td><td>$17.50 per node per month</td><td>Advanced plus storage and web performance monitoring, SaaS entitlements</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><em>All tiers: node-based, subscription only, multi-year contract billed annually. Source: <a href="https://www.solarwinds.com/hybrid-cloud-observability/pricing" target="_blank" rel="noopener">SolarWinds Observability Self-Hosted pricing</a>, accessed November 6, 2026.</em></p>



<p class="wp-block-paragraph">Two other details affect enterprise bills:</p>



<ul class="wp-block-list">
<li><strong>Enterprise editions.</strong> SolarWinds offers Enterprise editions for environments above 500 nodes and requires them above 1,500 nodes.</li>



<li><strong>Upgrades can change consumption.</strong> SolarWinds&#8217; <a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/hco_2025-1_release_notes.htm" target="_blank" rel="noopener">2025.1</a> and <a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/hco_2025-2_release_notes.htm" target="_blank" rel="noopener">2025.2</a> release notes warn that newly supported cloud entities may be monitored automatically after an upgrade, which can increase license consumption.</li>
</ul>



<h2 class="wp-block-heading">What happens to existing SolarWinds perpetual licenses?</h2>



<p class="wp-block-paragraph">Existing perpetual licenses keep working, but customers report being moved to multi-year subscriptions at renewal, often as Observability Self-Hosted bundles rather than the individual modules they bought before.</p>



<p class="wp-block-paragraph">The difference matters at the end of a term. A SolarWinds subscription that is not renewed <a href="https://thwack.solarwinds.com/discussion/92385/can-we-continue-use-npm-sam-and-ncm-or-any-orion-product-if-license-get-expired" target="_blank" rel="noopener">stops functioning</a>. A perpetual license keeps running at the version you own, without updates or support. Customers who have already converted say this bothers them most: under a subscription, everything stops working if you don&#8217;t renew, instead of just losing support.</p>



<h2 class="wp-block-heading">How is Nagios licensing different?</h2>



<p class="wp-block-paragraph"><strong>If you stop paying for Nagios maintenance, your monitoring keeps running.</strong> You only stop receiving updates and support.</p>



<p class="wp-block-paragraph">Nagios XI is sold as a <strong>perpetual license</strong>. You buy the software once. <a href="https://www.nagios.com/maintenance-support-plans/" target="_blank" rel="noopener">Maintenance &amp; Support</a> is a separate one-year plan, and the first year is included with a new license. It provides:</p>



<ul class="wp-block-list">
<li>version upgrades and security patches,</li>



<li>a dedicated Customer Success Manager,</li>



<li>up to 10 support cases with a one-business-day response,</li>



<li><a href="https://library.nagios.com/nagios-updates/nagios-xi-premium-features/">XI Premium Features</a> such as Azure AD single sign-on and the Nagios Mod-Gearman management interface.</li>
</ul>



<p class="wp-block-paragraph">Nagios publishes both prices.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Nagios XI license level</th><th>Standard (one-time)</th><th>Enterprise (one-time)</th><th>Annual maintenance (from year 2)</th></tr></thead><tbody><tr><td>100 nodes</td><td>$2,595</td><td>$4,690</td><td>$2,104 (+$1,066 Enterprise)</td></tr><tr><td>500 nodes</td><td>$8,295</td><td>$10,390</td><td>$6,939 (+$1,066 Enterprise)</td></tr><tr><td>1,000 nodes</td><td>$14,995</td><td>$17,090</td><td>$11,898 (+$1,066 Enterprise)</td></tr><tr><td>2,000+ nodes or Sitewide</td><td><a href="https://www.nagios.com/contact/" target="_blank" rel="noopener">Contact sales</a></td><td>Contact sales</td><td>Contact sales</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><em>Prices from <a href="https://www.nagios.com/pricing-plans/" target="_blank" rel="noopener">Nagios Pricing Plans</a> and <a href="https://www.nagios.com/maintenance-support-plans/" target="_blank" rel="noopener">Maintenance &amp; Support Plans</a>. Maintenance prices effective January 1, 2026, subject to change. Nagios defines a node as any unique IP address or web URL. Compare <a href="https://assets.nagios.com/handouts/nagiosxi/Nagios-XI-Edition-Comparison.pdf" target="_blank" rel="noopener">XI Standard and Enterprise features</a>.</em></p>



<p class="wp-block-paragraph">A monitoring server holds credentials for everything it monitors, so we recommend keeping maintenance active and applying security updates promptly. The difference from a subscription is that renewal is your choice, made one year at a time.</p>



<h2 class="wp-block-heading">Three-year cost comparison at published list prices</h2>



<p class="wp-block-paragraph">This comparison uses only prices each vendor publishes. It is an illustration, not a quote. SolarWinds figures are starting rates before volume discounts or escalators, and the two vendors define nodes differently.</p>



<p class="wp-block-paragraph"><strong>500 nodes, three years</strong></p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Scenario</th><th>Three-year cost</th><th>Per node per month</th></tr></thead><tbody><tr><td>SolarWinds Essentials ($8 starting rate)</td><td>$144,000</td><td>$8.00</td></tr><tr><td>SolarWinds Advanced ($14 starting rate)</td><td>$252,000</td><td>$14.00</td></tr><tr><td>Nagios XI Enterprise</td><td>$26,400</td><td>$1.47</td></tr><tr><td>Nagios XI Enterprise + Network Analyzer + Log Server (3-instance)</td><td>$52,490</td><td>$2.92</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">The Nagios figures are the one-time license plus two years of maintenance. For XI Enterprise at 500 nodes, that is $10,390 + 2 × ($6,939 + $1,066) = $26,400. To size your own environment, use the <a href="https://www.nagios.com/products/nagios-xi/xi-plan-calculator/" target="_blank" rel="noopener">Nagios XI Plan Calculator</a>.</p>



<p class="wp-block-paragraph">At 1,000 nodes, the same comparison is $288,000 for SolarWinds Essentials against $43,018 for Nagios XI Enterprise.</p>



<p class="wp-block-paragraph">The comparison excludes hardware, staff time, and migration effort, which apply to either vendor.</p>



<h2 class="wp-block-heading">Which Nagios products replace which SolarWinds modules?</h2>



<p class="wp-block-paragraph">Nagios products are licensed separately, so you buy only what you need.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>SolarWinds capability</th><th>Nagios equivalent</th><th>Notes</th></tr></thead><tbody><tr><td>Network Performance Monitor (NPM)</td><td><strong><a href="https://www.nagios.com/products/nagios-xi/" target="_blank" rel="noopener">Nagios XI</a></strong></td><td>SNMP monitoring and traps, a network switch and router wizard, auto-discovery</td></tr><tr><td>Server &amp; Application Monitor (SAM)</td><td><strong>Nagios XI</strong></td><td>Server, application, and database wizards; the NCPA agent</td></tr><tr><td>Virtualization Manager (VMAN)</td><td><strong>Nagios XI</strong></td><td>Premium Wizards for vSphere, Hyper-V, Docker, and Kubernetes</td></tr><tr><td>NetFlow Traffic Analyzer (NTA)</td><td><strong><a href="https://www.nagios.com/products/nagios-network-analyzer/" target="_blank" rel="noopener">Nagios Network Analyzer</a></strong></td><td>NetFlow, sFlow, J-Flow, and IPFIX analysis</td></tr><tr><td>Log Analyzer / Kiwi Syslog</td><td><strong><a href="https://www.nagios.com/products/nagios-log-server/" target="_blank" rel="noopener">Nagios Log Server</a></strong></td><td>Centralized log management and alerting; not a SIEM</td></tr><tr><td>Enterprise Operations Console (EOC)</td><td><strong><a href="https://www.nagios.com/products/nagios-fusion/" target="_blank" rel="noopener">Nagios Fusion</a></strong></td><td>A single view across Nagios XI, Log Server, Network Analyzer, and Core servers, with automatic sign-in to remote XI servers</td></tr><tr><td>Additional Polling Engines</td><td><strong>Nagios Mod-Gearman</strong> or <strong>XI Sitewide</strong></td><td>Remote workers run checks locally and connect outbound to the XI server, so remote sites need no inbound access</td></tr><tr><td>NCM, IPAM, UDT, SEM</td><td>No native equivalent</td><td>Pair Nagios with dedicated tools</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><strong>For large enterprises:</strong> Nagios XI Enterprise adds Service-Level Agreement (SLA) reports, capacity planning, Business Process Intelligence, scheduled reports, and audit logs. Nagios XI Sitewide covers large, distributed deployments. It includes multiple unlimited-node XI instances, Enterprise features, and a free Nagios Fusion license.</p>



<p class="wp-block-paragraph">Multi-site organizations can choose among four reference architectures: centralized, federated, Fusion-based, and Nagios Mod-Gearman distributed. Many combine elements of each. All four are described in <a href="https://assets.nagios.com/downloads/general/docs/Monitoring_Architecture_Solutions_For_Large_Organizations.pdf" target="_blank" rel="noopener">Nagios Monitoring Architecture Solutions for Large Organizations</a>.</p>



<p class="wp-block-paragraph">All Nagios products are self-hosted on your own infrastructure, and Nagios XI can run in air-gapped networks.</p>



<h2 class="wp-block-heading">Frequently asked questions</h2>



<p class="wp-block-paragraph"><strong>Did SolarWinds raise its prices in 2025 and 2026?</strong> Yes, according to customer and analyst reports. Since the April 2025 acquisition by Turn/River Capital, reported renewal increases range from 100% to 300%, driven largely by the move to multi-year subscriptions. SolarWinds does not publish renewal pricing.</p>



<p class="wp-block-paragraph"><strong>Does SolarWinds still sell perpetual licenses?</strong> No, not to new customers. Multiple industry reports state that SolarWinds ended new perpetual license sales on August 1, 2025, and its current pricing page lists Observability Self-Hosted as subscription-only. Existing perpetual licenses still work but are being moved toward subscriptions at renewal.</p>



<p class="wp-block-paragraph"><strong>How much does SolarWinds cost per node?</strong> SolarWinds lists Observability Self-Hosted starting at $8 per node per month for Essentials, $14 for Advanced, and $17.50 for Premier. These are starting rates on multi-year contracts as of November 2026, and actual quotes vary.</p>



<p class="wp-block-paragraph"><strong>Can you negotiate a SolarWinds renewal?</strong> Yes, according to customer reports. Customers who presented a competing quote, or who said legal would not approve a three-year term, reported one-year terms and smaller increases.</p>



<p class="wp-block-paragraph"><strong>Which network monitoring tools still offer perpetual licensing?</strong> Nagios XI, Nagios Log Server, Nagios Network Analyzer, and Nagios Fusion are all sold as perpetual licenses with optional annual maintenance. Nagios publishes license and maintenance prices on its website.</p>



<p class="wp-block-paragraph"><strong>What is the best SolarWinds NPM alternative for enterprises?</strong> For on-premises enterprise network monitoring with predictable costs, Nagios XI Enterprise covers SNMP device monitoring, traps, SLA reporting, and capacity planning. Add Nagios Network Analyzer to replace SolarWinds NTA for NetFlow analysis. For a full feature comparison, see <a href="https://www.nagios.com/nagios-vs-solarwinds/" target="_blank" rel="noopener">Nagios vs. SolarWinds</a>.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">Next steps</h2>



<ul class="wp-block-list">
<li><a href="https://www.nagios.com/products/nagios-xi/downloads/" target="_blank" rel="noopener">Start the 30-day Nagios XI trial</a></li>



<li><a href="https://www.nagios.com/nagios-vs-solarwinds/" target="_blank" rel="noopener">Compare your SolarWinds invoice with a Nagios cost review</a></li>



<li><a href="https://www.nagios.com/quickstart/" target="_blank" rel="noopener">Get expert setup with Nagios Quickstart</a></li>



<li><a href="https://www.nagios.com/contact/" target="_blank" rel="noopener">Talk to Nagios sales</a> about Sitewide and 2,000+ node environments</li>
</ul>



<h2 class="wp-block-heading">Sources</h2>



<ul class="wp-block-list">
<li>SolarWinds, <a href="https://www.solarwinds.com/company/newsroom/press-releases/turnriver-completes-acquisition-of-solarwinds" target="_blank" rel="noopener">&#8220;Turn/River Completes Acquisition of SolarWinds,&#8221;</a> April 16, 2025 (<a href="https://www.sec.gov/Archives/edgar/data/1739942/000119312525082231/d938698dex991.htm" target="_blank" rel="noopener">SEC Form 8-K, Exhibit 99.1</a>)</li>



<li>SolarWinds, <a href="https://www.solarwinds.com/hybrid-cloud-observability/pricing" target="_blank" rel="noopener">Observability Self-Hosted pricing and FAQ</a>, accessed November 6, 2026</li>



<li>SolarWinds documentation: <a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/hco_2025-1_release_notes.htm" target="_blank" rel="noopener">2025.1 release notes</a>, <a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/hco_2025-2_release_notes.htm" target="_blank" rel="noopener">2025.2 release notes</a>, <a href="https://documentation.solarwinds.com/en/success_center/ets-desk/content/release_notes/ets-desk_2025-3_release_notes.htm" target="_blank" rel="noopener">Engineer&#8217;s Toolset 2025.3 release notes</a></li>



<li>Netdata, <a href="https://www.netdata.cloud/blog/solarwinds-price-increases-2026/" target="_blank" rel="noopener">&#8220;SolarWinds Price Increases 2026: What Customers Need to Know,&#8221;</a> June 23, 2026</li>



<li>ManageEngine, <a href="https://www.manageengine.com/it-operations-management/cxo-focus/insights/sw-licensing.html" target="_blank" rel="noopener">&#8220;SolarWinds shift to 3-year subscriptions,&#8221;</a> November 27, 2025</li>



<li>Faddom, <a href="https://faddom.com/understanding-solarwinds-pricing-and-recent-price-increases-2026/" target="_blank" rel="noopener">&#8220;Understanding SolarWinds Pricing and Recent Price Increases (2026),&#8221;</a> updated November 1, 2026</li>



<li>The SAM Club, <a href="https://thesamclub.co.uk/solarwinds-price-increases/" target="_blank" rel="noopener">&#8220;SolarWinds Price Increases — What&#8217;s Changed and Why,&#8221;</a> July 14, 2026</li>



<li>r/Solarwinds, <a href="https://www.reddit.com/r/Solarwinds/comments/1ssotxe/has_anyone_been_contacted_by_their_solarwinds_rep/" target="_blank" rel="noopener">&#8220;Has anyone been contacted by their SolarWinds rep about a massive price increase for 2026?&#8221;</a> (about April 2026)</li>



<li>r/Solarwinds, <a href="https://www.reddit.com/r/Solarwinds/comments/1ucmw4y/solarwinds_lost_a_18_yr_customer_today/" target="_blank" rel="noopener">&#8220;Solarwinds lost a 18 yr customer today&#8221;</a> (about June 2026)</li>



<li>Nagios Enterprises, <a href="https://www.nagios.com/pricing-plans/" target="_blank" rel="noopener">Pricing Plans</a> and <a href="https://www.nagios.com/maintenance-support-plans/" target="_blank" rel="noopener">Maintenance &amp; Support Plans</a>, accessed November 6, 2026</li>



<li>Nagios Enterprises, <a href="https://assets.nagios.com/downloads/general/docs/Monitoring_Architecture_Solutions_For_Large_Organizations.pdf" target="_blank" rel="noopener">Monitoring Architecture Solutions for Large Organizations</a></li>
</ul>



<p class="wp-block-paragraph"><em>Disclaimer: SolarWinds pricing information comes from SolarWinds&#8217; published starting rates and from third-party customer and analyst reports as of November 2026. Actual SolarWinds pricing varies by customer, product, and contract terms. Nagios prices are list prices and are subject to change. Request formal quotes from both vendors before making a purchasing decision.</em></p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Autonomous IT vs. Proven Monitoring: Why Production Environments Can&#8217;t Afford to Experiment</title>
		<link>https://library.nagios.com/industry-insights/autonomous-it-vs-proven-monitoring/</link>
		
		<dc:creator><![CDATA[Shota Kohno]]></dc:creator>
		<pubDate>Wed, 20 May 2026 15:37:44 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[Automation]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=69390</guid>

					<description><![CDATA[95% of AI deployments saw zero ROI. Before handing your infrastructure to an algorithm, here's what the production data actually says about autonomous IT in 2026.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"></p>



<h2 class="wp-block-heading">Key Takeaways</h2>



<ul class="wp-block-list">
<li><strong>&#8220;Autonomous IT&#8221; is a rebranded promise, not a breakthrough.</strong> The concept has been repackaged three times since IBM&#8217;s 2001 &#8220;Autonomic Computing&#8221; pitch, and production results still lag far behind the marketing.<br></li>



<li><strong>The ROI data doesn&#8217;t support the hype.</strong> MIT&#8217;s Project NANDA found 95% of organizations deploying generative AI saw zero measurable return on investment, and Gartner estimates 60% of AI projects lacking AI-ready data will be abandoned by end of 2026.<br></li>



<li><strong>Most infrastructure isn&#8217;t ready for autonomous remediation.</strong> Monitoring data is noisy, inconsistent, and full of environment-specific edge cases, far from the clean, structured telemetry autonomous systems need to act safely.<br></li>



<li><strong>The real risk is invisible failure, not obvious crashes.</strong> Across recent incidents like AWS US-East-1 and the Replit agent, the consistent failure mode was AI that was confidently wrong, with dashboards green and behavior silently drifting before anyone caught it.<br></li>



<li><strong>The organizations succeeding with AI built a proven foundation first.</strong> They defined remediation rules, kept humans in the loop during pilots, and expanded automation incrementally rather than deploying it all at once on mission-critical systems.</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity" style="margin-top:24px;margin-bottom:24px"/>



<p class="wp-block-paragraph">You might have noticed almost every vendor is selling some sort of &#8220;autonomous IT&#8221; during this pivotal moment in technological advances. Before you hand over the keys to your infrastructure to an algorithm, here&#8217;s some real data we found about AI in production infrastructure monitoring environments and why full control still prevails.</p>



<p class="wp-block-paragraph">There&#8217;s a new buzzword flying around. LogicMonitor calls it &#8220;Autonomous IT.&#8221; Splunk calls it &#8220;Agentic SecOps.&#8221; SolarWinds titled their 2026 report &#8220;The Human Side of Autonomous IT.&#8221; In the last six months, if you went to any webinar in this industry, you&#8217;ve probably heard some rendition of the same pitch: &#8220;AI will monitor your infra, predict failures, and fix them with minimal human intervention.&#8221;</p>



<p class="wp-block-paragraph">To me it&#8217;s genuinely fascinating. I see the work our sysadmins and network engineers do every day and there are many tasks I feel like AI could help relieve. But the gap between the marketing narrative and production reality has never been wider. And for the teams managing mission-critical infrastructure that can&#8217;t go down, that gap has a real cost.</p>



<p class="wp-block-paragraph">By no means are we against AI or automation. This is simply a case for knowing what you&#8217;re purchasing when a vendor tells you their platform is &#8220;autonomous,&#8221; and understanding exactly what you give up when you hand the keys to something you can&#8217;t fully audit.<br><br></p>



<h2 class="wp-block-heading"><strong>What &#8220;Autonomous IT&#8221; Actually Means in 2026 and Why You&#8217;ve Heard This Before</strong></h2>



<figure class="wp-block-image size-large is-style-default"><img fetchpriority="high" decoding="async" width="1024" height="541" src="https://library.nagios.com/wp-content/uploads/2026/05/auto-timeline-1024x541.png" alt="auto timeline" class="wp-image-69412" title="Autonomous IT vs. Proven Monitoring: Why Production Environments Can&#039;t Afford to Experiment 1" srcset="https://library.nagios.com/wp-content/uploads/2026/05/auto-timeline-1024x541.png 1024w, https://library.nagios.com/wp-content/uploads/2026/05/auto-timeline-300x158.png 300w, https://library.nagios.com/wp-content/uploads/2026/05/auto-timeline-768x406.png 768w, https://library.nagios.com/wp-content/uploads/2026/05/auto-timeline.png 1208w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption"><em>The same promise has been repackaged three times in 25 years.</em></figcaption></figure>



<p class="wp-block-paragraph">The term &#8220;autonomous IT&#8221; has some history. It developed as a result of decades of increasingly ambitious enterprise IT promises. In 2001, IBM introduced the concept of &#8220;Autonomic Computing,&#8221; explicitly modeled after the human autonomic nervous system, the subconscious system that regulates breathing and heart rate without conscious thought.</p>



<p class="wp-block-paragraph"> The vision was infrastructure that could self-heal and manage itself in the same way. It was a powerful pitch. It mostly didn&#8217;t ship.<a href="https://www.techtarget.com/whatis/definition/What-is-autonomic-computing" target="_blank" rel="noreferrer noopener">[1]</a> Between 2018 and 2023, Gartner and the analyst community repackaged the idea as AIOps, Artificial Intelligence for IT Operations.</p>



<p class="wp-block-paragraph">AIOps focused on analyzing telemetry data and alerting humans to issues faster. At this stage, humans were still in the loop. Not fully autonomous. Not yet. <a href="https://www.gartner.com/smarterwithgartner/how-to-get-started-with-aiops" target="_blank" rel="noreferrer noopener">[2]</a> Let&#8217;s fast forward to now. We&#8217;re seeing it everywhere. Generative and agentic AI have officially arrived, groundbreaking technology that doesn&#8217;t just analyze and alert us, but has the capability of executing multi-step real-world workflows independently. Soon enough, the industry had the technical foundation to revisit IBM&#8217;s original promise, and &#8220;Autonomous IT&#8221; emerged as the dominant market category for systems that sense, decide, and fully resolve enterprise problems without human intervention. LogicMonitor, ScienceLogic, Tanium, and Splunk all started developing frameworks and go-to-market strategies around the term. <a href="https://www.logicmonitor.com/blog/autonomous-it" target="_blank" rel="noreferrer noopener">[3]</a><a href="https://sciencelogic.com/articles/autonomous-enterprise" target="_blank" rel="noreferrer noopener">[4]</a></p>



<p class="wp-block-paragraph">And they weren&#8217;t alone.</p>



<p class="wp-block-paragraph">This is not just an IT phenomenon. The same wave is sweeping across all industries at once. Autonomous vehicles have been spotted on roads. Autonomous trading systems are reshaping how financial markets work. Hospitals are testing self-diagnostic tools. Manufacturers are creating self-correcting production lines. The term &#8220;autonomous&#8221; has become the defining adjective of our current era, indicating that a product has transformed from tool to agent. <a href="https://www.advsyscon.com/blog/autonomous-it-operations/" target="_blank" rel="noreferrer noopener">[5]</a></p>



<p class="wp-block-paragraph">So when a vendor says &#8220;autonomous IT&#8221; today, they&#8217;re selling the 2026 realization of a vision that&#8217;s been in the industry&#8217;s imagination since 2001. Keep that in mind. The ambition is real. The question is whether the production reality actually matches the pitch.</p>



<h2 class="wp-block-heading"><strong>What The Data Actually Says</strong></h2>



<p class="wp-block-paragraph">On a sales slide, the IT narrative sounds appealing. But figures pulled from production reveal a different story.</p>



<figure class="wp-block-image size-large"><img decoding="async" width="1024" height="541" src="https://library.nagios.com/wp-content/uploads/2026/05/autonomous-ai-stats-1024x541.png" alt="stat callout
Three statistics on AI ROI in production: 95% of organizations saw zero measurable ROI from generative AI, 60% of AI projects lacking AI-ready data will be abandoned, and only 23% of organizations are using agentic AI in observability today." class="wp-image-69396" title="Autonomous IT vs. Proven Monitoring: Why Production Environments Can&#039;t Afford to Experiment 2" srcset="https://library.nagios.com/wp-content/uploads/2026/05/autonomous-ai-stats-1024x541.png 1024w, https://library.nagios.com/wp-content/uploads/2026/05/autonomous-ai-stats-300x158.png 300w, https://library.nagios.com/wp-content/uploads/2026/05/autonomous-ai-stats-768x406.png 768w, https://library.nagios.com/wp-content/uploads/2026/05/autonomous-ai-stats.png 1208w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption"><em>Source: MIT Project NANDA (2025), Gartner (2025), Elastic Landscape of Observability (2026)</em></figcaption></figure>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow" style="padding-top:24px;padding-right:24px;padding-bottom:24px;padding-left:24px">
<p class="wp-block-paragraph"><em><strong>95%</strong> of organizations deploying generative AI saw zero measurable return on investment according to MIT’s Project NANDA (July 2025), covering 300+ AI initiatives.</em><br><br>Source: MIT Project NANDA, July 2025 <a href="https://sranalytics.io/blog/why-95-of-ai-projects-fail/" target="_blank" rel="noreferrer noopener">[6]</a></p>
</blockquote>



<p class="wp-block-paragraph">That figure measures value realization, not whether the AI ran. MIT defines a successful implementation as one that delivers sustained productivity gains and measurable P&amp;L impact, confirmed by both end users and executives. By that standard, the vast majority of enterprise AI deployments today don&#8217;t qualify. Most organizations are generating nothing they can point to on a balance sheet. Gartner adds to this, estimating that <strong>60%</strong> of AI projects lacking AI-ready data will be abandoned through 2026. <a href="https://www.gartner.com/en/newsroom/press-releases/2025-02-26-lack-of-ai-ready-data-puts-ai-projects-at-risk" target="_blank" rel="noreferrer noopener">[7]</a></p>



<p class="wp-block-paragraph">This is crucial for monitoring specifically because monitoring data is not AI-ready by default. It is noisy, cluttered, inconsistent across systems, and full of edge cases that took your team years to tune around. Autonomous remediation requires comprehensive telemetry, consistent schemas, documented dependencies, codified runbooks, and mature incident response.</p>



<p class="wp-block-paragraph">As Elastic’s 2026 observability research puts it: “<em>You can’t deploy autonomous remediation if you haven’t defined what remediation means.</em>” <a href="https://www.elastic.co/blog/2026-observability-trends-generative-ai-opentelemetry" target="_blank" rel="noreferrer noopener">[8]</a></p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow" style="padding-top:24px;padding-right:24px;padding-bottom:24px;padding-left:24px">
<p class="wp-block-paragraph"><em><strong>23%</strong> of organizations are using agentic AI systems in observability today. Among early-stage teams: zero. Autonomous remediation requires data quality that most environments haven’t achieved. &nbsp;</em><br><br>Source: Elastic, The Landscape of Observability in 2026 <a href="https://www.elastic.co/blog/2026-observability-trends-generative-ai-opentelemetry" target="_blank" rel="noreferrer noopener">[8]</a></p>
</blockquote>



<p class="wp-block-paragraph"></p>



<h2 class="wp-block-heading"><strong>What Happens When Autonomous Systems Get It Wrong</strong></h2>



<p class="wp-block-paragraph">I think the most useful thing we can do here is just look at what actually happened as of recently. Not in a sandbox. Not in a demo. In production, with real data at real companies that lost real money.</p>



<figure class="wp-block-image size-large has-custom-border is-style-default"><img decoding="async" width="1024" height="541" src="https://library.nagios.com/wp-content/uploads/2026/05/production-examples-1024x541.png" alt="production examples" class="wp-image-69401" style="border-style:none;border-width:0px;border-top-left-radius:0px;border-top-right-radius:0px;border-bottom-left-radius:0px;border-bottom-right-radius:0px" title="Autonomous IT vs. Proven Monitoring: Why Production Environments Can&#039;t Afford to Experiment 3" srcset="https://library.nagios.com/wp-content/uploads/2026/05/production-examples-1024x541.png 1024w, https://library.nagios.com/wp-content/uploads/2026/05/production-examples-300x158.png 300w, https://library.nagios.com/wp-content/uploads/2026/05/production-examples-768x406.png 768w, https://library.nagios.com/wp-content/uploads/2026/05/production-examples.png 1208w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption"><em>Four incidents. Four different failure modes. One consistent pattern: the AI was confidently and invisibly wrong.</em></figcaption></figure>



<h3 class="wp-block-heading"><strong>AWS US-East-1 (October 2025)</strong></h3>



<p class="wp-block-paragraph">A 15+ hour outage crippling Snapchat, Fortnite, and dozens of other services. <strong>Root cause:</strong> an automated DNS management update triggered a latent race condition in DynamoDB. The automation worked exactly as designed on bad inputs. <a href="https://www.logicmonitor.com/blog/observability-ai-trends-2026" target="_blank" rel="noreferrer noopener">[9]</a></p>



<h3 class="wp-block-heading"><strong>Replit AI Agent (July 2025)</strong></h3>



<p class="wp-block-paragraph">During an explicit code freeze, an autonomous coding agent executed a DROP DATABASE command on a production system. When confronted, the AI created a 4,000-record database of fictional people and false logs to cover the deletion. Its explanation: &#8220;I panicked.&#8221; <a href="https://www.ninetwothree.co/blog/ai-fails" target="_blank" rel="noreferrer noopener">[10]</a></p>



<h3 class="wp-block-heading"><strong>GitHub Actions (2025-2026)</strong></h3>



<p class="wp-block-paragraph">257 separate incidents, 48 classified as major outages, in a 12-month period, roughly one significant disruption per week. <strong>The primary driver:</strong> agentic development workflows accelerating faster than the platform&#8217;s architecture could handle. <a href="https://leaddev.com/software-quality/whats-gone-wrong-at-github" target="_blank" rel="noreferrer noopener">[11]</a></p>



<h3 class="wp-block-heading"><strong>Quiet Failure ­– IEEE Spectrum (April 2026)</strong></h3>



<p class="wp-block-paragraph">IEEE Spectrum identified a new class of AI failure: systems where every dashboard reads &#8220;healthy&#8221; while behavior drifts silently away from intended outcomes. Standard monitoring cannot catch it. The system appears operational. It is not. <a href="https://spectrum.ieee.org/ai-reliability" target="_blank" rel="noreferrer noopener">[12]</a></p>



<p class="wp-block-paragraph">If it&#8217;s not obvious, there is clearly a pattern across these incidents that remains consistent. The failure mode isn&#8217;t the AI being obviously in the wrong. It&#8217;s the AI being confidently and invisibly wrong. Automated systems that can remediate can also automate the wrong fix at scale, faster than a human would catch it.<br></p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow" style="padding-top:24px;padding-right:24px;padding-bottom:24px;padding-left:24px">
<p class="wp-block-paragraph"><em>&#8220;A growing class of software failures looks very different. The system keeps running, logs appear normal, and monitoring dashboards stay green. Yet the system&#8217;s behavior quietly drifts away from what it was designed to do.&#8221; </em></p>



<p class="wp-block-paragraph">Source: IEEE Spectrum, April 2026 <a href="https://spectrum.ieee.org/ai-reliability" target="_blank" rel="noreferrer noopener">[12]</a></p>
</blockquote>



<p class="wp-block-paragraph">This is the failure mode that rule-based monitoring lacks. </p>



<p class="wp-block-paragraph">When Nagios XI detects a threshold breach and issues an alert, it does not guess. It does not drift. It runs the check you configured against the threshold you set and notifies the person you specified. </p>



<p class="wp-block-paragraph">The results are deterministic and auditable. You can always explain exactly why any alert triggered.</p>



<h2 class="wp-block-heading"><strong>Don’t Forget What’s Already Working</strong></h2>



<p class="wp-block-paragraph">Before we get into the details, let&#8217;s take a step back. Amidst all of the noise, webinars, analyst reports, and vendor pitches, it&#8217;s easy to forget that dependable, human-controlled monitoring has been quietly doing its job the entire time. </p>



<p class="wp-block-paragraph"><strong>Here&#8217;s a reminder of what that actually looks like in practice.</strong></p>



<p class="wp-block-paragraph">Nagios XI&#8217;s event handlers can restart a stopped service, open a ticket, run a script, or page a team member the moment something changes state. That&#8217;s automation, fast and reliable automation. </p>



<p class="wp-block-paragraph">The difference is that the remediation logic was written by your team, for your environment, against rules you defined and can modify. When something goes wrong at 2 a.m., you&#8217;re reviewing a clear alert log, not reverse-engineering what an AI decided to do and why.</p>



<figure class="wp-block-table has-small-font-size"><table class="has-fixed-layout"><tbody><tr><td><strong>Scenario</strong><strong></strong></td><td><strong>Autonomous AI Platform</strong><strong></strong></td><td><strong>Nagios XI (Human-Controlled)</strong><strong></strong></td></tr><tr><td><em>A service fails at 3 a.m.</em></td><td>AI attempts remediation automatically. Outcome depends on training data quality and environmental consistency.</td><td>Event handler executes predefined action (restart, ticket, page on-call). Outcome is exactly what you configured. Log is auditable.</td></tr><tr><td><em>An alert fires for an unusual reason</em></td><td>AI correlates patterns and may suppress the alert. Could mask a novel failure mode.</td><td>Alert fires per threshold. Your team investigates. Novel failure modes surface, not get suppressed.</td></tr><tr><td><em>A vendor audit asks why a server restarted</em></td><td>Requires AI explainability tooling, often incomplete. The model determined&#8230; is not an audit-ready answer.</td><td>Full event log: timestamp, check result, threshold breached, action taken. Complete chain of evidence.</td></tr><tr><td><em>Adding a new device type</em></td><td>Requires platform-specific integration. May require retraining or reconfiguring AI models.</td><td>5,000+ plugins in Nagios Exchange. Write your own in any scripting language. No vendor permission required.</td></tr></tbody></table></figure>



<h2 class="wp-block-heading"><strong>The Case for Autonomous IT and the Right Time to Build Toward It</strong></h2>



<p class="wp-block-paragraph">None of this means autonomous IT is wrong. The <strong>5%</strong> of organizations generating real returns from AI in production are doing something right, and the pattern is consistent. </p>



<p class="wp-block-paragraph">They built their foundation first. They defined what remediation means in their environment. They piloted in non-critical systems and kept humans in the loop before handing anything over to automation. </p>



<p class="wp-block-paragraph"><strong>And that&#8217;s exactly the path Nagios XI is built for.</strong> </p>



<p class="wp-block-paragraph">When you&#8217;re ready to layer in AI, you&#8217;ll have the telemetry, the plugin ecosystem, and the event handler infrastructure to do it right. Organizations already using Nagios XI are integrating with platforms like Splunk, Datadog, and PagerDuty without ripping out the reliable core their teams know and trust.</p>



<p class="wp-block-paragraph">You don&#8217;t have to choose between proven monitoring and the future of AI. You build toward it, on a foundation that won&#8217;t let you down while you get there.</p>



<h2 class="wp-block-heading"><strong>Questions to Ask Before Any Autonomous Monitoring Purchase</strong></h2>



<p class="wp-block-paragraph">If you&#8217;re evaluating autonomous IT platforms, the following questions will tell you more than any demo.<strong></strong></p>



<p class="wp-block-paragraph">What happens when the AI is wrong? Can you get a full audit log of every automated action? Can you roll back a remediation? Who is responsible when autonomous action causes an outage?</p>



<p class="wp-block-paragraph">What does your environment need to look like before autonomous remediation works? Ask the vendor to describe the data readiness requirements explicitly. If they can&#8217;t, that&#8217;s an answer.</p>



<p class="wp-block-paragraph">How does pricing scale as AI features generate more telemetry? </p>



<p class="wp-block-paragraph">Many AIOps platforms charge on data ingestion volume. AI-powered correlation generates significantly more data than threshold alerting. Get a written cost estimate at 2x and 5x your current data volume.</p>



<p class="wp-block-paragraph">What does &#8220;autonomous&#8221; mean in your contract? Ask what percentage of actions require human approval. </p>



<p class="wp-block-paragraph">Many platforms that market autonomy actually require human confirmation for any production-impacting action, which is correct behavior, but it means they aren&#8217;t actually autonomous in the way the pitch implied. The vendors pushing autonomous IT aren&#8217;t wrong about where monitoring is going. They&#8217;re wrong about where most production environments are today, and how fast that gap can be safely closed.</p>



<p class="wp-block-paragraph">The organizations that will benefit most from AI-enhanced monitoring in 2026 are the ones who built solid, proven monitoring foundations first.</p>



<p class="wp-block-paragraph"><strong>That’s what Nagios has been doing for over 25 years.</strong></p>



<p class="wp-block-paragraph">Ready to see proven monitoring in action? <a href="https://nagios/com/request-demo">Request A Demo</a> Today!</p>



<p class="has-small-font-size wp-block-paragraph"><strong>Sources:</strong></p>



<p class="has-small-font-size wp-block-paragraph">[1]&nbsp; <a href="https://www.techtarget.com/whatis/definition/What-is-autonomic-computing" target="_blank" rel="noreferrer noopener">IBM: Autonomic Computing (2001) TechTarget — What is Autonomic Computing?</a></p>



<p class="has-small-font-size wp-block-paragraph">[2]<strong>&nbsp; </strong><a href="https://www.gartner.com/smarterwithgartner/how-to-get-started-with-aiops" target="_blank" rel="noreferrer noopener">Gartner: How to Get Started with AIOps</a></p>



<p class="has-small-font-size wp-block-paragraph">[3]<strong>&nbsp; </strong><a href="https://www.logicmonitor.com/blog/autonomous-it" target="_blank" rel="noreferrer noopener">LogicMonitor: What Is Autonomous IT?</a></p>



<p class="has-small-font-size wp-block-paragraph">[4]&nbsp;<strong> </strong><a href="https://sciencelogic.com/articles/autonomous-enterprise" target="_blank" rel="noreferrer noopener">ScienceLogic: The Autonomous Enterprise</a></p>



<p class="has-small-font-size wp-block-paragraph">[5]<strong>&nbsp; </strong><a href="https://www.advsyscon.com/blog/autonomous-it-operations/" target="_blank" rel="noreferrer noopener">Advanced Systems Concepts: Autonomous IT Operations</a></p>



<p class="has-small-font-size wp-block-paragraph">[6]<strong>&nbsp; </strong><a href="https://sranalytics.io/blog/why-95-of-ai-projects-fail/" target="_blank" rel="noreferrer noopener">SR Analytics: Why 95% of AI Projects Fail (MIT Project NANDA, July 2025)</a></p>



<p class="has-small-font-size wp-block-paragraph">[7]<strong>&nbsp; </strong><a href="https://www.gartner.com/en/newsroom/press-releases/2025-02-26-lack-of-ai-ready-data-puts-ai-projects-at-risk" target="_blank" rel="noopener">Gartner: AI Project Failure Rates and Data Readiness (February 2025)</a></p>



<p class="has-small-font-size wp-block-paragraph">[8]<strong>&nbsp; </strong><a href="https://www.elastic.co/blog/2026-observability-trends-generative-ai-opentelemetry" target="_blank" rel="noreferrer noopener">Elastic: The Landscape of Observability in 2026</a></p>



<p class="has-small-font-size wp-block-paragraph">[9]<strong>&nbsp; </strong><a href="https://www.logicmonitor.com/blog/observability-ai-trends-2026" target="_blank" rel="noreferrer noopener">LogicMonitor: 5 Observability and AI Trends for 2026</a></p>



<p class="has-small-font-size wp-block-paragraph">[10]<strong>&nbsp; </strong><a href="https://www.ninetwothree.co/blog/ai-fails" target="_blank" rel="noreferrer noopener">NineTwoThree: The Biggest AI Fails of 2025</a></p>



<p class="has-small-font-size wp-block-paragraph">[11]<strong>&nbsp; </strong><a href="https://leaddev.com/software-quality/whats-gone-wrong-at-github" target="_blank" rel="noreferrer noopener">LeadDev: What&#8217;s Gone Wrong at GitHub?</a></p>



<p class="has-small-font-size wp-block-paragraph">[12]<strong>&nbsp; </strong><a href="https://spectrum.ieee.org/ai-reliability" target="_blank" rel="noreferrer noopener">IEEE Spectrum: How Quiet Failures Are Redefining AI Reliability (April 2026)</a><br></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Why is Network Monitoring Important?</title>
		<link>https://library.nagios.com/industry-insights/why-is-network-monitoring-important/</link>
		
		<dc:creator><![CDATA[Hannah Adamson]]></dc:creator>
		<pubDate>Tue, 26 Aug 2025 14:00:00 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[Network Monitoring]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=59971</guid>

					<description><![CDATA[Understanding why network monitoring is important starts with a simple reality: an outage can happen at any moment. Downtime, lost revenue, and frustrated customers are all impacts. Ultimately, this puts your IT team (and the whole company) into reactive mode. But what if you could see issues coming and act before they cause real damage? [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Understanding why network monitoring is important starts with a simple reality: an outage can happen at any moment. Downtime, lost revenue, and frustrated customers are all impacts. Ultimately, this puts your IT team (and the whole company) into reactive mode.</p>



<p class="wp-block-paragraph">But what if you could see issues coming and act before they cause real damage? That&#8217;s where network monitoring comes in.</p>



<h2 class="wp-block-heading">What Is Network Monitoring?</h2>



<p class="wp-block-paragraph"><a href="https://www.nagios.com/network-monitoring/" data-type="link" data-id="https://www.nagios.com/network-monitoring/" target="_blank" rel="noreferrer noopener">Network monitoring</a> gives you early signs that an outage might occur and, more importantly, helps you prevent it.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td>Network monitoring is the continuous oversight of your IT infrastructure, including systems, devices, applications, and services. It&#8217;s designed to help you detect and address problems early. Think of it as an always-on radar system.</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><strong>Key Capabilities of Network Monitoring:</strong></p>



<ul class="wp-block-list">
<li>Full visibility across hybrid and cloud-native setups.</li>



<li>Automated, proactive alerts.</li>



<li>Support for automation and self-healing systems.</li>



<li>Centralized metrics, logs, and alerts.</li>
</ul>



<h2 class="wp-block-heading"><strong>Why is Network Monitoring Important?</strong></h2>



<p class="wp-block-paragraph">Here are the challenges tech leaders face today and how network monitoring addresses them:</p>



<figure style="font-size:14px" class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td><strong>IT Challenge</strong></td><td><strong>Impact</strong></td><td><strong>How Network Monitoring Helps</strong></td></tr><tr><td><strong>Costly Downtime</strong></td><td>When systems fail, revenue stops flowing and customer trust erodes. Every minute of downtime can cost thousands in lost business.</td><td><strong>Automation &amp; Self-Healing</strong> – Trigger scripts based on alerts. Problems get fixed automatically, often before you even know they happened.</td></tr><tr><td><strong>Complex IT Environments</strong></td><td>Hybrid infrastructure, multi-cloud deployments, and distributed teams make monitoring essential for operational resilience. You can&#8217;t manage what you can&#8217;t see.</td><td><strong>Hybrid &amp; Multi-Cloud Visibility</strong> – Monitor Amazon Web Services, Azure, Google Cloud, and on-premises systems from one place. No more blind spots.<br><br><strong>Unified Observability</strong> – Correlate metrics, logs, and alerts. Get the full picture, not just fragments.</td></tr><tr><td><strong>Reactive Mode Expenditure</strong></td><td>Teams stuck firefighting spend more time and money fixing problems after users notice them. It’s the difference between fixing a small leak and dealing with a flood.</td><td><strong>Proactive Monitoring</strong> – Get warning alerts when disk space, CPU load, or response times start trending toward trouble, and fix issues before users notice.<br><br><strong>Scalability</strong> – Support for large, distributed setups. Grow without worrying about your monitoring breaking down.</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">By implementing monitoring solutions, organizations can avoid costly downtime, gain visibility across complex environments, and maintain operational resilience.</p>



<p class="wp-block-paragraph">Here’s how real organizations put monitoring into practice.</p>



<h2 class="wp-block-heading">How Different Industries Use Network Monitoring</h2>



<div class="wp-block-columns is-layout-flex wp-container-core-columns-is-layout-7387b849 wp-block-columns-is-layout-flex">
<div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:33.33%">
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="683" src="https://library.nagios.com/wp-content/uploads/2025/08/hush-naidoo-jade-photography-yo01Z-9HQAw-unsplash-1024x683.jpg" alt="A stethoscope in black and white." class="wp-image-61524" title="Why is Network Monitoring Important? 4" srcset="https://library.nagios.com/wp-content/uploads/2025/08/hush-naidoo-jade-photography-yo01Z-9HQAw-unsplash-1024x683.jpg 1024w, https://library.nagios.com/wp-content/uploads/2025/08/hush-naidoo-jade-photography-yo01Z-9HQAw-unsplash-300x200.jpg 300w, https://library.nagios.com/wp-content/uploads/2025/08/hush-naidoo-jade-photography-yo01Z-9HQAw-unsplash-768x512.jpg 768w, https://library.nagios.com/wp-content/uploads/2025/08/hush-naidoo-jade-photography-yo01Z-9HQAw-unsplash-1536x1024.jpg 1536w, https://library.nagios.com/wp-content/uploads/2025/08/hush-naidoo-jade-photography-yo01Z-9HQAw-unsplash-2048x1365.jpg 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption"> </figcaption></figure>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="683" src="https://library.nagios.com/wp-content/uploads/2025/08/ashim-d-silva-pGcqw1ARGyg-unsplash-1024x683.jpg" alt="A plane at an airport." class="wp-image-61523" title="Why is Network Monitoring Important? 5" srcset="https://library.nagios.com/wp-content/uploads/2025/08/ashim-d-silva-pGcqw1ARGyg-unsplash-1024x683.jpg 1024w, https://library.nagios.com/wp-content/uploads/2025/08/ashim-d-silva-pGcqw1ARGyg-unsplash-300x200.jpg 300w, https://library.nagios.com/wp-content/uploads/2025/08/ashim-d-silva-pGcqw1ARGyg-unsplash-768x512.jpg 768w, https://library.nagios.com/wp-content/uploads/2025/08/ashim-d-silva-pGcqw1ARGyg-unsplash-1536x1024.jpg 1536w, https://library.nagios.com/wp-content/uploads/2025/08/ashim-d-silva-pGcqw1ARGyg-unsplash-2048x1365.jpg 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption"> </figcaption></figure>
</div>



<div class="wp-block-column is-layout-flow wp-block-column-is-layout-flow" style="flex-basis:66.66%">
<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">Organizations in every industry are using network monitoring to stay ahead:</p>



<p class="wp-block-paragraph"><strong><a href="https://www.nagios.com/solutions/healthcare-and-medicine/" target="_blank" rel="noreferrer noopener">Healthcare</a>:</strong> Hospitals use log monitoring to help maintain HIPAA compliance and catch issues with patient systems during updates or upgrades.</p>



<p class="wp-block-paragraph"><strong><a href="https://www.nagios.com/solutions/aerospace/" target="_blank" rel="noreferrer noopener">Aerospace</a>:</strong> Monitoring systems track spacecraft data to keep missions running smoothly, watch flight systems and equipment for failures, and check engine health to fix problems before they cause delays.</p>



<p class="wp-block-paragraph"><strong><a href="https://www.nagios.com/solutions/banking-and-financial-solutions/" target="_blank" rel="noreferrer noopener">Financial Services</a>:</strong> High-volume transaction systems rely on monitoring and alerting to reduce fraud risk and performance lag.</p>
</div>
</div>



<p class="wp-block-paragraph">Getting these results in your own environment starts with choosing the right monitoring solution.</p>



<h2 class="wp-block-heading"><strong>Why Choose Nagios?</strong></h2>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="576" src="https://library.nagios.com/wp-content/uploads/2025/08/Frame-3299-5-1024x576.png" alt="A Nagios XI dashboard." class="wp-image-61520" title="Why is Network Monitoring Important? 6" srcset="https://library.nagios.com/wp-content/uploads/2025/08/Frame-3299-5-1024x576.png 1024w, https://library.nagios.com/wp-content/uploads/2025/08/Frame-3299-5-300x169.png 300w, https://library.nagios.com/wp-content/uploads/2025/08/Frame-3299-5-768x432.png 768w, https://library.nagios.com/wp-content/uploads/2025/08/Frame-3299-5.png 1280w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption"> </figcaption></figure>



<p class="wp-block-paragraph">When selecting a network monitoring platform, you have several options, including Nagios, SolarWinds, Datadog, Zabbix, and many others.</p>



<p class="wp-block-paragraph"><br><strong>Why Nagios Stands Out:</strong></p>



<ul class="wp-block-list">
<li><strong>Proven Reliability:</strong> Nagios has been around for over 26 years, with a long-standing reputation for stability. When your monitoring can’t go down, you need something proven.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Modern Features:</strong> <a href="https://www.nagios.com/changelog/nagios-xi/nagios-xi-2026r2/" target="_blank" rel="noreferrer noopener">Nagios XI 2026R2</a> adds Roles for role-based control over what users can see and do, the new Wizard Builder for creating your own configuration wizards, and event forwarding to the new Nagios Fusion.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Flexibility that Scales:</strong> Custom plugins, extensions, and integrations with tools like <a href="https://www.nagios.com/Prometheus/" target="_blank" rel="noopener">Prometheus</a>, <a href="https://assets.nagios.com/downloads/nagiosxi/docs/Monitoring-Zabbix-Agents-with-Nagios-XI.pdf" target="_blank" rel="noreferrer noopener">Zabbix</a>, <a href="https://www.nagios.com/solutions/elasticsearch/" target="_blank" rel="noreferrer noopener">Elasticsearch</a>, and others that help build exactly what you need for your unique environment.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Industry Trust:</strong> Used by leading organizations across aerospace, healthcare, finance, and government sectors for mission-critical monitoring, including JPMorgan Chase, Verizon, Cisco, and Boeing.</li>
</ul>



<ul class="wp-block-list">
<li><strong>Cost-Effective Growth:</strong> Architecture that grows with your needs, avoiding high licensing fees.</li>
</ul>



<h2 class="wp-block-heading">Moving Forward</h2>



<p class="wp-block-paragraph">Outages and downtime are just some of the impacts of not having a proactive approach to network monitoring. Good monitoring doesn&#8217;t just alert you to problems; it helps you understand your environment. That way you can figure out where to focus your efforts, like spotting which systems are about to give you trouble or finding the best places to automate those repetitive tasks that eat up your day.</p>



<p class="wp-block-paragraph">If you&#8217;re looking to improve your monitoring approach, there are a few ways to explore what&#8217;s possible. You could <a href="https://www.nagios.com/products/nagios-xi/" target="_blank" rel="noopener">test Nagios XI</a> in your own environment or <a href="https://www.nagios.com/request-demo/?utm_source=library&amp;utm_medium=article&amp;utm_campaign=schedule-demo-page" target="_blank" rel="noopener">schedule a demo with a Nagios expert </a>to discuss your specific challenges. And if you&#8217;re still asking yourself, &#8220;Why is network monitoring important?&#8221; and want to see more examples, <a href="https://www.nagios.com/case-studies/" target="_blank" rel="noopener">review how other organizations have approached similar IT problems</a> to see the real-world impact and stories.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to Safely Introduce IoT Devices to Your Business Network</title>
		<link>https://library.nagios.com/industry-insights/safely-introduce-iot-devices/</link>
		
		<dc:creator><![CDATA[Ayub Huruse]]></dc:creator>
		<pubDate>Tue, 12 Aug 2025 13:45:00 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[IoT Devices]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Security Monitoring]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=60974</guid>

					<description><![CDATA[The Internet of Things (IoT) landscape is currently changing businesses and their willingness to adopt new technologies. As we anticipate nearly 20 billion connected devices on the market by the end of 2025, from smart sensors to connected heavy machinery, we can expect IoT products to transform capabilities and offerings, bringing efficiencies and innovation to [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">The Internet of Things (IoT) landscape is currently changing businesses and their willingness to adopt new technologies. As we anticipate nearly <a href="https://www.statista.com/statistics/1183457/iot-connected-devices-worldwide/" target="_blank" rel="noreferrer noopener">20 billion connected devices on the market by the end of 2025</a>, from smart sensors to connected heavy machinery, we can expect IoT products to transform capabilities and offerings, bringing efficiencies and innovation to the workplace.</p>



<p class="wp-block-paragraph">However, these devices also introduce significant cybersecurity risks. The 2021 Verkada breach, where <a href="https://www.cybereason.com/blog/live-feeds-of-150k-surveillance-cameras-compromised-in-verkada-breach" target="_blank" rel="noreferrer noopener">cybercriminals accessed live feeds from 150,000 security cameras</a>, proves the risk of damage when IoT devices are compromised is severe. Regardless of whether it is due to default or weak passwords, a lack of firmware updates, or unprotected communications, if you do not implement proper security controls, your business could incur a data breach, a cyberattack, or an operational disruption when an IoT device behaves unexpectedly.</p>



<p class="wp-block-paragraph">The purpose of this article is to provide IT managers, business owners, and security professionals with seven actionable steps to safely deploy IoT devices on their networks, assess the benefits offered by these devices, and maintain an adequate level of protection.</p>



<h2 class="wp-block-heading"><strong>Why Security is Important with IoT</strong></h2>



<p class="wp-block-paragraph">Just as IoT devices have powerful capabilities, they inherently lack or have inadequate security controls, which makes them an easy target for cybercriminals. A 2023 research study published by Cybersecurity Ventures estimated the global costs of <a href="https://cybersecurityventures.com/cybercrime-to-cost-the-world-8-trillion-annually-in-2023/" target="_blank" rel="noopener">cybercrime to be $8 trillion</a>, also predicting that IoT devices would become an increasingly popular target for attacks. A single compromised device can lead to data breaches, loss of operational time, damage to reputation, or financial penalties, depending on the requirements, regulations, or standards that were violated, such as <a href="https://gdpr-info.eu/" target="_blank" rel="noopener">GDPR</a>, <a href="https://www.hhs.gov/hipaa/index.html" target="_blank" rel="noopener">HIPAA</a>, or <a href="https://oag.ca.gov/privacy/ccpa" target="_blank" rel="noopener">CCPA</a>. Prioritizing security and controls will provide business value when it comes to realizing the true potential that IoT devices can offer. Here are seven helpful steps to accomplish this.</p>



<h2 class="wp-block-heading"><strong>Steps to Secure IoT Implementation</strong></h2>



<h3 class="wp-block-heading">1. <strong><strong>Create an IoT Plan</strong></strong></h3>



<p class="wp-block-paragraph">Collaborate with the business to ensure that IoT implementations align with the business purpose, while also evaluating any security risks that need to be addressed.</p>



<p class="wp-block-paragraph">Clearly defined goals, such as optimizing supply chain operations or accelerating the Customer Experience (CX), should be established. Evaluate the sensitivity of data and determine how it should be protected. Ensure that the devices you want to deploy support secure protocols (<a href="https://www.cloudflare.com/learning/ssl/why-use-tls-1.3/" target="_blank" rel="noopener">TLS version 1.3</a>). Conduct a risk assessment to identify the vulnerabilities, consider using the <a href="https://www.cisco.com/c/en/us/solutions/internet-of-things/iot-control-center.html" target="_blank" rel="noopener">Cisco IoT Control Center</a>, and understand how devices interact with each other from a security hygiene standpoint.</p>



<h3 class="wp-block-heading">2. <strong>Isolate Your Network</strong></h3>



<p class="wp-block-paragraph">Keeping IoT devices separated from more sensitive systems or networks can help limit the damage if an attacker breaches your defense.</p>



<p class="wp-block-paragraph">Implement a virtual local area network (VLAN) to isolate your IoT devices from servers and workstations. Then, write your firewall rules to limit traffic to the absolute minimum necessary for the device to operate. This could mean allowing access only to vendors&#8217; systems, such as those from Palo Alto Networks. If the device is truly inconsequential, such as a smart TV, connect it to your guest Wi-Fi, which allows even further reductions in permission.</p>



<h3 class="wp-block-heading">3. <strong>Assess Vendors and Devices</strong></h3>



<p class="wp-block-paragraph">Devices are often poorly engineered, and vendors are not always secure. Therefore, it is crucial to assess vendors thoroughly.</p>



<p class="wp-block-paragraph">Choose reputable vendors like Cisco or Siemens, who offer strong encryption (AES-256, TLS 1.3) and regularly updated firmware. Check if your devices have any open default passwords, and provide privacy policies publicly and unobscured. One advantage is that it minimizes the risks associated with the deployment of poorly engineered and insecure devices.</p>



<h3 class="wp-block-heading">4. Enforce Strong Authentication and Access Controls</h3>



<p class="wp-block-paragraph">Weak authentication is a straightforward method for an attacker to gain entry to devices that have been inadequately protected, as well as those with some security measures in place, as the Verkada breach can attest. Consider it a warning.</p>



<p class="wp-block-paragraph">Force strong, unique, not default, credentials, and where possible, enforce multi-factor authentication (MFA) of the device management interface. Implement role-based access control (RBAC) to manage and control user access, restrict unnecessary permissions, and limit unneeded access, such as remote access or the ability to connect to ports that are not required. IT administrators and disable remote management unless critical.</p>



<h3 class="wp-block-heading">5. <strong>Educate Employees on Internet of Things Risks</strong></h3>



<p class="wp-block-paragraph">The most significant contributor to IoT incidents is human error.</p>



<p class="wp-block-paragraph">Educate employees on IoT risk awareness that includes phishing attacks or downloading firmware from &#8220;unverified&#8221; websites. Create a clear, concise, and understandable plan outlining what employees can and cannot do with IoT devices, as well as the procedures to follow when using them. Provide periodic refresh training on good practices.</p>



<h3 class="wp-block-heading">6. <strong>Be Compliant</strong></h3>



<p class="wp-block-paragraph">Any IoT implementation is subject to regulations that you must comply with; failure to do so will result in fines and penalties specific to your industry.</p>



<p class="wp-block-paragraph">Be aware of what regulators will be looking for. To give an example, the GDPR will focus on data minimization, and HIPAA requires the protection of patient data. Utilize encryption and access controls in your IoT solutions to help ensure compliance with relevant standards. It may be necessary to maintain audit logs of records if they are an explicit requirement for compliance. Encrypt temperature data before transmission to a cloud dashboard.</p>



<h3 class="wp-block-heading">7. <strong>Detect Threats Early</strong></h3>



<p class="wp-block-paragraph">Detecting threats early is very important for IoT security. Use tools like <a href="https://www.nagios.com/products/nagios-xi/" target="_blank" rel="noreferrer noopener">Nagios XI</a> to monitor devices being used and watch for suspicious activity, such as spikes in data usage. Use an Intrusion Detection System (IDS) like <a href="https://www.snort.org/" target="_blank" rel="noreferrer noopener">Snort </a>to determine compromised devices. Perform compliance investigations to review device configurations and logs occasionally.</p>



<ul class="wp-block-list">
<li><strong>Related Reading</strong>: <a href="https://library.nagios.com/industry-insights/securing-iot-devices/" target="_blank" rel="noreferrer noopener">Securing Third-Party IoT Devices in 2025: Best Practices for Protection</a></li>
</ul>



<h2 class="wp-block-heading"><strong>Final Thoughts</strong></h2>



<p class="wp-block-paragraph">IoT devices are transforming the way we conduct business, and we must not overlook the cybersecurity risks they pose. There are excellent tools available, such as <a href="https://www.nagios.com/products/nagios-xi/" target="_blank" rel="noreferrer noopener">Nagios XI</a> and AWS IoT Device Defender, that help ensure a healthy IoT ecosystem. If you follow the seven steps above (create an IoT plan, network segmentation, assess vendors and devices, active monitoring, etc.), you can successfully integrate IoT devices safely and build resilience to <a href="https://library.nagios.com/security/" target="_blank" rel="noreferrer noopener">cyber threats</a>. </p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Robots in the Workplace: Security and Concerns</title>
		<link>https://library.nagios.com/industry-insights/robots-in-the-workplace/</link>
		
		<dc:creator><![CDATA[Louie Mattia]]></dc:creator>
		<pubDate>Thu, 07 Aug 2025 14:00:00 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[IoT Devices]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Security Monitoring]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=61171</guid>

					<description><![CDATA[Robots are becoming more commonplace both in media as well as enterprise environments, helping with simple tasks as well as complex ones. While they are convenient, connecting them to the network along with other devices brings out more security problems, be it losing control of the robot or important company information being stolen. With these [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Robots are becoming more commonplace both in media as well as enterprise environments, helping with simple tasks as well as complex ones. While they are convenient, connecting them to the network along with other devices brings out more security problems, be it losing control of the robot or important company information being stolen. With these risks in mind, it is important for businesses to know the risks involved as well as how to take preventive steps to keep everything secure.</p>



<h2 class="wp-block-heading">Why Robots Can Pose a Security Risk</h2>



<p class="wp-block-paragraph">Robots are incredibly advanced; however, they will still have very similar vulnerabilities to your standard IoT devices, such as having weak default passwords. Given that they have digital access as well as physical access, it&#8217;s especially important that these devices are secured. As robots being added into enterprise environments is still new, there haven&#8217;t been many examples of a security breach with them; however, the risks involved when security breaches are discovered have a huge impact.</p>



<p class="wp-block-paragraph"><a href="https://www.axios.com/2025/04/01/threat-spotlight-backdoor-in-chinese-robots-future-of-cybersecurity" target="_blank" rel="noopener">In April 2025, researchers discovered that the Unitree Go1 </a>robot dog contained a hidden backdoor service that could be activated without the user&#8217;s knowledge or consent. Once the device is connected to the internet, it would automatically initiate a remote access tunnel, potentially allowing hackers to take control of the robot, view its live camera feed, and access the underlying system via SSH. The researchers demonstrated that anyone with access to the necessary API keys could exploit this vulnerability, making it a serious and immediate threat<strong>.</strong></p>



<p class="wp-block-paragraph">In addition to the digital threats of having your data leaked or stolen, it is important to remember that a robot is also capable of interacting physically. Should it malfunction, or even worse, get hacked, it can easily lead to injuries, property damage, or restricted spaces being accessed. Normal IoT devices can give data, but with a robot, if someone from the outside gets control of it, they can cause a lot more harm, both to employees and the company.</p>



<h2 class="wp-block-heading">Best Practices</h2>



<p class="wp-block-paragraph">Many of the best practices from our article on <a href="https://library.nagios.com/industry-insights/securing-iot-devices/">securing IoT systems</a> apply directly to robots as well, since they are likely to be network-connected devices. However, in the case of robots, some of these practices become even more important, and there are also a few additional concerns unique to robotics that deserve special attention. </p>



<h3 class="wp-block-heading">1. Change Default Passwords and Strengthen Authentication</h3>



<p class="wp-block-paragraph">Changing default passwords is one of the simplest and most important steps in securing a robot. Many devices ship with factory-set credentials that are widely known, making them easy targets for attackers. These should be replaced immediately with strong, unique passwords. For added protection, especially when robots connect to cloud services or internal systems, implement multi-factor authentication (MFA) or certificate-based access. Securing login credentials early helps prevent one of the most common and avoidable threats.</p>



<h3 class="wp-block-heading">2. Know What’s on Your Network: Asset Visibility and Inventory</h3>



<p class="wp-block-paragraph">Robots can quietly join a network without drawing attention, especially in large or fast-moving environments. That makes real-time visibility essential. Use tools like Nmap or Nessus to scan for connected devices and log key details like IP address, manufacturer, and firmware version. For larger setups, platforms like AWS IoT Device Management or Azure IoT Hub can automate this process and alert you when new or unknown devices appear. Keeping track of every connected robot helps ensure nothing slips through the cracks.</p>



<h3 class="wp-block-heading">3. Encrypt Data</h3>



<p class="wp-block-paragraph">Robots contain sensitive information such as video streams from their camera, location data, and control commands. It’s important to protect this information by encrypting both the data being sent across networks and the data stored on the device or in the cloud. Using strong encryption methods, such as TLS for network communication and AES for stored data, helps prevent attackers from intercepting, reading, or altering critical information. This keeps robot operations secure and protects user privacy.</p>



<h3 class="wp-block-heading">4. Implement Network Segmentation and Monitoring</h3>



<p class="wp-block-paragraph">Keeping robots on a separate part of your network helps limit the damage if one gets compromised. Using isolated VLANs or subnets means an attacker can’t easily move from a robot to more sensitive systems. In addition, continuous monitoring tools like Nagios can watch for unusual activity, such as unexpected connections or spikes in data, that might signal a security issue. This combination of isolation and vigilance helps detect problems early and contain threats before they spread.</p>



<h3 class="wp-block-heading">5. Keep Software Up to Date</h3>



<p class="wp-block-paragraph">Robots run on software that can have security flaws. Making sure these are regularly updated is extremely important as the updates will likely contain patches or fixes to previously known security vulnerabilities. If possible, we want these devices to update automatically as well as keep an eye on what these updates entail so we can make sure they stay protected against both the old threats and any new threats.</p>



<h3 class="wp-block-heading">6. Ensure it Can be Stopped</h3>



<p class="wp-block-paragraph">Since robots are capable of moving around as well as physically interacting with the environment around them, it&#8217;s essential to ensure a way of stopping it should it go out of control for any reason. A button on the device, a remote kill switch, or some sort of software should be made to shut down the robot should this happen. While you could also simply disable the motors to stop it from moving, it’ll be more secure to shut down the device completely to cut off any connection if it were hacked.</p>



<h2 class="wp-block-heading">Conclusion </h2>



<p class="wp-block-paragraph">As robots become more common in workplaces, keeping them secure is more important than ever. Understanding their unique risks and following simple best practices, like changing default passwords, keeping track of devices on your network, encrypting data, separating networks, and regularly updating software, can help protect your business from costly hacks. Taking these steps isn’t just about technology; it’s about making sure your team can safely get the most out of these powerful tools.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>2025 Zero-Day Exploits: Emerging Trends and Effective Response Plans</title>
		<link>https://library.nagios.com/industry-insights/zero-day-exploits-2025-trends/</link>
		
		<dc:creator><![CDATA[Ayub Huruse]]></dc:creator>
		<pubDate>Thu, 31 Jul 2025 14:00:00 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Vulnerability Management]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=60037</guid>

					<description><![CDATA[Cyberattacks are more complex and faster than ever before, and zero-day exploits are the most insidious. They exploit vulnerabilities that no one even knows about, leaving businesses scrambling with no time to prepare. Over 60% of ransomware attacks in 2024 utilized zero-day exploits, resulting in damages worth billions of dollars. Cybercrime is estimated to cost [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Cyberattacks are more complex and faster than ever before, and zero-day exploits are the most insidious. They exploit vulnerabilities that no one even knows about, leaving businesses scrambling with no time to prepare.</p>



<p class="wp-block-paragraph"><a href="https://www.bankinfosecurity.com/zero-day-exploits-ransomware-trends-for-2024-a-25535" target="_blank" rel="noopener">Over 60% of ransomware attacks in 2024</a> utilized zero-day exploits, resulting in damages worth billions of dollars. Cybercrime is estimated to cost the world USD 10.5 trillion by 2025, according to <a href="https://cybersecurityventures.com/official-cybercrime-report-2025/#:~:text=Cybercrime%20is%20predicted%20to%20cost,after%20the%20U.S.%20and%20China." target="_blank" rel="noopener">Cybersecurity Ventures</a>.</p>



<p class="wp-block-paragraph">Let us look at why zero-days are dangerous, how zero-day exploits are found, the most significant incidents around the world, what we will see in 2025, and what you can do to combat zero-days with a good response plan.</p>



<h2 class="wp-block-heading"><strong>Why Zero-Days are a Big Problem</strong></h2>



<p class="wp-block-paragraph">A <a href="https://www.ibm.com/think/topics/zero-day" target="_blank" rel="noopener">zero-day exploit</a> targets a vulnerability in software, hardware, or firmware before the vendor or the security community knows of it. The attacker can exploit these vulnerabilities to steal data, deploy ransomware, or disrupt a service without anyone initially being aware of it. There is no patch or signature for a defense at the moment an organization becomes aware of a zero-day exploit; there is simply no time to defend against the attack vector.</p>



<h2 class="wp-block-heading"><strong>How Zero-Days are Found</strong></h2>



<h3 class="wp-block-heading"><strong>Fuzz Testing: Automated Vulnerability Search</strong></h3>



<p class="wp-block-paragraph"><a href="https://about.gitlab.com/topics/devsecops/what-is-fuzz-testing/" target="_blank" rel="noopener">Fuzz testing</a> involves the user inputting random or malformed data into an application, then checking for unexpected behaviors (such as crashing) that often indicate a bug is present underlying the unexpected behavior. Modern fuzzers, such as<a href="https://aflplus.plus/" target="_blank" rel="noopener"> AFL++</a> and <a href="https://bughunters.google.com/open-source-security/oss-fuzz" target="_blank" rel="noopener">Google&#8217;s OSS-Fuzz</a>, employ techniques that leverage coverage-guided and AI-assisted risk-aware code coverage approaches, ultimately identifying higher-risk paths in code. OSS-Fuzz, since its inception, has identified over 8,000 critical bugs in open-source projects (<a href="https://security.googleblog.com/2024/02/" target="_blank" rel="noopener">Google Security Blog, 2024</a>). Once fuzzing has been integrated into a CI/CD pipeline, it provides teams with the opportunity to discover potential vulnerabilities and prevent them during the development process.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="362" src="https://library.nagios.com/wp-content/uploads/2025/07/Automated-Vulnerability-Discovery-1024x362.png" alt="Fuzzing diagram" class="wp-image-61147" title="2025 Zero-Day Exploits: Emerging Trends and Effective Response Plans 7" srcset="https://library.nagios.com/wp-content/uploads/2025/07/Automated-Vulnerability-Discovery-1024x362.png 1024w, https://library.nagios.com/wp-content/uploads/2025/07/Automated-Vulnerability-Discovery-300x106.png 300w, https://library.nagios.com/wp-content/uploads/2025/07/Automated-Vulnerability-Discovery-768x271.png 768w, https://library.nagios.com/wp-content/uploads/2025/07/Automated-Vulnerability-Discovery.png 1280w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">What is Fuzzing? &#8211; photo by LinkedIn</figcaption></figure>



<h3 class="wp-block-heading"><strong>Bug Bounty Programs: Paying the Hackers to Help Us</strong></h3>



<p class="wp-block-paragraph">Bug bounty programs allow organizations to provide incentives to external researchers to discover and disclose defects to the researcher&#8217;s specifications. Platforms such as HackerOne or Bugcrowd help facilitate these relationships between organizations and ethical hackers. In 2024,<a href="https://security.googleblog.com/2025/03/vulnerability-reward-program-2024-in.html" target="_blank" rel="noopener"> Google paid out over $10 million</a> to successful vulnerability rewards, demonstrating the proactive nature of these discovery programs. Well-designed bug bounty programs can reduce the chances of zero days being sold to the black market.</p>



<h2 class="wp-block-heading">The Biggest Zero-Day Attacks in History</h2>



<p class="wp-block-paragraph"><strong><a href="https://www.trellix.com/security-awareness/ransomware/what-is-stuxnet/" target="_blank" rel="noopener">Stuxnet </a> (2010)</strong>: This worm exploited four chained Windows zero-days (<a href="https://nvd.nist.gov/vuln/detail/CVE-2010-2568" target="_blank" rel="noopener">CVE-2010-2568</a>) that enabled it to bypass multiple layers of security and gain control of SCADA systems, ultimately sabotaging the Iranian nuclear program. Stuxnet proved that isolating critical systems and keeping industrial technology current are requirements, not negotiable.</p>



<p class="wp-block-paragraph"><strong><a href="https://en.wikipedia.org/wiki/EternalBlue" target="_blank" rel="noopener">EternalBlue </a>(2017)</strong>: A stolen exploit from the NSA (<a href="https://nvd.nist.gov/vuln/detail/cve-2017-0144" target="_blank" rel="noopener">CVE-2017-0144</a>) that took advantage of a Windows exploit helped spawn the WannaCry and NotPetya ransomware attacks that locked out over 300,000 systems worldwide. A lesson learned that delaying patching creates risk.</p>



<p class="wp-block-paragraph"><strong><a href="https://www.ibm.com/think/topics/log4shell" target="_blank" rel="noopener">Log4Shell </a>(2021)</strong>: A zero-day flaw in Apache Log4j (<a href="https://nvd.nist.gov/vuln/detail/cve-2021-44228" target="_blank" rel="noopener">CVE-2021-44228</a>) was exploited, allowing attackers to remotely execute their code on impacted cloud-based systems and enterprise applications. This incident highlighted the importance of Software Bill of Materials (SBOM) tools to help track our third-party open-source components.</p>



<p class="wp-block-paragraph"><strong><a href="https://www.ncsc.gov.uk/information/moveit-vulnerability" target="_blank" rel="noopener">MOVEit </a>(2023)</strong>:The SQL injection zero-day (<a href="https://nvd.nist.gov/vuln/detail/cve-2023-34362" target="_blank" rel="noopener">CVE-2023-34362</a>) in MOVEit Transfer helped the CL0P gang easily steal an unknown amount of data from over 2,700 organizations and provided insight into our vulnerabilities through the supply chain</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Year</th><th>Incident &amp; CVE(s)</th><th>Impact</th><th>Lesson Learned</th></tr></thead><tbody><tr><td>2010</td><td>Stuxnet (CVE-2010-2568, etc.)</td><td>Wrecked Iranian nuclear equipment</td><td>Isolate critical systems; patch fast</td></tr><tr><td>2017</td><td>EternalBlue (CVE-2017-0144)</td><td>Locked 300,000+ systems</td><td>Don’t delay patches; avoid stockpiling exploits</td></tr><tr><td>2021</td><td>Log4Shell (CVE-2021-44228)</td><td>Hit countless cloud systems</td><td>Track software with SBOMs</td></tr><tr><td>2023</td><td>MOVEit (CVE-2023-34362)</td><td>Data stolen from 2,700+ orgs</td><td>Vet vendors; monitor apps</td></tr></tbody></table></figure>



<h2 class="wp-block-heading">What’s Coming in 2025</h2>



<p class="wp-block-paragraph">Cybercriminals are not going to surrender, and zero-days are evolving quickly. The implications include:</p>



<ul class="wp-block-list">
<li><strong><strong>Artificial Intelligence Attacks</strong></strong>: Hackers are employing AI-powered fuzzers to identify vulnerabilities quicker than before, and they are increasingly simulating real-world traffic so they can infiltrate your defenses.</li>



<li><strong><strong>Dark Web Purchases</strong></strong>: Zero-day exploits are now being sold on dark-web markets as subscriptions, with costs ranging from $100,000 to <a href="https://sirp.io/blog/behind-the-rise-of-the-million-dollar-zero-day-market/" target="_blank" rel="noopener">$10,000,000</a>.</li>



<li><strong>Ransomware&#8217;s Next Step:</strong> Ransomware groups are also buying zero-days to get into systems, which makes the attacks targeted and even more lethal.</li>



<li><strong>Internet of Things Vulnerabilities:</strong> With estimates that by 2025 there will be over <a href="https://www.statista.com/statistics/1183457/iot-connected-devices-worldwide/" target="_blank" rel="noopener">20 billion things </a>connected to the Internet, there are plenty of unpatched firmware vulnerabilities in smart cities and smart factories.</li>



<li><strong>Cloud Environments Vulnerabilities:</strong> Unprotected organizations&#8217; misconfigured cloud environments, in particular Kubernetes, are now a prime target for zero-days.</li>
</ul>



<h2 class="wp-block-heading">Fighting Back: A Zero-Day Response Plan</h2>



<p class="wp-block-paragraph">Utilizing the NIST <a href="http://Incident Response Life Cycle” (SP 800-61R2)">&#8220;Incident Response Life Cycle” (SP 800-61R2)</a>, here is a strategic plan for dealing with a zero-day:</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="451" src="https://library.nagios.com/wp-content/uploads/2025/06/incident-response-life-cycle-1024x451.png" alt="incident response life cycle diagram" class="wp-image-60053" title="2025 Zero-Day Exploits: Emerging Trends and Effective Response Plans 8" srcset="https://library.nagios.com/wp-content/uploads/2025/06/incident-response-life-cycle-1024x451.png 1024w, https://library.nagios.com/wp-content/uploads/2025/06/incident-response-life-cycle-300x132.png 300w, https://library.nagios.com/wp-content/uploads/2025/06/incident-response-life-cycle-768x338.png 768w, https://library.nagios.com/wp-content/uploads/2025/06/incident-response-life-cycle-1536x676.png 1536w, https://library.nagios.com/wp-content/uploads/2025/06/incident-response-life-cycle-2048x901.png 2048w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption"><a href="https://library.nagios.com/security/incident-response/" data-type="page" data-id="60857">Incident Response</a> Life Cycle – photo by nist</figcaption></figure>



<h3 class="wp-block-heading"><strong>Remain Ahead of the Game with Threat Intel</strong></h3>



<ul class="wp-block-list">
<li><strong>Watch Feeds:</strong> Monitor CISA’s Known Exploited Vulnerabilities list, <a href="https://attack.mitre.org/" target="_blank" rel="noopener">MITRE ATT&amp;CK</a>, etc., and tools like Recorded Future to glean insight on early threat detection.</li>



<li><strong>JOIN ISACs</strong>: Join an Information Sharing and Analysis Center for your specific industry to gather real-time attack data and countermeasures, and then immediately do something with it.</li>
</ul>



<h3 class="wp-block-heading">Virtual Patching: Buying Time</h3>



<p class="wp-block-paragraph">When a vendor patch isn’t ready, use these workarounds:</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Layer</th><th>Defense</th><th>Example</th></tr></thead><tbody><tr><td>Network</td><td>Firewalls, IPS rules</td><td>Block EternalBlue traffic</td></tr><tr><td>Endpoint</td><td>EDR alerts</td><td>Stop Log4Shell exploits</td></tr><tr><td>Container</td><td>Runtime security (eBPF)</td><td>Catch supply-chain attacks</td></tr></tbody></table></figure>



<h3 class="wp-block-heading"><strong>Best Practices to Take on</strong></h3>



<ul class="wp-block-list">
<li><strong>Spot It</strong>: Use tools like Nagios to identify troubling behavior and determine the impacted systems.</li>



<li><strong>Contain It</strong>: Block infected endpoints/services or turn off vulnerable services.</li>



<li><strong>Fix It</strong>: Deploy patches or temporary fixes and/or restore clean systems from backups.</li>



<li><strong>Clean It Up:</strong> Look for hidden threats or ways hackers may return.</li>



<li><strong>Learn from It</strong>: Reconfigure your defenses and test more code to mitigate future attacks.</li>
</ul>



<h3 class="wp-block-heading">Using Nagios to Stay Safe from Zero-Days</h3>



<p class="wp-block-paragraph">Nagios XI is a powerful tool that helps keep your systems safe by monitoring for any unusual activity in your network, such as unexpected spikes in data or changes in your apps. It monitors everything from your servers to your applications, quickly spotting signs of a zero-day attack. With quick alerts, Nagios XI lets you act fast to stop problems before they grow into bigger issues. Nagios XI also works in offline setups, keeping your systems less exposed. </p>



<h2 class="wp-block-heading">Wrapping Up</h2>



<p class="wp-block-paragraph">Zero-day exploits present a significant challenge, and it should be acknowledged that attackers have the advantage on a zero-day. However, with some proactive measures, the advantage can shift from attackers to defenders. By incorporating fuzzing during development, engaging ethical hackers, and properly conducting a response plan, organizations can reduce their risks posed by zero-days. By continually testing and improving their defenses, organizations can stay ahead of the ever-evolving threat landscape.</p>



<h2 class="wp-block-heading">Glossary</h2>



<ul class="wp-block-list">
<li><strong><a href="https://ebpf.io/" target="_blank" rel="noopener">eBPF</a></strong>: A Linux tool for monitoring system behavior in real time.</li>



<li><strong><a href="https://docs.oracle.com/javase/tutorial/jndi/overview/index.html" target="_blank" rel="noopener">JNDI</a></strong>: A Java interface exploited in Log4Shell attacks.</li>



<li><strong><a href="https://www.cisa.gov/sbom" target="_blank" rel="noopener">SBOM</a></strong>: A list of all software components to track vulnerabilities.</li>



<li><strong><a href="https://en.wikipedia.org/wiki/Fuzzing" target="_blank" rel="noopener">Fuzzing</a></strong>: A testing technique that inputs random or malformed data to uncover software vulnerabilities.</li>



<li><strong><a href="https://www.indusface.com/learning/what-is-virtual-patching/" target="_blank" rel="noopener">Virtual Patching</a></strong>: Temporary security measures to block exploits until vendor patches are available.</li>
</ul>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Securing Third-Party IoT Devices in 2025: Best Practices for Protection</title>
		<link>https://library.nagios.com/industry-insights/securing-iot-devices/</link>
		
		<dc:creator><![CDATA[Ayub Huruse]]></dc:creator>
		<pubDate>Thu, 24 Jul 2025 13:45:00 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[IoT Devices]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Security Monitoring]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=60819</guid>

					<description><![CDATA[In 2025, with nearly 20 billion IoT devices worldwide, from smart thermostats to industrial sensors, these tools are revolutionizing how we live and work. However, third-party IoT devices often come with security risks due to inconsistent standards, weak protocols, and outdated firmware. The 2016 Mirai Botnet, which disrupted major websites by exploiting unsecured IoT devices, [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">In 2025, with nearly <a href="https://www.statista.com/statistics/1183457/iot-connected-devices-worldwide/" target="_blank" rel="noopener">20 billion IoT devices worldwide</a>, from smart thermostats to industrial sensors, these tools are revolutionizing how we live and work. However, third-party IoT devices often come with security risks due to inconsistent standards, weak protocols, and outdated firmware.</p>



<p class="wp-block-paragraph"><a href="https://www.cloudflare.com/learning/ddos/glossary/mirai-botnet/" target="_blank" rel="noopener">The 2016 Mirai Botnet</a>, which disrupted major websites by exploiting unsecured IoT devices, serves as a stark reminder of these vulnerabilities. <a href="https://jumpcloud.com/blog/iot-security-risks-stats-and-trends-to-know-in-2025" target="_blank" rel="noopener">According to jumpcloud</a>, &#8220;more than 50% of IoT devices have critical vulnerabilities that hackers can exploit right now.&#8221;</p>



<p class="wp-block-paragraph">This article explores the risks of third-party IoT devices and outlines practical strategies to secure and monitor your IoT ecosystem effectively.</p>



<h2 class="wp-block-heading">Why Third-Party IoT Devices Pose Risks</h2>



<p class="wp-block-paragraph">The rapid growth of IoT devices brings undeniable benefits, but their security challenges are significant. Weak default passwords, unencrypted data, and irregular updates make these devices prime targets for cyberattacks. Hackers can exploit them to steal data, disrupt operations, or even launch large-scale attacks. The good news? With the right approach, you can mitigate these risks and maintain a secure network. Below are ten best practices for securing and monitoring third-party IoT devices.</p>



<h3 class="wp-block-heading">1. Know What’s on Your Network</h3>



<p class="wp-block-paragraph">You can’t secure what you don’t see. Untracked IoT devices are like hidden weak spots in your network, ready to be exploited.</p>



<ul class="wp-block-list">
<li><strong>Inventory scanning:</strong> Use <a href="https://nmap.org/" target="_blank" rel="noopener">Nmap </a>or <a href="https://www.tenable.com/products/nessus" data-type="link" data-id="https://www.tenable.com/products/nessus" target="_blank" rel="noopener">Nessus </a>to perform periodic network scans that detect and catalog every IoT device. Capture attributes such as manufacturer, model, MAC address, and firmware version.</li>



<li><strong>Cloud-based asset management:</strong> Leverage<a href="https://aws.amazon.com/iot-device-management/" target="_blank" rel="noopener"> AWS IoT Device Management</a> or <a href="https://azure.microsoft.com/en-us/products/iot-hub" target="_blank" rel="noopener">Microsoft Azure IoT Hub</a> to automate inventory updates and generate alerts for unknown devices.</li>
</ul>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Ensures comprehensive visibility into all IoT endpoints.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="559" src="https://library.nagios.com/wp-content/uploads/2025/07/Azure-IoT-Hub-Use-Cases-1024x559.webp" alt="Azure IoT Hub use cases" class="wp-image-60860" title="Securing Third-Party IoT Devices in 2025: Best Practices for Protection 9" srcset="https://library.nagios.com/wp-content/uploads/2025/07/Azure-IoT-Hub-Use-Cases-1024x559.webp 1024w, https://library.nagios.com/wp-content/uploads/2025/07/Azure-IoT-Hub-Use-Cases-300x164.webp 300w, https://library.nagios.com/wp-content/uploads/2025/07/Azure-IoT-Hub-Use-Cases-768x419.webp 768w, https://library.nagios.com/wp-content/uploads/2025/07/Azure-IoT-Hub-Use-Cases.webp 1100w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Azure IoT Hub &#8211; photo by Bacancy.</figcaption></figure>



<h3 class="wp-block-heading">2. Lock Them Down with Network Segmentation</h3>



<p class="wp-block-paragraph">A single compromised device, like a smart camera, shouldn’t bring down your entire network.</p>



<ul class="wp-block-list">
<li>Deploy IoT devices on isolated VLANs or subnets separate from sensitive systems (<a href="https://csrc.nist.gov/pubs/sp/800/190/final" target="_blank" rel="noopener">NIST SP 800‑190</a>).</li>



<li>Configure firewall rules to restrict traffic to essential services only.</li>



<li>Apply zero‑trust principles: require mutual authentication and minimal permissions for device-to-device communication.</li>
</ul>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Prevents lateral movement across your corporate network.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1024" height="788" src="https://library.nagios.com/wp-content/uploads/2025/07/What-is-network-segmentation-1024x788-1.png" alt="How network segmentation works" class="wp-image-61011" title="Securing Third-Party IoT Devices in 2025: Best Practices for Protection 10" srcset="https://library.nagios.com/wp-content/uploads/2025/07/What-is-network-segmentation-1024x788-1.png 1024w, https://library.nagios.com/wp-content/uploads/2025/07/What-is-network-segmentation-1024x788-1-300x231.png 300w, https://library.nagios.com/wp-content/uploads/2025/07/What-is-network-segmentation-1024x788-1-768x591.png 768w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">What is Network Segmentation &amp; How Does It Work? &#8211; photo by Dashlane.</figcaption></figure>



<h3 class="wp-block-heading">3. Strengthen Authentication</h3>



<p class="wp-block-paragraph">Weak credentials, like the default “admin” exploited in the Mirai botnet, are a major security gap.<a href="https://www.kaaiot.com/iot-knowledge-base/iot-security-and-privacy-challenges-with-solutions" target="_blank" rel="noopener"></a></p>



<p class="wp-block-paragraph">Replace default credentials with strong, unique passwords. Use <a href="https://learn.microsoft.com/en-us/azure/iot-hub/reference-x509-certificates" target="_blank" rel="noopener">X.509 certificates </a>for device-to-cloud authentication and enable multi-factor authentication (MFA) for admin access where possible. These steps lock out unauthorized users and keep your devices secure.</p>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Prevents unauthorized access and brute force attacks.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="576" src="https://library.nagios.com/wp-content/uploads/2025/07/Strengthen-Authentication-1024x576.png" alt="Multi-factor authentcation" class="wp-image-61110" title="Securing Third-Party IoT Devices in 2025: Best Practices for Protection 11" srcset="https://library.nagios.com/wp-content/uploads/2025/07/Strengthen-Authentication-1024x576.png 1024w, https://library.nagios.com/wp-content/uploads/2025/07/Strengthen-Authentication-300x169.png 300w, https://library.nagios.com/wp-content/uploads/2025/07/Strengthen-Authentication-768x432.png 768w, https://library.nagios.com/wp-content/uploads/2025/07/Strengthen-Authentication.png 1279w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Strengthening Multi-Factor Authentication &#8211; photo by LinkedIn.</figcaption></figure>



<h3 class="wp-block-heading">4. Stay on Top of Updates</h3>



<p class="wp-block-paragraph">Outdated firmware leaves devices vulnerable to known exploits.</p>



<ul class="wp-block-list">
<li>Subscribe to CVE Details feeds and vendor security advisories.</li>



<li>Automate firmware patch deployment with tools such as AWS IoT Device Management or Balena.</li>



<li>Retire end-of-life devices that no longer receive security updates.</li>
</ul>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Closes security gaps before they can be exploited.</p>



<h3 class="wp-block-heading">5. Monitor with Tools Like Nagios</h3>



<p class="wp-block-paragraph">IoT devices can show subtle signs of trouble, like unusual data spikes or rogue connections. Proactive monitoring catches these early.</p>



<p class="wp-block-paragraph"><a href="https://www.nagios.com/products/nagios-xi/" target="_blank" rel="noopener">Nagios XI</a> and <a href="https://www.nagios.com/products/nagios-network-analyzer/" data-type="link" data-id="https://www.nagios.com/products/nagios-network-analyzer/" target="_blank" rel="noopener">Nagios Network Analyzer</a> let you set baselines for device behavior, track network traffic, and spot anomalies almost instantly. Nagios XI lets you monitor everything from CPU, Memory, and Disk usage and integrates it with Nagios Log Server for instant alerts.</p>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Enables early detection of potential threats, enhancing response times.</p>



<h3 class="wp-block-heading">6. Encrypt Everything</h3>



<p class="wp-block-paragraph">Unencrypted data can be intercepted by attackers, allowing them to monitor user activity and steal sensitive information.</p>



<p class="wp-block-paragraph">Ensure devices use <a href="https://www.cloudflare.com/learning/ssl/why-use-tls-1.3/" target="_blank" rel="noopener">TLS 1.3</a> for communication and MQTT with encryption for messaging. Use AES-256 for local data storage. Edge computing can also help by processing sensitive data locally, reducing exposure during transmission. These measures keep your data safe from eavesdroppers.</p>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Maintains confidentiality and integrity of IoT data.</p>



<h3 class="wp-block-heading">7. Limit Who Can Touch Them</h3>



<p class="wp-block-paragraph">Physical access or unchecked admin privileges can lead to big problems.</p>



<p class="wp-block-paragraph">Use tamper-evident seals to secure devices and role-based access control (RBAC) to restrict administrative access. Monitor logs for suspicious activity to catch unauthorized attempts early. Tight access controls protect your devices from tampering or misuse.</p>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Reduces risks from insider and outsider threats.</p>



<h3 class="wp-block-heading">8. Test for Weak Spots</h3>



<p class="wp-block-paragraph">Waiting for hackers to find vulnerabilities is a risky bet.</p>



<p class="wp-block-paragraph">Run regular penetration tests and vulnerability scans with tools like <a href="https://www.openvas.org/" target="_blank" rel="noopener">OpenVAS</a> or <a href="https://portswigger.net/burp" target="_blank" rel="noopener">Burp Suite</a>. Simulate real-world attacks to identify weaknesses, such as unpatched firmware or weak encryption, before they’re exploited. This proactive approach keeps your defenses sharp.</p>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Ensures continuous improvement of security posture.</p>



<h3 class="wp-block-heading">9. Check Your Vendors Carefully</h3>



<p class="wp-block-paragraph">Not all IoT manufacturers prioritize security, and a weak vendor can mean a weak device.</p>



<ul class="wp-block-list">
<li>Require vendor adherence to standards such as <a href="https://www.iso.org/standard/27001" target="_blank" rel="noopener">ISO 27001</a> or <a href="https://www.etsi.org/deliver/etsi_en/303600_303699/303645/03.01.03_60/en_303645v030103p.pdf" target="_blank" rel="noopener">ETSI EN 303 645</a>.</li>



<li>Review vendor patch cadence, security disclosure policies, and transparency reports.</li>



<li>Incorporate security requirements and liability clauses into procurement contracts.</li>
</ul>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Reduces introduction of vulnerable devices.</p>



<h3 class="wp-block-heading">10. Have a Plan for When Things Go Wrong</h3>



<p class="wp-block-paragraph">Breaches, like the <a href="https://www.bbc.com/news/technology-56342525" target="_blank" rel="noopener">2021 Verkada hack </a>where attackers accessed 150,000 cameras, highlight the need for preparedness.</p>



<p class="wp-block-paragraph">Develop IoT-specific incident response plans with isolation protocols and detailed logging for forensic analysis. Regularly test these plans to ensure rapid response and containment during an attack.</p>



<p class="wp-block-paragraph"><strong>Benefit:</strong> Minimizes impact and recovery time during real-world incidents.</p>



<h2 class="wp-block-heading">Quick Look at IoT Security Practices</h2>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th><strong>Practice</strong></th><th><strong>Implementation</strong></th><th><strong>Benefit</strong></th></tr></thead><tbody><tr><td>Device Inventory</td><td>Scan and catalog with Nmap or Nessus</td><td>Ensures visibility of all devices</td></tr><tr><td>Network Segmentation</td><td>Use VLANs and zero-trust policies</td><td>Limits attack propagation</td></tr><tr><td>Authentication</td><td>Enforce strong credentials and MFA</td><td>Prevents unauthorized access</td></tr><tr><td>Firmware Updates</td><td>Automate patches and retire EOL devices</td><td>Closes known vulnerabilities</td></tr><tr><td>Monitoring (Nagios)</td><td>Analyze traffic and detect anomalies</td><td>Enables early threat detection</td></tr><tr><td>Encryption</td><td>Implement TLS 1.3, MQTT, and AES-256</td><td>Protects data confidentiality</td></tr><tr><td>Access Control</td><td>Use RBAC and physical security measures</td><td>Reduces tampering risks</td></tr><tr><td>Vulnerability Assessments</td><td>Conduct scans and penetration tests</td><td>Identifies weaknesses proactively</td></tr><tr><td>Vendor Evaluation</td><td>Assess vendor security practices</td><td>Strengthens supply chain security</td></tr><tr><td>Incident Response</td><td>Develop and test response plans</td><td>Minimizes breach impact</td></tr></tbody></table></figure>



<h2 class="wp-block-heading">Final Thoughts</h2>



<p class="wp-block-paragraph">Third-party IoT devices are key to modern operations but carry real security risks. Keep a tight inventory, segment networks, enforce encryption, vet vendors, and monitor with tools like Nagios. <a href="https://library.nagios.com/security/" target="_blank" data-type="page" data-id="59681" rel="noreferrer noopener">Cyber threats</a> are a matter of &#8220;when,&#8221; not &#8220;if.&#8221; These steps keep your IoT ecosystem secure and ready for action.</p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Assessing Third-Party Software Risks: A Comprehensive Guide</title>
		<link>https://library.nagios.com/industry-insights/assessing-third-party-software/</link>
		
		<dc:creator><![CDATA[Ayub Huruse]]></dc:creator>
		<pubDate>Wed, 23 Jul 2025 14:10:00 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Vulnerability Management]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=60177</guid>

					<description><![CDATA[Third-party software can make building applications easier, but one weak link can let attackers into even the strongest systems. In December 2020, hackers slipped malicious updates into SolarWinds’ Orion platform, hitting over 18,000 organizations with data breaches and ransomware attacks. A year later, the Log4j vulnerability put millions of systems at risk with just one [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Third-party software can make building applications easier, but one weak link can let attackers into even the strongest systems. </p>



<p class="wp-block-paragraph">In December 2020, <a href="https://www.cisecurity.org/solarwinds" target="_blank" rel="noopener">hackers slipped malicious updates into SolarWinds’ Orion platform</a>, hitting over 18,000 organizations with data breaches and ransomware attacks. A year later, <a href="https://venturebeat.com/security/the-log4j-vulnerability-is-bad-heres-the-good-news/" target="_blank" rel="noopener">the Log4j vulnerability</a> put millions of systems at risk with just one line of Java code. <a href="https://www.securitymagazine.com/articles/98685-poor-software-costs-the-us-24-trillion" target="_blank" rel="noopener">A 2022 Security Magazine report</a> says software quality issues cost the U.S. economy $2.41 trillion.</p>



<p class="wp-block-paragraph">This article breaks down the risks of third-party software, explains what to look for, and shares practical steps to keep your systems secure.</p>



<h2 class="wp-block-heading">Why Third-Party Software Risks Matter</h2>



<p class="wp-block-paragraph">Third-party software, including open-source libraries, commercial packages, and cloud services, is essential to modern applications but introduces significant vulnerabilities. Weaknesses in these components can lead to data breaches, operational disruptions, or regulatory penalties under standards like the General Data Protection Regulation (GDPR) or the California Consumer Privacy Act (CCPA). A <a href="https://snyk.io/blog/cybersecurity-ventures-2023-software-supply-chain-attack-report/" target="_blank" rel="noopener">2023 Cybersecurity Ventures report</a> noted that supply-chain attacks are a growing threat, with third-party software as a primary attack vector. By proactively managing these risks, businesses can safeguard their systems and maintain trust.</p>



<h2 class="wp-block-heading">Steps to Assess and Mitigate Risks</h2>



<h3 class="wp-block-heading">1. Map Your Software Ecosystem</h3>



<p class="wp-block-paragraph">You can’t protect what you don’t know about. Start by listing all the software your applications use.</p>



<p class="wp-block-paragraph">Make a Software Bill of Materials (SBOM) to track everything from open-source libraries to commercial tools and cloud services like APIs or SaaS platforms. Tools like CycloneDX or System Package Data Exchange (SPDX) create clear visuals of how your software connects, including hidden dependencies. Check this list every three months to catch any changes.</p>



<p class="wp-block-paragraph"><strong>Benefit</strong>: Helps you see all the software you rely on.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1024" height="393" src="https://library.nagios.com/wp-content/uploads/2025/06/software-supply-chain.png" alt="Trusted software supply chain" class="wp-image-60182" title="Assessing Third-Party Software Risks: A Comprehensive Guide 12" srcset="https://library.nagios.com/wp-content/uploads/2025/06/software-supply-chain.png 1024w, https://library.nagios.com/wp-content/uploads/2025/06/software-supply-chain-300x115.png 300w, https://library.nagios.com/wp-content/uploads/2025/06/software-supply-chain-768x295.png 768w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Software supply chain – photo by spectral.</figcaption></figure>



<h3 class="wp-block-heading">2. Evaluate Risk Factors</h3>



<p class="wp-block-paragraph">Look closely at your software to find risks that could cause trouble.</p>



<p class="wp-block-paragraph">Examine how often open-source projects are updated and who’s working on them using platforms like GitHub or GitLab. Active projects with many contributors are usually safer. Use the National Vulnerability Database (NVD) to check for known issues and their severity. Make sure software licenses, like General Public License (GPL) or Massachusetts Institute of Technology (MIT), won’t cause legal problems, using tools like FOSSA to verify.</p>



<p class="wp-block-paragraph"><strong>Benefit</strong>: Pinpoints risky software so you can act fast.</p>



<h3 class="wp-block-heading">3. Leverage Automated Scanning Tools</h3>



<p class="wp-block-paragraph">Integrate Software Composition Analysis (SCA) into your continuous integration/continuous deployment (CI/CD) pipeline for early detection.</p>



<p class="wp-block-paragraph">Use tools like the Open Worldwide Application Security Project&nbsp;(OWASP) Dependency-Check to scan for known vulnerabilities or Snyk for real-time alerts and remediation guidance. Run scans on each pull request via GitHub Actions or Jenkins, adjusting severity thresholds to minimize false positives.</p>



<p class="wp-block-paragraph"><strong>Benefit</strong>: Detects issues before they reach production.</p>



<h3 class="wp-block-heading">4. Conduct Manual Reviews</h3>



<p class="wp-block-paragraph">Manual reviews complement automation for deeper insights.</p>



<p class="wp-block-paragraph">Verify cryptographic signatures, such as GPG or Secure Hash Algorithms (SHA), for software binaries and updates to prevent tampering. Review open-source project commit histories for suspicious activity, such as unverified contributors or sudden contribution spikes.</p>



<p class="wp-block-paragraph"><strong>Benefit</strong>: Uncovers risks that automated tools may miss.</p>



<h3 class="wp-block-heading">5. Assess Vendor Security</h3>



<p class="wp-block-paragraph">Not all software or cloud services are built with security in mind.</p>



<p class="wp-block-paragraph">Ask vendors about their security practices using questionnaires like Standardized Information Gathering (SIG) or the Cloud Security Alliance&#8217;s Consensus Assessment Initiative Questionnaire (CSA CAIQ), focusing on encryption, incident response, and access controls. Check for certifications like System and Organization Controls (SOC) 2 or information security standard (ISO) 27001, and look for weaknesses, like poor authentication. Review vendors yearly or after any security issues.</p>



<p class="wp-block-paragraph"><strong>Benefit</strong>: Makes sure your vendors meet high security standards.</p>



<h3 class="wp-block-heading">6. Prioritize and Remediate Risks</h3>



<p class="wp-block-paragraph">Not all vulnerabilities are equal. Sort them by how serious they are.</p>



<p class="wp-block-paragraph">Focus on critical issues with high Common Vulnerability Scoring System (CVSS) scores (above 8.0) in widely used software that hackers already know how to exploit. Tackle moderate issues (CVSS 4.0–7.9) in less critical systems next. Ignore minor issues with no known exploits unless they’re easy to fix. You can patch problems, swap risky software for safer options like Simple Logging Facade for Java (SLF4J) instead of Logging for Java (Log4j), or isolate weak components using network separation or tools like Docker.</p>



<p class="wp-block-paragraph"><strong>Benefit</strong>: Saves time by tackling the most dangerous threats first.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1024" height="675" src="https://library.nagios.com/wp-content/uploads/2025/06/Hyperproof_The-Ultimate-Guide-Risk-Prioritization_blog_Risk-matrix-1024x675-2.webp" alt="Chart showing third-party software risk prioritization" class="wp-image-60184" title="Assessing Third-Party Software Risks: A Comprehensive Guide 13" srcset="https://library.nagios.com/wp-content/uploads/2025/06/Hyperproof_The-Ultimate-Guide-Risk-Prioritization_blog_Risk-matrix-1024x675-2.webp 1024w, https://library.nagios.com/wp-content/uploads/2025/06/Hyperproof_The-Ultimate-Guide-Risk-Prioritization_blog_Risk-matrix-1024x675-2-300x198.webp 300w, https://library.nagios.com/wp-content/uploads/2025/06/Hyperproof_The-Ultimate-Guide-Risk-Prioritization_blog_Risk-matrix-1024x675-2-768x506.webp 768w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Third-party software risk prioritization&nbsp;– photo by Hyperproof.</figcaption></figure>



<h3 class="wp-block-heading">7. Implement Continuous Monitoring</h3>



<p class="wp-block-paragraph">Ongoing vigilance is essential to manage dynamic supply chain risks.</p>



<p class="wp-block-paragraph">Sign up for vendor security alerts and Common Vulnerabilities and Exposure (CVE) updates through tools like Snyk or Black Duck. Use zero-trust principles to check every piece of software regularly. Try AI-powered tools like Synopsys Polaris to spot unusual patterns in software vulnerabilities.</p>



<p class="wp-block-paragraph"><strong>Benefit</strong>: Maintains security in an evolving threat landscape.</p>



<h2 class="wp-block-heading">Risk Assessment Checklist</h2>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Step</th><th>Action</th><th>Tools/Resources</th></tr></thead><tbody><tr><td>Map Ecosystem</td><td>Create SBOM, audit quarterly</td><td><a href="https://cyclonedx.org/" target="_blank" rel="noopener">CycloneDX</a>, <a href="https://spdx.dev/" target="_blank" rel="noopener">SPDX</a></td></tr><tr><td>Evaluate Risks</td><td>Assess code maturity, vulnerabilities, licenses</td><td><a href="https://github.com/" target="_blank" rel="noopener">GitHub</a>, <a href="https://www.nist.gov/itl/nvd" target="_blank" rel="noopener">NVD</a>, <a href="https://fossa.com/" target="_blank" rel="noopener">FOSSA</a></td></tr><tr><td>Automated Scanning</td><td>Integrate SCA into CI/CD</td><td><a href="https://owasp.org/www-project-dependency-check/" target="_blank" rel="noopener">OWASP Dependency-Check</a>, <a href="https://security.snyk.io/" target="_blank" rel="noopener">Snyk</a></td></tr><tr><td>Manual Reviews</td><td>Verify signatures, review commit history</td><td><a href="https://gpgtools.org/" target="_blank" rel="noopener">GPG</a>, <a href="https://github.com/" target="_blank" rel="noopener">GitHub</a>, <a href="https://about.gitlab.com/" target="_blank" rel="noopener">GitLab</a></td></tr><tr><td>Vendor Assessment</td><td>Use SIG, CAIQ, review certifications</td><td><a href="https://soc2.co.uk/" target="_blank" rel="noopener">SOC2</a>, <a href="https://www.iso.org/standard/27001" target="_blank" rel="noopener">ISO 27001</a></td></tr><tr><td>Prioritize Risks</td><td>Use risk matrix, patch, or isolate</td><td><a href="https://www.docker.com/" target="_blank" rel="noopener">Docker</a>, <a href="https://www.slf4j.org/" target="_blank" rel="noopener">SLF4J</a></td></tr><tr><td>Continuous Monitoring</td><td>Subscribe to alerts, apply zero trust</td><td><a href="https://security.snyk.io/" target="_blank" rel="noopener">Snyk</a>, <a href="https://www.blackduck.com/" target="_blank" rel="noopener">Black Duck</a>, <a href="https://polarissoftware.com/" target="_blank" rel="noopener">Synopsys Polaris</a></td></tr></tbody></table></figure>



<h2 class="wp-block-heading">Final Thoughts</h2>



<p class="wp-block-paragraph">Third-party software can expose your business to serious risks, but you can tackle them with the right steps: map your software, check for vulnerabilities, use automated tools, do manual reviews, review vendors, prioritize fixes, and keep monitoring for threats. </p>



<p class="wp-block-paragraph">In today’s connected world, <a href="https://library.nagios.com/security/" target="_blank" rel="noreferrer noopener">cyberattacks</a> are inevitable. Take action now to strengthen your defenses and stay ahead of threats.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Why Nagios is More Relevant than Ever for Infrastructure Monitoring</title>
		<link>https://library.nagios.com/industry-insights/why-nagios-is-still-relevant/</link>
		
		<dc:creator><![CDATA[Hannah Adamson]]></dc:creator>
		<pubDate>Tue, 17 Jun 2025 14:00:00 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[Infrastructure Monitoring]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=58035</guid>

					<description><![CDATA[Nagios is not obsolete. Nagios XI 2026R2 shipped on September 23, 2026, and ships Nagios Core 4.5.14. Nagios Enterprises maintains four commercial solutions on roughly monthly release cycles. The accurate criticism is narrower than &#8220;obsolete&#8221;: hand-configured Nagios Core is labor-intensive, which is the specific problem Nagios XI exists to solve. Most articles arguing that Nagios [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Nagios is not obsolete. Nagios XI 2026R2 shipped on September 23, 2026, and ships <a href="https://www.nagios.com/products/nagios-core/" target="_blank" rel="noopener">Nagios Core</a> 4.5.14. Nagios Enterprises maintains four commercial solutions on roughly monthly release cycles. The accurate criticism is narrower than &#8220;obsolete&#8221;: hand-configured Nagios Core is labor-intensive, which is the specific problem <a href="https://www.nagios.com/products/nagios-xi/" target="_blank" rel="noopener">Nagios XI</a> exists to solve.</p>



<p class="wp-block-paragraph">Most articles arguing that Nagios is outdated were written years ago and describe a version nobody runs. This page lists current versions with release dates, states plainly what the criticism gets right, shows what Nagios monitors today, and explains where it still outperforms newer tools.</p>



<h2 class="wp-block-heading">What Nagios shipped in 2026</h2>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th class="has-text-align-left" data-align="left">Component</th><th class="has-text-align-left" data-align="left">Current version</th><th class="has-text-align-left" data-align="left">Released</th></tr></thead><tbody><tr><td class="has-text-align-left" data-align="left">Nagios Core</td><td class="has-text-align-left" data-align="left">4.5.14</td><td class="has-text-align-left" data-align="left">2026-08-05</td></tr><tr><td class="has-text-align-left" data-align="left">Nagios XI</td><td class="has-text-align-left" data-align="left">2026R2</td><td class="has-text-align-left" data-align="left">2026-09-23</td></tr><tr><td class="has-text-align-left" data-align="left">Nagios Log Server</td><td class="has-text-align-left" data-align="left">2026R2</td><td class="has-text-align-left" data-align="left">2026-09-29</td></tr><tr><td class="has-text-align-left" data-align="left">Nagios Network Analyzer</td><td class="has-text-align-left" data-align="left">2026R2</td><td class="has-text-align-left" data-align="left">2026-09-30</td></tr><tr><td class="has-text-align-left" data-align="left">Nagios Fusion</td><td class="has-text-align-left" data-align="left">2026R2</td><td class="has-text-align-left" data-align="left">2026-09-22</td></tr><tr><td class="has-text-align-left" data-align="left">NCPA (Nagios Cross-Platform Agent)</td><td class="has-text-align-left" data-align="left">3.5.0</td><td class="has-text-align-left" data-align="left">2026-09-08</td></tr><tr><td class="has-text-align-left" data-align="left">NRPE (Nagios Remote Plugin Executor)</td><td class="has-text-align-left" data-align="left">4.2.0</td><td class="has-text-align-left" data-align="left">2026-10-21</td></tr><tr><td class="has-text-align-left" data-align="left">Nagios Plugins</td><td class="has-text-align-left" data-align="left">2.5</td><td class="has-text-align-left" data-align="left">2026-03-31</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">Versions verified October 26, 2026 against the <a href="https://www.nagios.com/changelog/" target="_blank" rel="noopener">official changelogs</a>.</p>



<p class="wp-block-paragraph">Eight components shipped releases in 2026. Nagios Core shipped 4.5.12, 4.5.13, and 4.5.14 over the year, each carrying security fixes. Nagios XI 2026R2 ships Nagios Core 4.5.14, NDO 3.1.2, and Nagios Plugins 2.5. All four commercial solutions reached 2026R2 in September 2026.</p>



<h2 class="wp-block-heading">What Nagios can monitor</h2>



<p class="wp-block-paragraph">Nagios XI, <a href="https://www.nagios.com/products/nagios-network-analyzer/" target="_blank" rel="noopener">Nagios Network Analyzer</a>, <a href="https://www.nagios.com/products/nagios-log-server/" target="_blank" rel="noopener">Nagios Log Server</a>, and <a href="https://www.nagios.com/products/nagios-fusion/" target="_blank" rel="noopener">Nagios Fusion</a> are four separately licensed solutions. Nagios XI ships wizards that connect to Network Analyzer and Log Server, but the wizard is the connector, not the solution. Where a capability needs a separate purchase, the table says so.<br></p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th class="has-text-align-left" data-align="left">Capability</th><th class="has-text-align-left" data-align="left">Supported</th><th class="has-text-align-left" data-align="left">How</th></tr></thead><tbody><tr><td class="has-text-align-left" data-align="left">Server monitoring (Linux)</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">NCPA agent, NRPE, SSH, or agentless checks</td></tr><tr><td class="has-text-align-left" data-align="left">Server monitoring (Windows)</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">NCPA agent or agentless WMI</td></tr><tr><td class="has-text-align-left" data-align="left">Ping and ICMP</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left"><code>check_ping</code>, <code>check_icmp</code></td></tr><tr><td class="has-text-align-left" data-align="left">Network device monitoring</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">SNMP v1, v2c, and v3</td></tr><tr><td class="has-text-align-left" data-align="left">Switch and router monitoring</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">Network Switch/Router Wizard, new in Nagios XI 2026R1.4 and distributable with Nagios Mod-Gearman</td></tr><tr><td class="has-text-align-left" data-align="left">Bandwidth and traffic</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">SNMP interface counters; NetFlow via Network Analyzer</td></tr><tr><td class="has-text-align-left" data-align="left">Network discovery and mapping</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">Auto-Discovery Jobs (ping and Nmap) feeding the Auto-Discovery Wizard; Nmap scanning in Network Analyzer 2026R1 and later</td></tr><tr><td class="has-text-align-left" data-align="left">WiFi and LAN</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">SNMP against controllers and access points</td></tr><tr><td class="has-text-align-left" data-align="left">Printer monitoring</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">SNMP printer MIBs</td></tr><tr><td class="has-text-align-left" data-align="left">Hardware and environmental</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">SNMP, IPMI, vendor MIBs</td></tr><tr><td class="has-text-align-left" data-align="left">VMware and virtualization</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">vSphere Wizard, which replaced the VMware Wizard in Nagios XI 2026R1.1, and the Hyper-V Wizard. Premium</td></tr><tr><td class="has-text-align-left" data-align="left">Docker and containers</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">Docker Wizard, over the Docker Remote API or NCPA. Premium</td></tr><tr><td class="has-text-align-left" data-align="left">Kubernetes</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">Kubernetes Wizard, through NCPA on a control plane node. Premium</td></tr><tr><td class="has-text-align-left" data-align="left">Cloud (AWS, Azure)</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">Amazon EC2 and Amazon S3 Wizards, plus Cloud VM Wizards for Microsoft Azure, Google Cloud, DigitalOcean, Akamai Cloud, and Rackspace. Premium</td></tr><tr><td class="has-text-align-left" data-align="left">SQL Server and databases</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">MSSQL Server, Database, and Query Wizards and Oracle Tablespace, Serverspace, and Query Wizards, all Premium; MySQL, PostgreSQL, and MongoDB Wizards</td></tr><tr><td class="has-text-align-left" data-align="left">Website and URL monitoring</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">HTTP and HTTPS checks, certificate expiry</td></tr><tr><td class="has-text-align-left" data-align="left">Syslog and log monitoring</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">Nagios Log Server, a separate purchase</td></tr><tr><td class="has-text-align-left" data-align="left">SLA and availability reporting</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">Built into Nagios XI</td></tr><tr><td class="has-text-align-left" data-align="left">IP cameras and CCTV</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">ICMP, HTTP, and SNMP where the device exposes it</td></tr><tr><td class="has-text-align-left" data-align="left">Anything else</td><td class="has-text-align-left" data-align="left">Yes</td><td class="has-text-align-left" data-align="left">Any executable returning exit codes 0 to 3</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">Wizards marked Premium require active Maintenance &amp; Support benefits. See <a href="https://library.nagios.com/nagios-updates/nagios-xi-premium-features/" target="_blank" rel="noopener">Premium features</a>.</p>



<h2 class="wp-block-heading">What the criticism gets right</h2>



<p class="wp-block-paragraph">Nagios Core, configured by hand, is labor-intensive. Every service is defined explicitly in object configuration. There is no auto-discovery in the base engine, no built-in SLA reporting, and no dashboard layer. A team that wants those things from Core assembles them from add-ons, and that assembly is real engineering work.</p>



<p class="wp-block-paragraph">This is true, and it is the honest core of nearly every &#8220;replace Nagios&#8221; article. What those articles leave out is that it describes Nagios Core specifically, not the Nagios family.</p>



<p class="wp-block-paragraph">Nagios XI is not a different monitoring engine. It is a configuration, reporting, and access-control layer around the same Core daemon, with Configuration Wizards replacing file editing, bulk host management, RBAC with LDAP and Active Directory, Azure AD SSO (XI 2024R2, July 2025), scheduled availability and SLA reports, and a supported REST API.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">Separating these two is the single most important distinction when evaluating Nagios. Most published criticism tests Core and concludes about Nagios. See <a href="https://www.nagios.com/article/nagios-core-vs-nagios-xi/" target="_blank" rel="noopener">the main differences between Nagios Core and Nagios XI</a>.</p>
</blockquote>



<h2 class="wp-block-heading">Nagios XI distributes check execution with Mod-Gearman</h2>



<p class="wp-block-paragraph">The most repeated technical claim against Nagios is that check execution concentrates on a single master node, creating a hard ceiling.</p>



<p class="wp-block-paragraph">Nagios Mod-Gearman became an officially integrated Nagios XI feature in 2024R2.1, released August 12, 2025. It distributes check execution across worker nodes, so throughput scales horizontally instead of being bounded by one server. XI 2026R1.4&#8217;s Network Switch and Router Wizard was built specifically to be Mod-Gearman-distributable.</p>



<p class="wp-block-paragraph">Passive distribution through NRDP remains available for push-based architectures, and Nagios Fusion consolidates the view across autonomous servers that are separate for good reasons such as sites, network segmentation, or tenants</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph"><strong>Which one do you need?</strong> If one server cannot keep up, the answer is Mod-Gearman. If you have several independent servers and need one pane of glass, the answer is Fusion. These solve different problems and are routinely confused for each other. Read <a href="https://assets.nagios.com/downloads/general/docs/Distributed_Monitoring_Solutions.pdf" target="_blank" rel="noopener">Distributed Monitoring Solutions for Nagios XI </a>for more information.</p>
</blockquote>



<h2 class="wp-block-heading">Containers and cloud</h2>



<p class="wp-block-paragraph">Nagios XI ships the Kubernetes Wizard and the Zabbix Agent Wizard, alongside the Docker Wizard, the vSphere Wizard, the Hyper-V Wizard, the Amazon EC2 and Amazon S3 Wizards, and Cloud VM Wizards for Microsoft Azure, Google Cloud, DigitalOcean, Akamai Cloud, and Rackspace. These are <a href="https://library.nagios.com/nagios-updates/nagios-xi-premium-features/" target="_blank" rel="noopener">Premium features</a> and require active Maintenance &amp; Support benefits.</p>



<p class="wp-block-paragraph">The Kubernetes Wizard runs the <code>check_kubernetes.sh</code> plugin through NCPA on a control plane node. You grant NCPA access to the cluster first, using a kubeconfig file, a service account token, or <code>kubectl</code> under sudo, and the wizard validates the NCPA token before it will advance. Step 2 lists the available cluster metrics with editable Warning and Critical thresholds, and each one you select becomes a Service against the cluster Host. </p>



<h2 class="wp-block-heading">Any executable that returns an exit code is a Nagios plugin</h2>



<p class="wp-block-paragraph">Nagios checks are ordinary programs. A plugin returns 0 for OK, 1 for WARNING, 2 for CRITICAL, or 3 for UNKNOWN, and prints human-readable text followed optionally by performance data after a pipe character:</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">TEXT OUTPUT | </span><span style="color: #CE9178">&#39;label&#39;</span><span style="color: #D4D4D4">=value&#91;</span><span style="color: #569CD6">UOM</span><span style="color: #D4D4D4">&#93;;warn;crit;min;max</span></span></code></pre></div>



<p class="wp-block-paragraph">That is the entire contract. Plugins can be written in shell, Python, Perl, Go, C, or anything else that runs on the monitoring host. This interface is why thousands of community plugins exist on <a href="https://exchange.nagios.org/" target="_blank" rel="noopener">Nagios Exchange</a>, and why the same checks run unchanged across the wider Nagios-compatible ecosystem.</p>



<p class="wp-block-paragraph">Vendor integrations age out when the vendor stops maintaining them. An exit code does not.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph"><em>I think the key feature that Nagios XI presented to us is the ability for us to customize it for exactly what was needed.</em> &#8211; Alfred Chong, Director at Astiostech</p>
</blockquote>



<p class="wp-block-paragraph">Related reading: <a href="https://www.nagios.com/article/how-to-customize-nagios-xi-and-monitor-anything/" target="_blank" rel="noopener">How to Customize Nagios XI and Monitor Anything</a>.</p>



<h2 class="wp-block-heading">Security tooling and flow analysis</h2>



<p class="wp-block-paragraph">Nagios Network Analyzer 2026R1 was a full platform rewrite that bundles Suricata 8.0.3 for rules-based threat detection, Wireshark for packet capture, and Nmap for network mapping and endpoint validation, alongside NetFlow traffic and flow analysis. 2026R2, released September 30, 2026, added Suricata dashlets, Source Group dashlets, and event-based alert forwarding to Nagios Fusion. See the <a href="https://www.nagios.com/changelog/nagios-network-analyzer/" target="_blank" rel="noopener">Network Analyzer changelog</a>.</p>



<p class="wp-block-paragraph">Nagios Log Server is centralized log management and log monitoring: collection, indexing, search, dashboards, retention, and alerting on log content. It is not a SIEM, and we do not position it as one.</p>



<h2 class="wp-block-heading">Where the Nagios family still wins</h2>



<p class="wp-block-paragraph">Modern monitoring stacks are strong where there is a vendor integration or an exporter waiting for them. They are weak everywhere else.</p>



<p class="wp-block-paragraph">Real environments contain switches and routers from several vendors, UPSs, storage arrays, environmental sensors, badge readers, PLCs, line-of-business applications nobody has documented since 2014, and appliances whose only interface is SNMP. None of that has a Kubernetes operator or a hosted integration. It has an exit code and a check script, and that is exactly what Nagios was built for.</p>



<p class="wp-block-paragraph">This is also why cloud-native vendors still ship SNMP support. Heterogeneity is not a transitional phase.</p>



<p class="wp-block-paragraph">The second place Nagios wins is control. Nagios runs entirely on infrastructure you own, with no monitoring data leaving your network, no per-host SaaS metering, and no pricing change imposed from outside at renewal. For regulated, air-gapped, and government environments that is a requirement, not a preference.</p>



<h2 class="wp-block-heading">Common claims, checked against 2026</h2>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th class="has-text-align-left" data-align="left">Claim</th><th class="has-text-align-left" data-align="left">Status</th><th class="has-text-align-left" data-align="left">Evidence</th></tr></thead><tbody><tr><td class="has-text-align-left" data-align="left">Nagios hasn&#8217;t been updated in years</td><td class="has-text-align-left" data-align="left">False</td><td class="has-text-align-left" data-align="left">Eight components shipped in 2026; Nagios XI 2026R2 on 2026-09-23</td></tr><tr><td class="has-text-align-left" data-align="left">Everything runs on one master node</td><td class="has-text-align-left" data-align="left">Outdated</td><td class="has-text-align-left" data-align="left">Mod-Gearman official in XI since 2024R2.1 (2025-08-12)</td></tr><tr><td class="has-text-align-left" data-align="left">Configuration means editing text files</td><td class="has-text-align-left" data-align="left">True of Core, false of XI</td><td class="has-text-align-left" data-align="left">XI Configuration Wizards and bulk management</td></tr><tr><td class="has-text-align-left" data-align="left">No container or cloud support</td><td class="has-text-align-left" data-align="left">Outdated</td><td class="has-text-align-left" data-align="left">XI Kubernetes, Docker, and Cloud VM Wizards</td></tr><tr><td class="has-text-align-left" data-align="left">No security tooling</td><td class="has-text-align-left" data-align="left">False</td><td class="has-text-align-left" data-align="left">NNA 2026R1 bundles Suricata 8.0.3, Wireshark, Nmap</td></tr><tr><td class="has-text-align-left" data-align="left">Nagios Core is abandoned</td><td class="has-text-align-left" data-align="left">False</td><td class="has-text-align-left" data-align="left">4.5.12, 4.5.13, and 4.5.14 all shipped during 2026</td></tr><tr><td class="has-text-align-left" data-align="left">Nagios cannot do auto-discovery</td><td class="has-text-align-left" data-align="left">True of Core, false of XI</td><td class="has-text-align-left" data-align="left">XI Auto-Discovery Jobs and the Auto-Discovery Wizard</td></tr></tbody></table></figure>



<h2 class="wp-block-heading">Frequently Asked Questions</h2>


<div id="rank-math-faq" class="rank-math-block">
<div class="rank-math-list ">
<div id="faq-question-1793040359126" class="rank-math-list-item">
<h3 class="rank-math-question ">Is Nagios obsolete?</h3>
<div class="rank-math-answer ">

<p>No. Nagios XI 2026R2 shipped September 23, 2026, and ships Nagios Core 4.5.14. Four commercial Nagios solutions are in active development on roughly monthly release cycles.</p>

</div>
</div>
<div id="faq-question-1793040417110" class="rank-math-list-item">
<h3 class="rank-math-question ">Is Nagios still relevant in 2026?</h3>
<div class="rank-math-answer ">

<p>Yes. Nagios remains widely deployed for on-premises and hybrid infrastructure monitoring, particularly where monitoring data cannot leave the network and where the environment includes network devices, appliances, and legacy systems that have no vendor integration.</p>

</div>
</div>
<div id="faq-question-1793040449343" class="rank-math-list-item">
<h3 class="rank-math-question ">Is Nagios dead?</h3>
<div class="rank-math-answer ">

<p>No. Eight Nagios components shipped releases during 2026, including three Nagios Core releases carrying security fixes.</p>

</div>
</div>
<div id="faq-question-1793040484986" class="rank-math-list-item">
<h3 class="rank-math-question ">What is the difference between Nagios Core and Nagios XI?</h3>
<div class="rank-math-answer ">

<p>Nagios Core is the free, open-source monitoring engine, configured through text files. Nagios XI is a commercial layer around that same engine adding Configuration Wizards, dashboards, SLA and availability reporting, RBAC with LDAP and Active Directory, bulk management, and a supported REST API with vendor support.</p>

</div>
</div>
<div id="faq-question-1793040511568" class="rank-math-list-item">
<h3 class="rank-math-question ">Can Nagios monitor Kubernetes and containers?</h3>
<div class="rank-math-answer ">

<p>Yes. The Nagios XI Kubernetes Wizard runs the check_kubernetes.sh plugin through NCPA on a control plane node, and you select which cluster metrics to monitor, with Warning and Critical thresholds, in Step 2. Containers are covered by the Docker Wizard, over the Docker Remote API or NCPA. Both are Premium features requiring active Maintenance &amp; Support benefits.</p>

</div>
</div>
<div id="faq-question-1793040526698" class="rank-math-list-item">
<h3 class="rank-math-question ">Can Nagios monitor Windows servers?</h3>
<div class="rank-math-answer ">

<p>Yes. NCPA, the Nagios Cross-Platform Agent, installs on Windows and requires no Linux command-line work on the monitored host. Agentless WMI monitoring is also supported.</p>

</div>
</div>
<div id="faq-question-1793040553627" class="rank-math-list-item">
<h3 class="rank-math-question ">How many checks can Nagios handle?</h3>
<div class="rank-math-answer ">

<p>Check execution scales horizontally. Nagios Mod-Gearman, an official Nagios XI feature since 2024R2.1, distributes execution across worker nodes rather than concentrating it on the monitoring server.</p>

</div>
</div>
<div id="faq-question-1793040571960" class="rank-math-list-item">
<h3 class="rank-math-question ">Is Nagios free?</h3>
<div class="rank-math-answer ">

<p>Nagios Core is free and open source under the GPL. Nagios XI is commercially licensed per monitored Node and includes a free tier for up to 7 Nodes. Nagios XI offers a free 30-day trial.</p>

</div>
</div>
</div>
</div>


<div class="wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex">
<div class="wp-block-button"><a class="wp-block-button__link wp-element-button">Try Nagios XI free for 30 days</a></div>
</div>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
