# A09:2025 - Security Logging and Alerting Failures

> Inability to detect, escalate, and respond to breaches due to insufficient logging.

- **Category**: Owasp Security
- **Subcategory**: top10_2025
- **Canonical URL**: https://designpattern.fyi/owasp_security/a09_logging_failures/

---

## Description
'**Intent**: Enable effective detection, escalation, and response to security incidents through comprehensive logging and monitoring.

**Context**: Without sufficient logging and monitoring, breaches cannot be detected. Most breach studies show time to detect a breach is over 200 days. Insufficient logging allows attackers to further attack systems undetected.

**Solution**: Log all authentication, access control, and server-side input validation failures. Ensure logs are in a format suitable for log management solutions. Establish effective monitoring and alerting. Create an incident response plan.'



## Use Cases
Use to ensure visibility into security events, enable incident response, and meet compliance requirements.





## Trade-offs


### Advantages

- Enables breach detection

- Supports incident response

- Provides forensic evidence

- Meets compliance requirements




### Considerations & Drawbacks

- Log storage costs can be significant

- Excessive logging impacts performance

- Requires trained staff to monitor







---
**Reference**: [Original Source](https://owasp.org/Top10/2025)

