static application security testing
Analysing source code without running it to find insecure patterns, such as SQL built from user input.
In more detail
Good SAST tools parse the code into a syntax tree, so comments and harmless strings do not trigger findings. Pattern rules miss data that flows across functions, which taint analysis helps with.
Related terms
- Semgrep — An open-source static analysis tool whose rules look like the code they match, with metavariables and ellipses for the parts that vary.
- abstract syntax tree — A tree-shaped description of a program's structure, with nodes for pieces such as functions, calls and assignments, that tools build from the source text.
- taint analysis — Tracking untrusted data from where it enters (a source) to where it would be dangerous (a sink), unless it passes a sanitiser first.
- software composition analysis — Finding the open-source packages in your software and checking their exact versions against known vulnerability advisories.
Taught in
- Pipeline Security: The Build Role That Could Do Anything — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Scanning Code, Dependencies And Containers — Microsoft Azure DevOps Engineer Expert (AZ-400) Exam Prep
- Static Application Security Testing with Semgrep — Cloud Security & DevSecOps Engineering