Dynamic Application Security Testing
Subject: Computer and Technology noun /daɪˈnæm.ɪk ˌæp.lɪˈkeɪ.ʃən sɪˈkjʊr.ə.ti ˈtɛs.tɪŋ/ 1 definition
- application-security
- web-security
- security-testing
- automated-testing
-
Definition (noun)
Entry #339 · UpdatedDynamic Application Security Testing (DAST) is a black-box application security methodology that evaluates a running software system from the outside to uncover exploitable vulnerabilities and runtime misconfigurations. Operating without access to source code or internal implementation details, a DAST engine discovers exposed interfaces—such as web forms, REST or GraphQL APIs, and authentication flows—and sends crafted attack payloads while inspecting HTTP responses, state changes, and timing anomalies. By testing live or staging deployments during execution, it exposes environment-dependent weaknesses including injection flaws, cross-site scripting (XSS), broken access controls, and insecure server or TLS configurations. Because it observes only external input-output behavior, DAST complements white-box Static Application Security Testing (SAST) by verifying runtime reachability on live endpoints while lacking visibility into unexercised code paths or exact offending source lines.
Common Forms
Unauthenticated DAST: Scans publicly exposed URLs, forms, and HTTP headers without credentials to uncover pre-authentication flaws, leaked administrative endpoints, and server misconfigurations.
Authenticated DAST: Replays login sequences, session cookies, or OAuth bearer tokens so the scanner can exercise protected workflows and detect broken access controls or privilege escalation paths.
API-Driven DAST: Imports OpenAPI, GraphQL, or gRPC specifications to construct valid structured requests and fuzz backend endpoints that traditional HTML link crawlers cannot discover.
Proxy-Based DAST: Intercepts live browser or mobile client traffic through a local HTTP proxy to passively audit responses and actively replay mutated payloads against recorded requests.
Example
After deploying a build to an isolated staging container, a CI workflow runs OWASP ZAP (
zap-api-scan.py) against an OpenAPI specification (/openapi.json) using a seeded test account'sAuthorization: BearerJWT. When the scanner sends' OR 1=1--toGET /api/v2/invoices?status=and probesGET /api/v2/invoices/1042owned by another tenant, it detects an HTTP500PostgreSQL stack trace and an unauthorized200 OKpayload, failing the pipeline gate before production release.