Managing agentic tests - Port Swigger
Summary: PortSwigger's Burp AT documentation describes how to manage agentic tests: users check progress under Agentic tests, review findings on the Issues or Discovered URLs tabs, and stop or delete tests, with a stopped test's environment shutting down only after 24 hours without activity if left alone. Burp AT issues are added to site, folder and global Issues lists but not to scan results or reports, and do not raise tickets in Jira or ServiceNow.
What's compelling: Burp AT findings never reach scan results, reports, or Jira and ServiceNow tickets, so anything its agents uncover lives only in the Issues lists unless someone goes looking. Each instance also caps how many agentic tests run at once, and a test left running holds its environment for 24 hours after its last activity.
Read the original at PortSwigger Research ↗
- Topics
- Vulnerabilities & Patching
- Related
- Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026