Interactive Application Security Testing
What is Interactive Application Security Testing?
A security testing approach that combines elements of static and dynamic analysis to identify vulnerabilities while the application is running.
Terms that appear alongside interactive application security testing
Each of these is named in at least one of the same controls as interactive application security testing. The number is how many controls name both.
- security testing 4 shared controls
- application security testing 4 shared controls
- application security 4 shared controls
- owasp 3 shared controls
- code signing 2 shared controls
Frameworks that govern interactive application security testing
What the standards actually require on interactive application security testing
Requirements naming interactive application security testing across 5 standards, quoted from the control text.
Require the developer of the system, system component, or system service to employ interactive application security testing tools to identify flaws and document the results.
NIST800-SA-11(9) · SA-11(9) Developer Testing and Evaluation | Interactive Application Security Testing →Integrate routine static, dynamic, and interactive application security testing throughout the development and deployment lifecycle.
ZTMM-APP-TEST · Applications Pillar: Application Security Testing →Per OWASP ASVS V10: protect against malicious code. Requirements include (a) integrate static + dynamic + interactive application security testing in CI/CD pipeline + (b) maintain dependency inventory + SBOM + scan for vulnerabilities + license issues + malici...
OWASPASVS-10 · Malicious Code Verification (V10) →Per OWASP DSOMM Test and Verification dimension: implement comprehensive security testing. Requirements include (a) integrate Static Application Security Testing (SAST) in CI/CD with developer feedback + tuning + (b) operate Dynamic Application Security Testin...
DSOMM-4 · Test and Verification - SAST, DAST, IAST, SCA, Penetration Testing →Per OWASP MASVS v2 MASVS-CODE: code quality + build settings + secure updates. Requirements include (a) implement secure coding practices including input validation + output encoding + memory safety + (b) use memory-safe languages + APIs where possible + (c) i...
OWASPMASVS-6 · MASVS-CODE: Code Quality, Build Settings, and Updates →Questions people ask about interactive application security testing
What is Interactive Application Security Testing?
Why is Interactive Application Security Testing important for compliance?
Which compliance frameworks address Interactive Application Security Testing?
Where can I learn more about Interactive Application Security Testing?
See how Interactive Application Security Testing applies across compliance frameworks
Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.