Running websites / scan observation
Web Vulnerability
Scanning
Explore PortSwigger
Observe the run

Observe whether a scan keeps its intended session

A scan configured with credentials can still lose access. Session observation checks what identity was available during relevant parts of the run, without treating one successful login as proof of continuing coverage.

Choose an approved identity indicator

Identify a harmless application state or response that distinguishes the intended signed-in role from an anonymous session. Agree it with the application owner. Keep credentials and reusable tokens out of the shared observation record.

For an illustrative customer portal, the presence of a permitted account-specific view might support one access observation. The text of a generic login page returned with HTTP 200 would not. The interpretation must follow actual application behavior rather than status code alone.

Observe at meaningful transitions

Record access near the start, after authentication-relevant changes and when the scanner reports failures or unexpected navigation. Use the product’s supported verification mechanisms where available. Do not claim that a periodic indicator proves every request used the same identity.

If the session becomes unavailable, note when the evidence last supported the intended access and which later areas are uncertain. Preserve the tool’s own warnings with that timeline.

Distinguish permission denial from lost identity

A signed-in user can correctly be denied an operation outside its role. That denial is different from being sent to login because the session expired. The surface map supplies the expected actor and behavior needed to interpret the difference.

When the rule is ambiguous, ask the owner to resolve it. Do not invent an authorization policy from whichever response appeared during the scan.

Carry the limit into the result

An authentication failure may leave some valid findings and some unexamined surface. Summarize both. Repeating the relevant work after access is restored is a different observation and should receive its own run reference.

Use the observation sheet and result review guide to keep the session timeline attached to the conclusion.

Continue reading

Cite this entry

Web Vulnerability Scanning. “Observe whether a scan keeps its intended session.” Reviewed 2026-11-16.
https://webvulnerabilityscanning.com/session-observation/