Dynamic testing meaning, in plain words

Dynamic testing finds holes by operating a running site. How it works, what it can and cannot show, why consent comes first, and the free URL check.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Dynamic testing is a way of finding holes by actually operating a site. OWASP calls this kind of tool DAST and explains that it usually examines a web application from outside. Because the site is really running, what is examined is the running state, including appearance and settings.

How does dynamic testing work?

Compare it with inspecting a finished building. The plans may be perfect, but once the building stands, a door may not close fully or a window lock may not engage. In dynamic testing, the inspector turns each doorknob and tries each window lock one at a time, in the same way as checking each entrance to the site.

In practice, the work moves through the screens and input fields, sends unexpected input, and watches how the site reacts. According to OWASP's list, this kind of tool looks for web application vulnerabilities and insecure server settings, among other things. Some methods use tools such as ZAP, and checks by a person can be added.

It is good at problems that appear only in combination and at faulty settings. It does not need the code to be read, and it examines the site as it looks from outside.

It is hard, though, to see where in the code a problem lies. OWASP notes that each tool has strengths and weaknesses. The scope of an assessment that really operates the site is in web application assessment.

Why does dynamic testing matter?

Because holes can remain in the running site even when the plans and code are right. How WordPress plugins combine, and how the server is configured, cannot be learned by reading code alone. Trying it live confirms the same picture an attacker sees.

What matters is doing it with the owner's agreement. Trying it on someone else's site without permission may violate the Unauthorized Computer Access Law. We assess only after we receive a consent form in which the targets, period, and method are agreed.

Our Cyber Shield Scan runs dynamic testing together with static analysis, a check of dependencies, and a check of settings, headers, and TLS. AI judges whether a finding can be abused, and a person confirms it before we report. OWASP's Web Security Testing Guide is also a reference for the whole of an assessment.

What should you settle before a test?

  1. Which pages and screens are in scope.
  2. The period and the time window when production might be affected.
  3. The method, set out in the consent form.

To settle these with us, contact us.

Because the test uses the site as an outsider would, its results are easy to explain to non-engineers: each finding is something that could be reached from a screen. That also means it cannot promise that the code is free of problems that never show on a screen, which is why it is paired with static analysis.

Related terms

  • Static analysis: a way of finding holes by reading source code without running it
  • Vulnerability: a security hole in a program or its settings
  • WAF: a wall that stops malicious traffic at the entrance
  • Rate limiting: a limit on how often something can be accessed in a short time

Frequently asked questions

What is the difference between dynamic testing and static analysis?

The target differs. Static analysis reads source code, and dynamic testing operates a running site from outside. The former makes it easy to point to a place in the code, and the latter makes it easier to find problems that arise in the real screens and settings.

Can dynamic testing on a live site bring it down?

We run safe assessments that keep the number of requests per second low. A method that might affect production is carried out only in a time window agreed beforehand. The targets, period, and method are agreed in advance in a consent form.

Is the free URL check dynamic testing?

No. The free URL check only passively reads one page of the URL sent and basic public information, and it sends no login attempts or attack traffic. To examine screens behind login, you need an assessment based on a consent form.

Next step

Start with the free URL check, which shows only what is visible from outside. The scope of an assessment that operates the site is in web application assessment. To decide targets and time windows, contact us.

Frequently asked questions

What is the difference between dynamic testing and static analysis?

The target differs. Static analysis reads source code, and dynamic testing operates a running site from outside. The former makes it easy to point to a place in the code, and the latter makes it easier to find problems that arise in the real screens and settings.

Can dynamic testing on a live site bring it down?

We run safe assessments that keep the number of requests per second low. A method that might affect production is carried out only in a time window agreed beforehand. The targets, period, and method are agreed in advance in a consent form.

Is the free URL check dynamic testing?

No. The free URL check only passively reads one page of the URL sent and basic public information, and it sends no login attempts or attack traffic. To examine screens behind login, you need an assessment based on a consent form.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.