Theory · 9 min · Web attack monitoring
Web access logs and attack patterns
Read an access log line and spot injection, traversal and scanning.
A web server access log (Apache combined, nginx, IIS W3C) records each request: client IP, time, method, path and query, status code, response size, referrer and user agent.
Injection is number five in the OWASP Top 10:2025. In logs it looks like SQL in a parameter (' OR 1=1--, UNION SELECT), often URL-encoded. Path traversal tries ../ sequences to read files outside the web root.
Scanners leave volume: hundreds of 404s for admin pages and backup files from one IP, with tool user agents. Most are background noise from the internet.
The status code and size tell you if it worked. A 200 with a response much larger than normal for that page is the line to escalate; a 403 or 404 usually is not.
Your turn: select the field that proves it. Select the field that shows this SQL injection attempt probably returned data.
Do the interactive check Free, in the browser.
Sources
- OWASP Top 10:2025 OWASP
- SQL Injection OWASP
- Apache HTTP Server: log files Apache