PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Watch the on-demand webinar: Shift left without the strain

portswigger.net | blog | #webinar | #false-positives | #dast | #burp-suite-dast | #cicd | #shift-left
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Struggling to shift left? Learn how Burp Suite DAST overcomes slow scans, false positives and pipeline friction in our on-demand webinar
Published
Collected

Related coverage

blog · portswigger.net
DAST without disruption: Burp Suite DAST winter update 2025
The Burp Suite DAST winter update adds scan freeze windows, better large-portfolio management, CI-driven scan folders, and improved authenticated scanning with recorded login editing.
blog · portswigger.net
Watch the webinar: Scale secure coverage without scaling headcount
A webinar recap showing how Burp Suite DAST scales trusted scanning across hundreds of apps and APIs, with enterprise-grade accuracy, flexible deployment and CI/CD integrations.
blog · hackerone.com
Shift Left is Dead: A Post Mortem
HackerOne's CTO argues shift left failed: tools disrupt workflows, flood developers with false positives, and lack actionable alerts; he calls for a developer-first security approach instead.
blog · aikido.dev
DAST Tools: Features, Capabilities & How to Evaluate Them
DAST scans running applications from the outside in, catching runtime flaws like injection and broken access control that static tools miss. Endpoint discovery and CI/CD integration are must-haves.
blog · portswigger.net
The year so far: How Burp Suite DAST is leveling up enterprise security in 2025
A recap of Burp Suite DAST's first-half 2025 updates: bulk scan scheduling, site tagging, dynamic authentication token refresh, and Postman Collection support for API scanning.
blog · portswigger.net
HTTP/1.1 Must Die: What This Means for AppSec Leadership
What AppSec leaders should take from HTTP/1.1 Must Die: desync attacks remain a systemic protocol-level threat, and auditing with Burp Suite DAST plus moving to upstream HTTP/2 is the fix.
Back