Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is DAST?

Dynamic Application Security Testing probes a running application from the outside, sending crafted requests and judging the responses, with no access to the source code.

Illustration for the cybersecurity term DAST
Home / Blog / Cybersecurity Terms / What Is DAST?
17 November 2026

What Is DAST?

What Is DAST?

Dynamic Application Security Testing (DAST) examines an application while it is running. The tool behaves like an attacker with no inside knowledge: it crawls the application, sends deliberately malformed or hostile requests, and decides from the responses whether a weakness is present. Nothing is known about the source code, the framework, or the server configuration except what the application reveals.

What a Scan Actually Does

A scan has two phases. During discovery the tool maps the attack surface by following links, submitting forms, and, for APIs, importing an OpenAPI or Postman definition. During the attack phase it replays each parameter with payloads chosen per check: quotation marks and timing payloads for injection, script fragments for cross-site scripting, traversal sequences for file access, and out-of-band callbacks for blind issues where no evidence appears in the response.

That last technique matters more than it sounds. A payload that triggers a DNS lookup to a collaborator domain is often the only way to detect blind server-side request forgery or out-of-band injection, and tools without that capability simply report nothing.

Strengths and Blind Spots

DAST tests what is deployed, including the web server, reverse proxy, framework defaults, and third-party components, so it catches the gap between how an application was written and how it ended up configured. Findings are concrete: a request, a response, and a reproduction step that a developer can replay.

The blind spots are equally predictable:

Where It Sits Among the Other Techniques

TechniqueNeedsFinds
SASTSource codeUnsafe patterns, tainted data flows
DASTA running instanceExploitable behaviour and configuration
IASTAgent plus test trafficConfirmed issues with a stack trace
SCADependency manifestsKnown vulnerable libraries

They overlap less than vendors suggest. A hardcoded credential is a static finding; a missing security header is a dynamic one; a vulnerable transitive dependency is neither until it is reachable.

Running It in a Pipeline

Teams that get value from DAST tend to split it in two. A short baseline scan, often OWASP ZAP in its automation mode, runs on every deployment to a test environment and fails the build only on new high-severity findings. A full authenticated scan runs nightly or weekly, where a two-hour run time is acceptable. Authentication is the part that breaks most often: script the login, provide a session token, and add a check that the scanner is still logged in, or the whole run will quietly cover only the public pages.

Commercial options include Burp Suite Enterprise Edition, Invicti, and Qualys WAS; open-source teams usually combine ZAP with Nuclei templates for known vulnerable components.

Expectations in the UK

The NCSC’s secure development and deployment guidance asks for continuous security testing integrated into the development process rather than a single pre-release gate. For card environments, PCI DSS v4.0 requirement 6.4.1 expects public-facing web applications to be reviewed at least annually and after significant change, or protected by an automated solution; requirement 11.3.1 covers internal and external vulnerability scanning on a quarterly cycle. Automated scanning satisfies the cadence, but neither standard treats it as equivalent to manual testing, which is why a penetration test remains the control that finds the issues a scanner structurally cannot.

FAQ – Frequently Asked Questions

Can DAST Replace a Penetration Test?

No. A scanner applies a fixed library of checks to the paths it can reach, which makes it excellent for regression coverage between tests. It cannot chain two medium findings into an account takeover, reason about business rules, or recognise that one customer should not see another customer’s order. Most assessment standards treat automated scanning and manual testing as separate requirements for that reason.

Should We Scan Production?

Only with care. Active scanning submits forms, creates records, and can trigger outbound emails or payment attempts. Run full active scans against a staging environment that mirrors production configuration, and restrict production to passive checks or a tightly scoped, out-of-hours run agreed with the service owner and monitored throughout.

Why Does Our Scanner Report Different Results Each Run?

Usually because coverage varies rather than the application changing. Session expiry, rate limiting, changed test data, randomised URLs, and crawl time limits all alter which pages were reached. Compare the number of URLs tested between runs before comparing findings, and pin the scan to a defined URL list or API specification when consistency matters.

Does DAST Work Against APIs and Single-Page Applications?

Yes, but not by crawling. For APIs, import an OpenAPI, GraphQL, or Postman definition so the tool knows the endpoints, parameters, and schemas. For single-page applications, use a scanner with a browser-based crawler and give it a recorded login sequence. Without either, the tool sees one HTML page and reports almost nothing.

Related Terms

You May Be Interested In These

What Is a Bootkit?

Cybersecurity Terms

17 November 2026

What Is a Bootkit?

Read More
What Is Steganography Detection?

Cybersecurity Terms

17 November 2026

What Is Steganography Detection?

Read More
What Is Lateral Movement?

Cybersecurity Terms

17 November 2026

What Is Lateral Movement?

Read More