Input Validation
Checking that incoming data matches expected type, format, and range.
What it is
The practice of verifying that data entering an application conforms to strict expectations (type, length, format, and allowed values), and rejecting anything that does not, ideally against an allow-list.
Why it matters
Most injection and tampering attacks stem from trusting input, so sound validation is a primary defense, and its gaps are usually the root cause traced back during an exploited-app investigation.
In practice
Rejecting an order quantity field that contains letters or SQL syntax instead of a positive number.
What to look for
- Fields that accept any type or length.
- Validation done only in the browser.
- Allow lists versus deny lists.
Common mistake
Validating on the client only. The server must check every input.
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
- Output Encoding: Encoding data for its context so it renders as text, not code.
- SQL Injection: Injecting SQL through input to manipulate a database query.
- Parameter Tampering: Altering request fields to change application behavior or access.