Skip to main content
Free plan, no cardStart free
Topic · updated 2026-11-05

Web application security testing: DAST, evidence, CI

Web application security testing probes a running application the way an attacker would, through its pages and APIs, and reports what it found. The difference between a useful scanner and a noisy one is evidence: a finding that carries the request, the response and the differential that proves it is a finding; one without them is a suspicion that costs an engineer an afternoon.

The pages below start with that distinction, then cover the scanner and its evidence bundles, running security checks in the pipeline, the reporting duties the EU Cyber Resilience Act added in 2026, and an honest comparison with ZAP. The security-teams solution page is written for the reviewer who has to sign off.

What people search for

The literal queries this hub is written to answer; each leads to one of the pages below.

  • web application security testing
  • dast tool
  • website vulnerability scanner
  • owasp zap alternatives
  • security testing in ci/cd
  • owasp top 10 testing
  • security scanner false positives

Learn: findings, evidence and the standards

What a confirmed finding is, and the lists scanners are measured against.

Do it: scan, gate, report

The guide, the pipeline article and the reporting duty.

Compare

With the incumbent’s strengths first.

Prove it: tools

Two browser-only tools for the artefacts security reviews start from.

Security testing by country: the check buyers are asked for

What a regulator or a buyer asks for is not the same everywhere, and in several countries the answer is an accredited or empanelled provider rather than a tool. Each row is taken from that country’s page, which says what the scans cover and what they do not.

Security testing by country: the check buyers are asked for
CountrySecurity or testing check asked for
United StatesFTC Safeguards Rule, for the financial institutions it covers: penetration testing annually, vulnerability assessments every six months
United KingdomCyber Essentials on higher-risk central government contracts (PPN 014)
IndiaCERT-In: audits by empanelled auditors, incidents reported within 6 hours
AustraliaEssential Eight to Maturity Level Two for non-corporate Commonwealth entities; ISM-0402 testing before release
IrelandNIS2 was not yet law in Ireland when checked; Article 21 will ask for effectiveness and vulnerability handling
GermanyNIS2 through the BSI Act: section 30 risk-management measures since 6 December 2025
FranceNIS2 was not yet law in France when checked
NetherlandsNIS2 through the Cyberbeveiligingswet: an article 21 duty of care since 15 August 2026
United Arab EmiratesDubai’s Information Security Regulation and the federal Information Assurance Regulation (T7.7)
JapanVulnerability assessment services registered under the ministry’s Information Security Service Standards
IndonesiaOJK: vulnerability assessment and penetration test at a bank-set frequency, scenario-based test yearly

All countries compared, with the dates to plan around.

Questions people ask

What is the difference between DAST and a vulnerability scanner?

DAST (dynamic application security testing) is the category: tests run against a running application through its interface. A vulnerability scanner is a DAST tool, and the words are used interchangeably. What separates tools is coverage of authenticated and API surfaces, the false-positive rate, and whether each finding carries evidence.

How do I reduce false positives from a security scanner?

Require evidence per finding: the request that was sent, the response that came back and the control request that differed. A scanner that reports a differential rather than a pattern match produces findings a developer can reproduce; the rest are observations to triage. Dokimore separates the two in its reports, and the article on evidence-backed findings explains the method.

Can I run security tests in my CI pipeline?

Exported tests run in any CI; the scanner itself is run from the platform on a target you have authorised, and the results are read in the app or exported. There is no pipeline trigger that starts a scan from your CI yet; the integration pages say per provider what is wired today.

Try it on your own application

The Free plan asks for no card and runs for 14 days after the trial: record a flow, replay it, and read the evidence each step produced.

Try it against your own app.

Record one flow and get four kinds of evidence back. Judge the results yourself.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India