Join our Newsletter — 33% off our NHI Course
Home› FAQ› Cyber Security› What is the difference between reliable and non-reliable…
Cyber Security

What is the difference between reliable and non-reliable disk buffering in syslog-ng?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated November 1, 2026 Domain: Cyber Security

Reliable disk buffering writes the cache and output queue to disk, so nearly all outgoing messages survive abnormal termination. Non-reliable buffering keeps the cache and queue in memory, but spills to disk when needed and can still lose in-flight messages if the process or host crashes. Reliable mode improves durability, while non-reliable mode usually offers better performance and lower disk usage.

How reliable disk buffering changes syslog-ng delivery behaviour

The practical difference is where syslog-ng keeps queued messages when the destination cannot accept them immediately. Reliable buffering puts the queue on disk so a restart or crash is far less likely to lose messages. Non-reliable buffering keeps the working queue in memory and only uses disk as overflow storage, so it is faster but less durable under failure.

The choice is really a trade-off between delivery assurance and throughput. If the log stream is operationally important, durable buffering is the safer default. If the log path is high-volume and short-lived loss is acceptable, non-reliable buffering can be a better fit because it reduces disk activity and overhead.

For teams managing log pipelines at scale, Log Management and Retention Guide is the most relevant companion because buffering decisions sit inside the larger questions of collection, retention, storage tiers and log integrity.

What failure mode each buffering type is protecting against

Reliable disk buffering is designed for abnormal termination: process crashes, host reboots, or other outages that interrupt forwarding. It aims to preserve nearly all queued outgoing events so the delivery pipeline can resume with minimal loss. Non-reliable buffering tolerates ordinary backpressure, but if the process or host fails while messages are still in flight, those messages can disappear even if the queue had temporarily spilled to disk.

That means the operational question is not only whether logs are buffered, but whether the messages still matter after a failure. For audit, incident response, or regulated logging, losing a small tail of messages can be material. For transient telemetry where duplicates and gaps are acceptable, the extra durability may not justify the cost.

When the log path is part of a broader control environment, NIST SP 800-53 Rev 5 Security and Privacy Controls is a useful reference point because logging, auditability and system integrity expectations often determine whether durable delivery is necessary.

When to prefer one mode over the other

Prefer reliable disk buffering when message loss would weaken investigation, compliance evidence, or chain-of-events reconstruction. Prefer non-reliable buffering when you care more about performance, lower storage overhead, and acceptable best-effort delivery than about near-complete persistence across failures. In practice, many teams reserve reliable buffering for high-value log sources and use lighter buffering for less critical streams.

What to verify: check whether the downstream destination, disk capacity, and queue settings match the failure tolerance of the log source. A buffering mode is only as useful as the recovery path around it, so the team should confirm that the queue can actually survive the outage class they are trying to absorb.

Trade-off: reliable buffering improves durability but increases reliance on local disk and may add overhead; non-reliable buffering usually reduces that overhead but accepts a higher probability of loss during crashes or abrupt shutdowns.

Practitioner takeaway: choose reliable buffering for logs you would regret losing after a crash, and treat non-reliable buffering as an optimisation for throughput or cost only when some message loss is operationally acceptable.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AU-2 — Event LoggingSyslog-ng buffering affects audit log persistence and delivery reliability.
AU-6 — Audit Record Review, Analysis, and ReportingBuffered logs are only useful if analysts can recover and review them after disruption.
Recommendation — Ensure log delivery survives outages where audit evidence must be retained. Verify queued logs remain reviewable after restart or destination failure.
CIS Controls v8CIS-8 — Audit Log ManagementDisk buffering is part of keeping security logs available and intact under failure.
Recommendation — Retain logs on durable storage where audit continuity matters.
ISO/IEC 27001:2022A.8.15 — LoggingThe topic directly concerns how logs are stored and preserved for operational security.
Recommendation — Define logging durability requirements before choosing buffering mode.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 1, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org