Porównaj metody

	Dynamic Application Security Testing	Statyczne testowanie bezpieczeństwa aplikacji
Dziedzina	Kryptografia	Kryptografia
Rodzina	Machine learning	Machine learning
Rok powstania	2000s	2000s
Twórca	Various researchers	Various researchers
Typ	runtime vulnerability detection	source code vulnerability detection
Źródło pierwotne	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.	Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. ISBN: 978-0321424778
Inne nazwy	DAST, black-box testing, runtime security testing	SAST, white-box testing, source code analysis
Pokrewne	3	3
Podsumowanie	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.	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.