Penetration testing is the technique best matched to verifying that input data is properly validated and sanitized, because testers deliberately attempt to exploit weaknesses such as SQL injection, cross-site scripting, and command injection that stem directly from missing or weak input validation and sanitization routines. The other pairings mismatch technique and requirement: fuzz testing is aimed at robustness and error handling under malformed input, not at measuring the performance of cryptographic algorithms; threat modeling is a design-time risk-identification activity, not a means of testing conformance to an organizational security policy; and static vulnerability analysis examines source code for known flaw patterns, which is a weaker fit for verifying working authentication and authorization mechanisms than dynamic/functional security testing.
Community Discussion