Offline buffering is a log shipper’s ability to store events in memory or on disk while the destination is unreachable, then forward them automatically once the connection recovers. Without it, every SIEM outage, network partition, or agent restart becomes a permanent gap in your security telemetry. Every SIEM eventually goes down. So does the WAN link to your central collector, and eventually the host running the agent itself. None of these events should cost you log data, but whether they do depends on how your log shipper buffers when it can’t deliver data to the destination.

USB device auditing on Windows means tracking three things: when a device connects, what files move to or from it, and whether your device-control policy stopped what it was supposed to stop. Windows can record all three. Almost none of it is enabled by default. Honeywell’s 2025 Cyber Threat Report counted 1,826 unique USB-borne threats in the first quarter of 2025 alone, including 124 that were completely new. These findings came from Secure Media Exchange scanning stations at industrial sites.

A single Windows Event Collector (WEC) server has three documented scaling limits: disk write speed, concurrent WinRM connections, and registry growth from per-client bookmark data. Microsoft’s current guidance is to plan for roughly 3,000 events per second on average across all subscriptions on commodity hardware. The "10k × 10k" rule of thumb (up to 10,000 clients and 10,000 EPS per collector) still circulates widely. IBM QRadar and Juniper JSA documentation still quote it, both attributing it to Microsoft’s article.

Windows records scheduled task activity in two separate event logs. The Security log holds event IDs 4698-4702, covering task creation, deletion, turning on, turning off, and updates, with the full task definition XML attached. The Microsoft-Windows-TaskScheduler/Operational log holds event IDs 106, 140, and 141 for registration changes, plus 100, 200, and 201 for execution. Windows doesn’t switch on either source by default: Microsoft’s own Tarrask analysis states that "neither of these are audited by default and must be explicitly turned on by an administrator.

We are happy to announce the latest release of NXLog Platform, version 1.14. This update adds an entitlements usage summary to the NXLog Platform UI and extends NXLog Agent support to the newest Ubuntu 26.04 LTS release and Red Hat Enterprise Linux 5 for long-lived legacy deployments. Read on for more details about these updates. See data source entitlements and usage at a glance NXLog Platform 1.14 adds entitlements usage visibility to the NXLog Platform UI, giving you a clear breakdown of how your data source license is used without contacting support.

Some of the most critical systems in your infrastructure are also the oldest. If you operate in energy, manufacturing, or government, chances are you have hosts still running Red Hat Enterprise Linux 5 or CentOS 5. Not because anyone forgot to upgrade them, but because upgrading them is not an option. The OS is frozen by compliance requirements, tied to certified industrial equipment, or locked to software that would break on anything newer.