手法を比較

	動的アプリケーションセキュリティテスト	ファジング	静的アプリケーションセキュリティテスト
分野	暗号学	暗号学	暗号学
系統	Machine learning	Machine learning	Machine learning
提唱年	2000s	1990	2000s
提唱者	Various researchers	Barton Miller	Various researchers
種類	runtime vulnerability detection	random input-based testing technique	source code vulnerability detection
原典	Kals, S., Kirda, E., Kruegel, C., & Jovanovic, N. (2006). Secubat: A web vulnerability scanner. In Proceedings of the 15th International Conference on World Wide Web (WWW 2006), pp. 247-256.	Miller, B. P., Fredriksen, L., & So, B. (1990). An empirical study of the reliability of UNIX utilities. Communications of the ACM, 33(12), 32-44.	Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. ISBN: 978-0321424778
別名	DAST, black-box testing, runtime security testing	fuzz testing, fuzzer, mutation testing	SAST, white-box testing, source code analysis
関連	3	3	3
概要	Dynamic Application Security Testing (DAST) is a security analysis technique that tests a running application by sending various inputs and observing responses to identify vulnerabilities and security flaws. Developed in the 2000s as a complement to static analysis, DAST exercises the application at runtime, finding vulnerabilities that only manifest during execution such as authentication bypass, insecure redirects, and logic flaws. DAST is commonly used for web application testing and is considered a black-box testing approach since the tester requires no knowledge of internal code structure.	Fuzzing is a software testing technique that inputs large numbers of random or semi-random test cases to a program to find bugs, crashes, and security vulnerabilities. Pioneered by Barton Miller in 1990, fuzzing has become a primary method for discovering zero-day vulnerabilities in complex software. Modern fuzzing tools like libFuzzer, AFL, and HoneyPot combine coverage-guided mutation with instrumentation to efficiently explore program paths and trigger vulnerabilities. Fuzzing has discovered thousands of critical vulnerabilities in major software including browsers, compilers, and cryptographic libraries.	Static Application Security Testing (SAST) is a security analysis technique that examines source code or compiled binaries without executing the program to identify vulnerabilities, code quality issues, and security flaws. Developed in the 2000s, SAST analyzes code structure, data flow, and control flow to detect potential bugs such as SQL injection, buffer overflows, and insecure cryptographic usage. SAST is widely integrated into development workflows as a shift-left security practice, enabling early detection of vulnerabilities before code reaches production.