Web Application Security for Cyber Securitys
Web application security focuses on flaws in websites and APIs. The OWASP Top 10 lists the most common risks, including broken access control, injection and cryptographic failures. Testers examine how inputs, sessions and permissions are handled, and the same ideas extend to REST APIs and mobile apps.
Stage: Offensive Security · Part of the Cyber Security roadmap · Last reviewed 19 November 2026
What to learn in Web Application Security
- Exploit and then fix a SQL injection using parameterised queries
- Demonstrate reflected cross-site scripting and prevent it with output encoding
- Test for broken access control by changing an object ID in a request
- Intercept and modify requests with Burp Suite
- Describe common API flaws such as excessive data exposure
Web Application Security interview questions
How do you prevent SQL injection?
Use parameterised queries or prepared statements so user input is always treated as data and never as SQL code. Add least-privilege database accounts and input validation as extra layers. Escaping alone is error-prone.
What is an IDOR vulnerability?
An insecure direct object reference happens when an application exposes an identifier, like an invoice number, and does not check that the logged-in user owns that object. Changing the id in the request reveals other users' data. It falls under broken access control.
Where Web Application Security fits in the Cyber Security roadmap
Web Application Security belongs to the Offensive Security stage (beginner level), which takes about 5 hours. Think like an attacker.
Other units in this stage
Back to the full Cyber Security roadmap