Web Application Firewall (WAF) telemetry is generally classified as high-value, high-noise security data before appropriate filtering, normalization, and detection tuning have been implemented.
An internet-facing WAF observes HTTP and HTTPS requests directed toward applications exposed to external networks. Its logs can contain valuable indicators of SQL injection, cross-site scripting, command injection, directory traversal, malicious automation, reconnaissance, and attempted exploitation of application vulnerabilities.
Consequently, WAF telemetry provides significant visibility into attack activity affecting customer-facing applications.
However, WAF deployments also process substantial volumes of legitimate application traffic, automated scanning, web crawlers, unsuccessful requests, and other events that may not represent meaningful security threats.
Without appropriate tuning, these records can produce excessive alert volume, unnecessary storage consumption, and operational noise.
Splunk Enterprise Security supports analyzing web telemetry through normalized security data, statistical comparisons, and detection searches. Analysts can improve the signal-to-noise ratio by applying contextual enrichment, filtering known benign activity, correlating multiple indicators, and developing application-specific baselines.
The objective should not be to discard all routine traffic indiscriminately, because seemingly benign events may provide essential investigative context.
Option A would be more appropriate after successful tuning. Options C and D underestimate the security value of internet-facing WAF telemetry.
Official reference / study topic: Splunk Enterprise Security, Web Intelligence Dashboards and Relevant Detection Use Cases.
===============
Submit