방법 비교
선택한 방법을 나란히 검토하세요. 서로 다른 행은 강조 표시됩니다.
| 동적 애플리케이션 보안 테스팅× | 정적 애플리케이션 보안 테스팅× | |
|---|---|---|
| 분야 | 암호학 | 암호학 |
| 계열 | Machine learning | Machine learning |
| 기원 연도 | 2000s | 2000s |
| 창시자 | Various researchers | Various researchers |
| 유형≠ | runtime vulnerability detection | 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. DOI ↗ | Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. ISBN: 978-0321424778 |
| 별칭 | DAST, black-box testing, runtime security testing | SAST, white-box testing, source code analysis |
| 관련 | 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. | 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. |
| ScholarGate데이터셋 ↗ |
|
|