Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
IAST is a testing method that watches for holes from inside while the application runs. It stands for Interactive Application Security Testing. While the application runs, it looks at its inner state and reports behavior that leads to a hole.
How does IAST work?
Picture fitting small sensors to a factory production line so that faults are detected while it runs. You do not only watch from outside, you can see the machine's inner movement, so the place of a fault is easier to find.
According to OWASP's DevSecOps guideline, IAST examines the application while it runs. What drives it can be automated tests, human operation, or any activity that uses the functions. The part that does the examining is a sensor (a library) built into the application's code, which watches its behavior and reports when it detects a hole.
The guideline explains that this sensor can see the whole code, the flow of data and processing, system configuration, screen components, and information on connections to the back end. Where SAST reads code without running it and DAST examines from outside, IAST differs in examining from inside. Assessments of running sites are on the web application assessment page.
Why does IAST matter?
It can return the results of running the app to developers at once, in the middle of development and testing. The advantage the guideline names is getting results in real time in settings such as development environments, continuous integration, quality checks, and production.
OWASP's guideline explains that SAST has many false alarms because it does not look at other measures or at runtime behavior, whereas IAST examines while running and is not tied to source code alone. It is also said to give results in less time than DAST.
On the other hand, the sensor is a library built into the application. So before introducing it, you need to check whether the language and environment can take it and whether its effect on operation is acceptable. Where it can be used is mainly a system you develop yourself.
To discuss which testing methods fit your system, contact us.
Related terms
- SAST: a method that reads a program without running it to find holes.
- DAST: a method that mounts mock attacks on a running site to find holes.
- Vulnerability: a weakness in a program or setting that can become an entry for attack.
- Dynamic testing: an assessment that actually operates a running site to find holes.
Next step
The kinds of assessment for a running site are on the web application assessment page. The free URL check shows only what is visible from outside. To choose a testing method, contact us.
Frequently asked questions
Does a small site need IAST?
For many small sites it is not a must. IAST is used by building a dedicated part into the application, so it suits a system you develop yourself. A site on a ready-made CMS should put updates and outside assessment first.
Can IAST replace SAST or DAST?
No. What it can check depends on the environments it can be built into and on the operations you run. Use it together with SAST and DAST to suit your purpose.
Frequently asked questions
Does a small site need IAST?
For many small sites it is not a must. IAST is used by building a dedicated part into the application, so it suits a system you develop yourself. A site on a ready-made CMS should put updates and outside assessment first.
Can IAST replace SAST or DAST?
No. What it can check depends on the environments it can be built into and on the operations you run. Use it together with SAST and DAST to suit your purpose.