Static application security testing
SAST articles
Finding vulnerabilities in source code without running it: taint analysis, per-language engines and keeping the signal above the noise.
Static application security testing (SAST) reads source code to find injection, unsafe deserialisation and other flaws before the code ships. These articles explain taint analysis, how SAST differs from SCA and secrets scanning, and how to reduce false positives without hiding real bugs.
- SAST remediation: write tests that protect the fixTurn a SAST finding into a focused remediation test that checks the dangerous data flow, preserves valid behaviour and catches future regressions. · Sujan Singh
- SAST vs SCA vs secrets scanning: what each one catchesSAST vs SCA vs secrets scanning compared: what each inspects, what it misses, when it should run and who fixes its findings, with one shared example. · Sujan Singh
- Reducing SAST false positives without hiding real bugsReduce SAST review noise with better rules, reachability context and reason-coded triage, while keeping real weaknesses visible for reassessment. · Sujan Singh
- SAST taint analysis explained: sources, sinks, sanitisersLearn how SAST taint analysis traces untrusted input from source to sink, why it beats pattern matching on noise, and where its blind spots are. · Sujan Singh
See it on your stack
See connected security in action.
Explore the workflow with your engineering, security and compliance teams. No repository access is needed for the initial demonstration.