Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
SAST is a method that reads a program without running it to look for holes. It stands for Static Application Security Testing. OWASP explains that it is also called static code analysis or source code analysis.
How does SAST work?
Picture a proofreader reading a book manuscript for errors before it is printed. It happens before the book reaches readers, so the work to fix it is also smaller.
OWASP's DevSecOps guideline places SAST as a kind of code review and a white-box method, one that looks at the inside. It examines without running the program and looks for syntax violations, security flaws, programming errors, coding-standard violations, and undefined values. The same guideline says that combining it with component analysis (SCA) and with checks of infrastructure managed as code lets you check more widely.
OWASP's Source Code Analysis Tools page names as an advantage that this kind of tool can examine a wide range repeatedly. It can be built into nightly builds and continuous integration, and it shows the location of a problem by file name and line number. The overall idea is on the static analysis page, and assessment of a program's contents on the source code assessment page.
Why does SAST matter?
If you find a hole early in development, the work can be smaller than fixing it after release. For a system built by an outside party, if you can get the source code, it can be used to check what was delivered.
OWASP also names weaknesses. False alarms are many, and it is hard to confirm whether a reported problem is really a hole. Authentication, access control, and insecure cryptography are hard to check automatically, and configuration problems do not appear in code, so they are hard to find.
So SAST is not used alone. It is combined with a source code review in which a person reads, and with methods that examine the running site. Do not treat every finding with the same weight. Have the person in charge look and judge whether it can really be exploited.
To choose the checking methods that suit your system, contact us.
Related terms
- Static analysis: the idea of reading a program without running it to find holes.
- Source code review: a check in which people and tools read a program's contents to find holes.
- Vulnerability: a weakness in a program or setting that can become an entry for attack.
- DAST: a method that mounts mock attacks on a running site to find holes.
- IAST: a method that watches for holes from inside while the app runs.
Next step
The scope of an assessment that examines a program's contents is on the source code assessment page. The free URL check shows only what is visible from outside. To choose a testing method, contact us.
Frequently asked questions
When does SAST fit?
It fits while the program is being written, and for checks before release. OWASP explains that this kind of tool can be run repeatedly in nightly builds and continuous integration. For checking a finished site from outside, use another method.
If SAST reports nothing, is the program safe?
No. Problems in authentication and access control, and flaws in configuration, are said to be hard for this method to find. Judge together with other methods and a person's checks.
Frequently asked questions
When does SAST fit?
It fits while the program is being written, and for checks before release. OWASP explains that this kind of tool can be run repeatedly in nightly builds and continuous integration. For checking a finished site from outside, use another method.
If SAST reports nothing, is the program safe?
No. Problems in authentication and access control, and flaws in configuration, are said to be hard for this method to find. Judge together with other methods and a person's checks.