Choosing where tickets go - Port Swigger

Summary: PortSwigger's documentation describes how Burp Suite DAST actions control where tickets are created and what fields they carry, with connection-level defaults for Reporter, Impact and Urgency and per-action settings for Table and Assignment group. Severity maps to impact and urgency as High to 1, Medium to 2, and Low and Info to 3, and DAST cannot set mandatory ServiceNow columns of type date and time, journal, HTML, list or currency, which blocks saving an action for that table if no default exists.
Why it matters: Without the admin role, a field made mandatory by a ServiceNow data policy appears optional in DAST, and ServiceNow rejects the ticket when it is raised with that field empty - a failure that surfaces only at ticket creation unless a test ticket is raised from each action first.

Read the original at PortSwigger Research ↗

Topics: Vulnerabilities & Patching
Related: Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026
U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026
PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026