SIEM Logging: Security Log Aggregation, Processing and Analysis - Exabeam

SIEM Logging: Security Log Aggregation, Processing and Analysis

Event logs are a foundation of modern security monitoring, investigation and forensics, and SIEM systems. In this chapter, you’ll learn in-depth how logs are aggregated, processed, and stored, and how they are used in the security operations center (SOC).

SIEM vs. log management: What is the difference?

SIEM and log management are similar in the following respects:

  • Both tools collect, store, and retrieve log data in real time across operating systems, security devices, network infrastructure, systems, and applications.
  • Both tools can be used for operational reporting and compliance auditing.
  • Both tools enable IT and security teams to manage and aggregate logs, define criteria for alerting, and access full log data for further investigation of incidents.

SIEM and log management have the following key differences:

  • SIEM combines event logs with contextual information about users, assets, threats, and vulnerabilities and can help correlate related events. Log management usually does not provide contextual log analysis. It is up to the security analyst to interpret the data and determine if threats are real.
  • SIEM provides real-time and historical threat analysis based on log data. It also sends alerts when potential security threats are detected, prioritizes threats based on severity, and helps security professionals systematically address issues. Log management tools typically lack these features, making them less suitable for threat detection and incident response scenarios.
  • SIEM aggregates and normalizes logs into a unified format to ensure consistency across all log data. Log management typically does not transform log data from different sources, resulting in inconsistencies and variations in the collected data.

What is log monitoring?

There is a wealth of information in log files that can help identify problems and patterns in production systems. Log monitoring involves scanning log files, searching for patterns, rules, or inferred behavior that indicates important events, and triggering an alert sent to operations or security staff.

Log monitoring can help identify problems before they are experienced by users. It can uncover suspicious behavior that might represent an attack on organizational systems. It can also help record baseline behavior of devices, systems, or users, in order to identify anomalies that require investigation.


How does SIEM logging work? Basics of security event logs

Log aggregation and log monitoring is a central activity for security teams. Collecting log information from critical systems and security tools, and analyzing those logs, is the most common way to identify anomalous or suspicious events, which might represent a security incident.

The two basic concepts of security log management are events and incidents — an event is something that happens on a network on an endpoint device. One or more events can be identified as an incident — an attack, violation of security policies, unauthorized access, or change to data or systems without the owner’s consent.

Common security-relevant log events

  • Report from antivirus software that a device is infected by malware
  • Report from firewall about traffic to/from a prohibited network address
  • Attempt to access a critical system from an unknown host or IP address
  • Repeated failed attempts to access a critical system
  • Change in user privileges
  • Usage of insecure or prohibited protocols/ports

Common security incidents

  • Malicious email received and activated by organizational users
  • Malicious website accessed by organizational users (e.g., drive-by download)
  • Improper or prohibited usage by an authorized user
  • Unauthorized access
  • An attempt to compromise, deny access to, or delete organizational systems
  • Loss or theft of equipment, such as employee laptops, servers
  • Data leak or malware infection via removable media

SIEM log analysis

In the security world, the primary system that aggregates logs, monitors them, and generates alerts about possible security systems, is a Security Information and Event Management (SIEM) solution.

SIEM platforms aggregate historical log data and real-time alerts from security solutions and IT systems like email servers, web servers, and authentication systems.

They analyze the data and establish relationships that help identify anomalies, vulnerabilities, and incidents. The SIEM’s main focus is on security-related events such as suspicious logins, malware, or escalation of privileges.

The SIEM’s goal is to identify which events have security significance and should be reviewed by a human analyst, and sends notifications for those events. Modern SIEMs also provide extensive dashboards and data visualization tools, allowing analysts to actively seek data points that might indicate a security incident — known as threat hunting.

Traditional SIEM log analysis

Traditionally, the SIEM used two techniques to generate alerts from log data: correlation rules, specifying a sequence of events that indicates an anomaly, which could represent a security threat, vulnerability, or active security incident; and vulnerabilities and risk assessment, which involves scanning networks for known attack patterns and vulnerabilities.

The drawback of these older techniques is that they generate a lot of false positives, and are not successful at detecting new and unexpected event types

Next-generation SIEM log analysis

Advanced SIEMs use technology called User and Entity Behavior Analytics (UEBA). UEBA leverages machine learning to look at patterns of human behavior, automatically establish baselines, and intelligently identify suspicious or anomalous behavior.

