Web Application Firewall
Also called WAF.
A filter that inspects HTTP traffic to block web attacks.
What it is
A control positioned in front of a web application that analyzes incoming HTTP requests and responses against rules and signatures to detect and block attacks such as injection and cross-site scripting.
Why it matters
A WAF buys time and visibility against web exploitation and is a rich log source for investigations, though it is a mitigation rather than a fix and can be bypassed, so it complements secure code rather than replacing it.
In practice
A rule pattern blocking requests that contain telltale SQL-injection syntax before they reach the app.
What to look for
- Blocked requests and the rules that fired.
- Rules in log only mode that should block.
- Traffic that reaches the origin around the WAF.
Common mistake
Treating it as the fix. It buys time; the code still needs to be fixed.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- SQL Injection: Injecting SQL through input to manipulate a database query.
- Cross-Site Scripting: Injecting attacker script that runs in other users' browsers.
- Security Headers: HTTP response headers that harden the browser's handling of a site.