Security Logging and Alerting Failures
This category helps detect, escalate, and respond to active breaches. Without logging and alerting, breaches cannot be detected in time to respond.
Overview
Renamed from 'Security Logging and Monitoring Failures' to emphasize actionable alerts over mere monitoring. This category is challenging to test for and isn't well represented in CVE/CVSS data.
How Attackers Exploit This
Understanding attack patterns helps you build better defenses. These are the techniques security teams watch for.
Undetected breach
Without proper logging and alerting, attackers can operate undetected for extended periods, exfiltrating data gradually.
Log tampering
Attackers with access modify or delete logs to cover their tracks.
Alert fatigue exploitation
Attackers generate noise to cause alert fatigue, then conduct real attacks during the confusion.
How to Prevent
- Log all login, access control, and server-side input validation failures
- Ensure logs are in a format easily consumed by log management solutions
- Ensure log data is encoded correctly to prevent injection attacks
- Ensure high-value transactions have an audit trail with integrity controls
- Establish effective alerting with actionable thresholds
- Establish an incident response and recovery plan
- Use SIEM or centralized logging with real-time alerting
CWEs with Shoulder Detection (3)
These CWEs have Shoulder detection rules. Click to see specific vulnerabilities and fixes.
Other Mapped CWEs (2)
These CWEs are mapped to this category. Use MITRE references for guidance.