Logging of Excessive Data
This vulnerability occurs when an application records more information than necessary in its logs, making log files difficult to analyze and potentially slowing down incident response or security investigations.
While comprehensive logging is essential for debugging during development, excessive logging in a live production environment creates significant operational problems. Overly verbose logs can overwhelm system administrators, making it harder to spot genuine security alerts or performance issues amidst the noise. This clutter can inadvertently provide cover for an attacker, as critical malicious activity gets lost in a flood of irrelevant data. From a security perspective, excessive logging also complicates forensic analysis after a breach, as investigators must sift through mountains of data to find relevant events. Furthermore, it can impact system performance and storage costs, and may even lead to accidentally recording sensitive information (like passwords or personal data), creating additional security risks. The goal is to implement smart, targeted logging that captures what you need without drowning you in data.
Impact: DoS: Resource Consumption (CPU)DoS: Resource Consumption (Other)
Log files can become so large that they consume excessive resources, such as disk and CPU, which can hinder the performance of the system.
Impact: Hide Activities
Logging too much information can make the log files of less use to forensics analysts and developers when trying to diagnose a problem or recover from an attack.
Impact: Hide Activities
If system administrators are unable to effectively process log files, attempted attacks may go undetected, possibly leading to eventual system compromise.
Low
- ISA/IEC 62443
- ISA/IEC 62443
- ISA/IEC 62443
- ISA/IEC 62443