🚀 Join our AI Wargame at Black Hat Asia and our Workshop + Wargame at NDC Sydney .


Logging of Excessive Data

The application generates an excessive volume of log data, resulting in oversized log files and reduced visibility into security-relevant events. Excessive logging can make operational monitoring, incident detection, troubleshooting, and forensic investigations more difficult by obscuring important events within large amounts of low-value or repetitive log entries. In addition, excessive log generation may consume unnecessary system resources such as disk space, storage quotas, network bandwidth, or processing capacity, potentially impacting system performance and availability.

Remediation

Review logging practices and ensure that only operationally and security-relevant events are recorded in production environments. Reduce unnecessary verbosity, suppress repetitive or duplicate log entries where appropriate, implement log rotation and retention policies, and configure monitoring to alert on abnormal log growth. Logging levels should be adjusted appropriately when transitioning from development or debugging environments into production.

Metadata

  • Severity: low
  • Slug: logging-of-excessive-data

CWEs

  • 779: Logging of Excessive Data

OWASP

  • A09:2021: Security Logging and Monitoring Failures

Available Labs

Open Gcp labs in SecDim Play for this vulnerability.

Deco line
Deco line

Play AppSec WarGames

Want to skill-up in secure coding and AppSec? Try SecDim Wargames to learn how to find, hack and fix security vulnerabilities inspired by real-world incidents.

Deco line
Deco line

Got a comment?

Join our secure coding and AppSec community. A discussion board to share and discuss all aspects of secure programming, AppSec, DevSecOps, fuzzing, cloudsec, AIsec code review, and more.

Read more