Course contentsShow
← Security
Lesson 1468 of 3,05230. Operating System Security - MonitoringFree lesson

Logging Architecture Components

Understanding log sources, log daemons, log files, and centralized logging infrastructure.

Logging Architecture Components

You'll learn the key building blocks of a secure and scalable logging system, from where logs originate to where they're stored and analyzed.

The Big Picture

Think of logging architecture like a city's emergency response system: events happen at various locations (log sources), dispatchers receive and route them (log daemons), records are filed (log files), and a central command center coordinates everything (centralized logging infrastructure). Understanding these components helps you design robust monitoring and incident response capabilities.

Core Components

Log Sources

These are the origins of log data—applications, services, kernel events, authentication attempts, firewalls, and databases. Every process that generates security-relevant events is a log source. In Linux, sources might include SSH daemon, kernel messages, web servers, or audit subsystems.

Log Daemons

Log daemons are the middleware that collect, filter, and route log messages. On Linux systems, rsyslog or syslog-ng receive messages from local sources via /dev/log socket or network connections, then route them based on facility and severity. They're the traffic controllers of your logging system.

Log Files

These are the local storage destinations—typically text files in /var/log/. Examples include /var/log/auth.log for authentication events, /var/log/syslog for general messages, or application-specific logs. Log files provide immediate, local access but require rotation to prevent disk exhaustion.

Centralized Logging Infrastructure

For security operations, local logs aren't enough—attackers often delete them. Centralized logging forwards logs to remote collectors (like Elasticsearch, Splunk, or dedicated SIEM systems) in real-time. This provides tamper resistance, correlation across systems, long-term retention, and powerful search capabilities.

Key Takeaway: Modern logging architecture separates concerns—sources generate events, daemons route them, local files provide quick access, and centralized infrastructure ensures security, durability, and analysis at scale.