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.
Evidence-backed security findings
Why a finding without its request and response is not a finding.
Confirmed finding versus observation
The vocabulary the reports use.
DAST
Dynamic testing of a running application.
OWASP Top 10
The 2025 edition and what changed.
Do it: scan, gate, report
The guide, the pipeline article and the reporting duty.
Security scanner and evidence bundles
Target ownership, scan scopes and what a bundle contains.
Security in CI/CD, shift left
What to run on every change and what to leave for a scheduled scan.
CRA vulnerability reporting
The 24-hour clock and the evidence QA must produce.
Tenant isolation testing
The cross-tenant read a scanner does not look for.
Compare
With the incumbent’s strengths first.
Dokimore vs ZAP (formerly OWASP ZAP)
Where ZAP is the right choice and where evidence bundles differ.
DAST and security testing
What the scanner does, with its limits.
For security teams
The reviewer’s questions, answered honestly.
Prove it: tools
Two browser-only tools for the artefacts security reviews start from.
JWT decoder
alg none, no exp, no aud, a key URL in the header: the warnings, by eye.
HTTP header reference
Every header, with the ones that carry a security meaning marked.
robots.txt tester
Not access control, and this page says why.
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.
| Country | Security or testing check asked for |
|---|---|
| United States | FTC Safeguards Rule, for the financial institutions it covers: penetration testing annually, vulnerability assessments every six months |
| United Kingdom | Cyber Essentials on higher-risk central government contracts (PPN 014) |
| India | CERT-In: audits by empanelled auditors, incidents reported within 6 hours |
| Australia | Essential Eight to Maturity Level Two for non-corporate Commonwealth entities; ISM-0402 testing before release |
| Ireland | NIS2 was not yet law in Ireland when checked; Article 21 will ask for effectiveness and vulnerability handling |
| Germany | NIS2 through the BSI Act: section 30 risk-management measures since 6 December 2025 |
| France | NIS2 was not yet law in France when checked |
| Netherlands | NIS2 through the Cyberbeveiligingswet: an article 21 duty of care since 15 August 2026 |
| United Arab Emirates | Dubai’s Information Security Regulation and the federal Information Assurance Regulation (T7.7) |
| Japan | Vulnerability assessment services registered under the ministry’s Information Security Service Standards |
| Indonesia | OJK: vulnerability assessment and penetration test at a bank-set frequency, scenario-based test yearly |
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.
Related topics
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.