static application security testing
Finding security problems by reading a program's source code without running it.
In more detail
SAST is cheap enough to run on every change and sees paths a test environment cannot exercise, but its rules describe risky patterns, not proven exploits. Good scanners work on the syntax tree, report a stable rule, a file and line and a reason, and gate only on new high-confidence findings.
Related terms
- 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.
- Bandit — An open-source static analysis tool from PyCQA that scans Python code for common security problems.
- security gate — An automated check in a pipeline that stops a change going further when it fails, usually by exiting with a non-zero code.
Taught in
- Adding GitLab's Security Scanners To A Pipeline — GitLab Certified CI/CD Associate Exam Prep
- Reading Security Results: The Merge Request And The Vulnerability Report — GitLab Certified CI/CD Associate Exam Prep
- Pinned For Stability: Images, Registries And Code — Kubernetes and Cloud Native Security Associate (KCSA) Exam Prep
- Static Application Security Testing — Application Security & Threat Modeling for Engineers
- How To Stop Drowning In Findings — Application Security & Threat Modeling for Engineers