Cyber Risks · PortSwigger Research

Using recorded logins - Port Swigger

Summary: PortSwigger's Burp Scanner uses recorded login sequences - sets of instructions for logging in to a web app - so it can audit content only authenticated users can see, including apps with complex mechanisms such as Single Sign-On. The documentation recommends configuring a status checker that looks for confirmation text, XPath expressions, or CSS selectors to verify the scanner is logged in on each replay, and notes that AI-recorded logins are available for Cloud instances of Burp Suite DAST but cannot record sequences for sites using multi-factor authentication.

Why it matters: The scanner's authenticated coverage depends on a status check that confirms login on every replay, and recorded login images are only stored for 14 days - so a stale or failing login sequence can quietly narrow what your scans actually reach.

Read the original at PortSwigger Research ↗

Topics
Identity & Access Management
Related