Method evidence record

Static Application Security Testing

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.

Sources recorded, not reviewed

Source record

Citations copied verbatim from the method’s source record. No claim-level verification is inferred from them.

Static Application Security Testing (SAST)

Taxonomic method record · ml-model / cryptography

Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. · ISBN 978-0321424778
Walz, C., Seifert, H. P., & Fischer, A. (2010). Static source code analysis tools. In Secure Software Development (SANS Institute), pp. 1-20. · URL

Open full method

Curated claims

Claims persisted in the evidence ledger, each with its own assessment.

No curated claims yet

This view does not invent a claim assessment when the ledger has none.

Related methods

Generated from the method graph and shown as machine-suggested relations — no evidence claim is inferred.

Taxonomic bucketDynamic Application Security Testingmachine-suggested · Relational suggestion, not evidence.Same method familySymbolic Executionmachine-suggested · Relational suggestion, not evidence.Same method familyTaint Analysismachine-suggested · Relational suggestion, not evidence.