✦Template Printable Ideas Insights

Security Logging & Monitoring: Examples of Failure

By

Security logging and monitoring are critical components of any organization's defensive strategy. They provide visibility into system activities, helping detect anomalies and respond to security incidents swiftly. However, these systems can fail or be manipulated, leaving organizations vulnerable. Let's delve into some common examples of security logging and monitoring failures.

Poor logging practices, insufficient monitoring, or lack of integration between these systems can lead to critical information being missed or ignored. In this article, we'll explore common pitfalls in security logging and monitoring, their real-world impacts, and provide best practices to avoid similar failures.

Weak or Inadequate Log Management

Insufficient or improper log management can hinder an organization's ability to detect and respond to security incidents. One common failure is not collecting and storing logs from all relevant systems and applications. This siloed approach can lead to blind spots in security visibility.

Security Logging and Monitoring Failure Attack Example
Security Logging and Monitoring Failure Attack Example
a hand holding a magnifying glass with a red check mark on it
a hand holding a magnifying glass with a red check mark on it
System Error and Network Failure Illustration
System Error and Network Failure Illustration

Another critical failure is not rotating logs regularly. This practice is crucial to prevent log tampering and ensure the integrity of historical logs. Additionally, failing to monitor logs in real-time for suspicious activity can delay detection and response to security incidents.

Silos in Logging Data

الأمام When logs are not collected and correlated from all relevant systems, it can hinder threat detection and incident response. For instance, an attacker could exploit a vulnerability in a system that is not logging to your Security Information and Event Management (SIEM) system, making it harder to detect their activities elsewhere in your network.

the windows event log is shown in this document
the windows event log is shown in this document
🛡 Types of Security Logs | Chirag Goswami
🛡 Types of Security Logs | Chirag Goswami
the microsoft event log is shown in this document
the microsoft event log is shown in this document

A clear example of this was the 2017 Equifax data breach. Attackers exploited a vulnerability in an unpatched web application that wasn't part of Equifax's logging system, allowing them to remain undetected for 60 days.

Poor Log Rotational Practices

اتش Proper log rotation is crucial to maintain log integrity and prevent log tampering. Without regular log rotation, an attacker could replace existing logs with falsified ones, covering their tracks. Moreover, insufficient log storage can lead to the loss of critical historical data, hindering incident investigations and regulatory compliance.

In the 2016 Democratic National Committee (DNC) data breach, attackers altered log timestamps to cover their tracks. This manipulation would have been significantly more challenging if proper log rotation practices had been in place.

the windows event log is shown in this document
the windows event log is shown in this document
Top Log Terminologies
Top Log Terminologies
Incident Response Explained Simply
Incident Response Explained Simply
the windows event log is shown in this screenshote, and it appears to be an
the windows event log is shown in this screenshote, and it appears to be an
Cybersecurity Monitoring and Response Flow Computer Knowledge, Software Engineer, Linux, No Response
Cybersecurity Monitoring and Response Flow Computer Knowledge, Software Engineer, Linux, No Response
Why Your Logs Decide If You Sleep at 2AM 😴
Why Your Logs Decide If You Sleep at 2AM 😴

Insufficient Monitoring and Alerting

Another common failure is not monitoring logs in real-time or setting up effective alerting mechanisms. This can lead to delayed detection and response to security incidents, resulting in extended dwell time for attackers within a network.

Inadequate monitoring can also lead to alert fatigue, where security teams become desensitized to frequent alerts, potentially missing genuine security incidents. Moreover, not validating and tuning alerts can result in an overwhelming volume of false positives, diluting the effectiveness of the alerting system.

Inadequate Real-time Monitoring

ت In real-time monitoring ensures timely detection and response to security incidents. Without it, attackers can maintain persistence in a network for extended periods. For instance, the 2013 Target data breach went undetected for 14 days due to inadequate monitoring and alerting processes.

an info sheet with instructions for how to use the incident response chart in this workbook
an info sheet with instructions for how to use the incident response chart in this workbook
owasp top 10 web application vulnerabilities
owasp top 10 web application vulnerabilities
Incident Management Response Process Watermark
Incident Management Response Process Watermark

Real-time monitoring can be augmented with User and Entity Behavior Analytics (UEBA), which uses machine learning to detect anomalous behavior and insider threats that traditional rule-based systems might miss.

Unvalidated and Tuned Alerts

ون Poorly validated and tuned alerts can lead to alert fatigue and ineffective incident response. Unnecessarily frequent alerts can desensitize security teams, making them more likely to miss critical alerts. Conversely, too few alerts can result in a delayed response to security incidents.

According to a report by Exabeam, 82% of security professionals have experienced alert fatigue. The 2017 WannaCry ransomware attack highlights the importance of alert tuning. Hospitals affected by WannaCry were slow to respond due to the sheer volume of alerts generated by the attack, many of which were false positives.

To conclude, security logging and monitoring failures can have severe consequences, including data breaches, extended dwell time for attackers, and significant financial losses. However, organizations can mitigate these failures by implementing robust log management practices, investing in real-time monitoring, and validating and tuning their alerts. By doing so, they can enhance their security posture and better protect their assets.