This can help detect risks that are unknown or difficult to define with correlation rules, such as insider threats, targeted attacks, fraud, and anomalies across long periods of time or across multiple organizational systems.


Using endpoint logs for security

Traditionally, monitoring and security efforts focused on network traffic to identify threats. Today, there is a growing focus on endpoints, such as desktop computers, servers, and mobile devices. Endpoints are frequently targeted by threat actors who can bypass traditional security measures — for example, a laptop forgotten on a train can be stolen by an attacker and used to penetrate organizational systems. Without careful monitoring of the laptop’s activity, this and similar attacks could go undetected.

Windows Event Logs

The Windows operating system provides an event logging protocol that allows applications, and the operating system itself, to log important hardware and software events. The events can be viewed directly by an administrator using the Windows Event Viewer.

Which events are logged?

Events logged in Windows Event Logs include application installations, security management (see Windows Security Logs below), initial startup operations, and problems or errors. All these event types can have security significance, and should be monitored by log aggregation and monitoring tools.

Example of Windows Event Log

Warning               5/11/2018 10:29:47 AM Kernel-Event Tracing      1 Logging

Windows Security Logs

The Windows Security Log is a part of the Windows Event Log framework. It contains security-related events specified by administrators using the system’s audit policy. Microsoft describes the Security Log as “Your Best and Last Defense” when investigating security breaches on Windows systems.

Which events are logged?

The following types of Windows log events can be defined as security events: account log on, account management, directory service access, logon, object access (for example, file access), policy change, privilege use, tracking of system processes, system events.

iOS logs and iOS crash reports

Unlike Windows and Linux, the iOS operating system does not log system and application events by default, with the exception of application crash reports. iOS 10.0 onwards offers a logging API that allows specific applications to log application events and store them in a centralized location on disk. Log messages can be viewed using the Console app of the log command-line tool.

Because iOS does not provide convenient remote access to logs, several third-party solutions have emerged that allow for remote collection and aggregation of iOS logs.

Linux event logs

Linux logs record a timeline of events that occur in the Linux operating system and applications. Central system logs are stored in the /var/log directory, and logs for specific applications may be stored in the application folder, for example, ‘~/.chrome/Crash Reports’ for Google Chrome.

Which events are logged?

There are Linux log files for system events, kernel, package managers, boot processes, Xorg, Apache, MySQL, and other common services. As in Windows, all these events could possibly have security significance.

Which are the most critical Linux logs to monitor?

  • /var/log/syslog or /var/log/messages — stores all activity data across the Linux system.
  • /var/log/auth.log or /var/log/secure — stores authentication logs
  • /var/log/boot.log — messages logged during startup
  • /var/log/maillog or var/log/mail.log — events related to email servers
  • /var/log/kern — Kernel logs
  • /var/log/dmesg — device driver logs
  • /var/log/faillog — failed login attempts
  • /var/log/cron — events related to cron jobs or the cron daemon
  • /var/log/yum.log — events related to installation of yum packages
  • /var/log/httpd/ — HTTP errors and access logs containing all HTTP requests
  • /var/log/mysqld.log or /var/log/mysql.log — MySQL log files

Managing Endpoint Detection and Response (EDR) logs

Endpoint Detection and Response (EDR) technology helps to detect, investigate, and mitigate security incidents on organizational endpoints. EDR is complementary to traditional endpoint tools such as antivirus, Data Loss Prevention (DLP), and SIEM. EDR technology provides visibility into events taking place on endpoints, including application access and activity, operating system operations, creation, modification, copying and movement of data, memory usage, and user access to predefined sensitive data.

EDR systems provide aggregated logs that allow security teams to analyze and explore events from across the enterprise endpoint portfolio.

Symantec Endpoint Protection logs

Symantec Endpoint Protection is a security suite that includes intrusion prevention, firewall, and anti-malware. Endpoint Protection logs contain information about configuration changes, security-related activities such as virus detections, errors on specific endpoints, and traffic that enters and exits the endpoint.

Which events are logged?

Symantec Endpoint Protection log types include:

  • Policy modifications
  • Application and device control — events on endpoint devices where some behavior was blocked
  • Compliance logs
  • Computer status — operational status such as computer name, IP address, infection status
  • Deception logs — attacker interaction with “honeypots” deployed by the security solution
  • Network and host exploit mitigation
  • Virus scan events
  • Risk events detected by Symantec
  • System log — information about operating system and services.

