Sammenlign metoder
Gjennomgå de valgte metodene side om side; rader som avviker, er uthevet.
| Symbolsk eksekvering× | Statisk testing av applikasjonssikkerhet× | |
|---|---|---|
| Fagfelt | Kryptografi | Kryptografi |
| Familie | Machine learning | Machine learning |
| Opprinnelsesår≠ | 1976 | 2000s |
| Opphavsperson≠ | James C. King | Various researchers |
| Type≠ | formal verification technique | source code vulnerability detection |
| Opprinnelig kilde≠ | King, J. C. (1976). Symbolic execution and program testing. Communications of the ACM, 19(7), 385-394. DOI ↗ | Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. ISBN: 978-0321424778 |
| Alias | symbolic execution, symbolic analysis, concolic execution | SAST, white-box testing, source code analysis |
| Relaterte | 3 | 3 |
| Sammendrag≠ | 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. | 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. |
| ScholarGateDatasett ↗ |
|
|