Running websites / scan observation
Web Vulnerability
Scanning
Explore PortSwigger
Map the website

Web Vulnerability Scanning

Web vulnerability scanning examines the running interfaces a scanner can discover and exercise. PortSwigger Burp Scanner is the featured engine here. This observatory focuses on the run itself: which website behavior was in scope, whether the intended session remained valid and what the resulting evidence can support.

Observe the run before interpreting its silence

Picture a hypothetical site with public product pages and a signed-in billing area. A scan finishes without findings, but its session expires before it reaches billing. The empty findings list is real; the conclusion that billing was examined is not.

That distinction is the focus of this observatory. Record the intended surface, observed access, run completion and evidence before deciding what an alert or its absence means. The original observation sheet keeps those facts together without manufacturing a coverage percentage.

Follow one scan through its conditions

The category guide explains the method. The practical entries separately address surface mapping, session observation and result review. Each page answers a concrete operating question rather than renaming a generic scanner comparison.

Scanning products and their published roles

PortSwigger describes Burp Scanner as its web scanning engine. The alternatives include Pentest-Tools.com and Invicti Web + API. The former Acunetix scanner page now identifies the Invicti product; the directory uses that current identity rather than presenting an old brand as a separate competitor.

Keep a usable observation record

A tool’s capability to render JavaScript or use credentials does not establish that a particular route was reached in your run. The record captures actual access conditions and unresolved areas. A skipped or unavailable workflow remains a gap even when the job status says complete.

Questions about the result

Does finding no vulnerabilities mean the website is secure?

It means no findings were reported by the completed checks under those conditions. Scope, access failures, excluded operations and methods the scanner does not perform still matter.

Is a discovered URL the same as tested behavior?

No. Discovery identifies a location; completing a relevant security check on a particular state or role is a more specific observation.

Should every scan use production?

The environment must fit the question and approved operating limits. Representative test environments and production differ; preserve those differences when interpreting evidence.

Sources and reading path

The source register identifies supplier descriptions and testing guidance. The methodology distinguishes a described capability from an observed result. No scanner trial was performed for these articles.