This release lets you track security issues in GitHub, shows issue evidence as timestamped cards, and fixes a number of bugs.
Track security issues in GitHub
You can now raise and track Burp Suite DAST issues as GitHub issues. Connect to GitHub.com, GitHub Enterprise Server, or GitHub Enterprise Cloud with data residency, using a fine-grained personal access token.
When you raise an issue, choose an owner and a repository. You can set labels, assignees, milestones, issue types and projects, and Burp Suite DAST adds the issue's severity and confidence as labels. If you pick a public repository, you see a warning that anyone can read its issues.
Other improvements
We made the following improvements:
- Evidence as timestamped cards. An issue's Evidence tab now shows one card for each finding, newest first, with the date and time it was found. The tab label shows how many cards there are.
- AI-enhanced scanning. In scan settings, Burp AI and automation is now called AI-enhanced scanning. On an issue's Advisory tab, the Burp AI section is now headed AI enhanced scanning and appears below Vulnerability classifications.
Bug fixes
We fixed the following bugs:
- On MySQL and MariaDB, Burp Suite DAST now stores retest data larger than 64 KB. Previously, scans on Kubernetes could get stuck at "Scan not progressing", and on standard agents Retest was not offered for some issues.
- Importing an OpenAPI definition no longer fails when an XML request body schema is a primitive type with no XML name.