Comparer des méthodes

	Tests statiques de sécurité des applications	Exécution symbolique
Domaine	Cryptographie	Cryptographie
Famille	Machine learning	Machine learning
Année d'origine	2000s	1976
Auteur d'origine	Various researchers	James C. King
Type	source code vulnerability detection	formal verification technique
Source fondatrice	Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. ISBN: 978-0321424778	King, J. C. (1976). Symbolic execution and program testing. Communications of the ACM, 19(7), 385-394.
Alias	SAST, white-box testing, source code analysis	symbolic execution, symbolic analysis, concolic execution
Apparentées	3	3
Résumé	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.	Symbolic execution is a program analysis technique that executes programs using symbolic (non-concrete) values instead of actual inputs, tracking how symbolic values flow through the program. Introduced by James C. King in 1976, symbolic execution builds mathematical constraints on program variables and can determine which inputs cause specific program behaviors, enabling automatic test generation and vulnerability detection. Modern symbolic execution tools like KLEE, S2E, and Z3 have become powerful instruments for finding subtle bugs and security vulnerabilities.