How to configure DAST full scans for complex web applications

What this post added

This post details how to optimize DAST full scan duration for complex web applications by reducing the number of tested pages (using DAST_AUTH_EXCLUDE_URLS), populating the app with relevant test data (e.g., using review apps), and identifying/excluding irrelevant rules (using DAST_EXCLUDE_RULES). It also discusses parallelizing DAST jobs to further reduce pipeline duration.