Security Testing for Quality Assurance (QA)s
Security testing for QA means checking an application for common weaknesses before attackers find them. Testers use the OWASP Top 10 as a checklist, probing for injection, broken authentication and access control, and insecure configuration with a proxy such as ZAP or Burp, without needing to be a full penetration tester.
Stage: Non-functional Testing · Part of the Quality Assurance (QA) roadmap · Last reviewed 19 November 2026
What to learn in Security Testing
- List the main categories of the OWASP Top 10 with an example each
- Try a SQL injection payload on an input and read the response
- Check that one user cannot read another user's data by changing an id
- Inspect cookies, headers and HTTPS settings for weaknesses
- Run an automated ZAP baseline scan and triage the findings
- Report a security issue without exposing sensitive data
Security Testing interview questions
What is broken access control and how do you test it?
It is when users can act outside their permissions, for example viewing another account's order. Test by logging in as one user and changing ids in URLs or API calls, or calling admin endpoints with a normal user's token.
How does SQL injection happen?
It happens when user input is concatenated into a SQL string, so crafted input alters the query. Parameterised queries prevent it. A tester tries quote characters and payloads in inputs and watches for errors or unexpected data.
Where Security Testing fits in the Quality Assurance (QA) roadmap
Security Testing belongs to the Non-functional Testing stage (beginner level), which takes about 3 hours. Beyond happy paths.
Other units in this stage
Back to the full Quality Assurance (QA) roadmap