McAfee Endpoint Security

McAfee Endpoint Security provides centralized management for endpoint devices, anti-malware protection, application containment, web security, threat forensics, and machine learning analysis for the detection of unknown threats.

The solution allows you to set each endpoint device to one of three log levels: no logging, event logging, and debug logging. Logs are saved on the endpoints in the McAfee folder.

Which events are logged?

McAfee Endpoint Security saves several log files on each endpoint device:

  • myAgent.log — aggregate log file containing historic logs
  • myNotices.log — notices and warnings generated by the McAfee agent
  • myUninstall.log — software uninstall events
  • myUpdate.log — software update events
  • myInstall.log — software installation events

Managing firewall logs

Firewall logs are extremely valuable for security analysis, because they contain trails of almost all traffic flowing into and out of your network. If malicious activity is occurring, even if it cannot be detected by known malware or attack signatures, it will be captured by the firewall and can probably be seen by analyzing firewall logs for unusual behavior.

For example, when a zero-day virus infects computers on your network, even if it cannot be detected yet by antivirus software, firewall logs may show unusually high numbers of denied connections, or allowed connections, with suspicious remote hosts. A routine review of firewall logs can discover trojans or rootkits trying to connect to their command and control systems via IRC, over the firewall.

Cisco syslog and logging levels

Cisco routers save logs in syslog format, and also allow logs to be viewed by the admin interface. Messages are tagged with message codes — for example, most denied connections have a message code in the 106001 to 106023 range. Most firewall devices do not have local storage space, so logs must be configured to be sent elsewhere — Cisco allows saving logs to a syslog server on the network, via SMTP, via console port, telnet, or several other options.

What log entries are important to analyze?

  • Connections allowed by firewall security policies — these can help spot “holes” in the security policies
  • Connections denied by firewall security policies — might contain suspicious or attack behavior
  • Using the deny rate logging feature can show DoS or brute force attacks
  • IDS activity messages — show attacks identified by Cisco Intrusion Detection features
  • User authentication and command usage — lets you review and audit firewall policy changes
  • Bandwidth usage — shows connections by duration and traffic volume — outliers could be interesting to investigate
  • Protocol usage messages — show protocols and port numbers — can show unusual or insecure protocols used on the network
  • NAT or PAT connections — check if you receive a report of malicious activity coming inside your network

Check Point logging

Check Point routers can save logs in syslog format, and also allow logs to be viewed over an admin interface. Check Point routers maintain a security log that saves events that are deemed to have security significance.

Categories of events saved to security log:

  • Connection accepted
  • Connection decrypted
  • Connection dropped
  • Connection encrypted
  • Connection rejected
  • Connection monitored — a security event was monitored but not blocked according to current firewall policy
  • URL allowed — URL allowed for access by internal users
  • URL filtered — URL disallowed for access by internal users
  • Virus detected — virus detected in an email
  • Potential spam stamped — email marked as potential spam
  • Potential spam detected — email rejected as potential spam
  • Mail allowed — non-spam email was logged
  • VStream Antivirus blocked a connection

Severity levels in the Check Point security log:

  • Red — connection attempts blocked by the firewall, by security policy downloaded from the Service Center or user-defined rules
  • Orange — traffic detected as suspicious but accepted by the firewall
  • Green — traffic accepted by the firewall

Log management and next-generation SIEMs

Log management has always been complex, and is becoming more so with the proliferation of network devices, endpoints, microservices, and cloud services, and exponentially increasing traffic and data volumes.

In a security environment, next-generation Security Information and Event Management (SIEM) solutions can help manage and extract value from security-relevant log events:

  • Next-generation SIEMs are based on data lake technology which can store unlimited data volumes of historical logs
  • Next-generation SIEMs come with User and Entity Behavior Analytics technology which can automatically establish baseline activity for devices and users, and identify anomalous or suspicious behavior
  • Next-generation SIEMs provide advanced data exploration capabilities which can help security analysts perform threat hunting by actively searching through logs

Exabeam is an example of a next-generation SIEM platform that provides these capabilities. It can pull together logs from enterprise systems and security tools and perform the complete log management process, including log collection and aggregation, log processing, log analysis using advanced analytics and UEBA technology, and alerting about security incidents.

See Exabeam in action: Request a demo