Redact Sensitive Information By Default in DAST debug output
Problem
A DAST scan can output logs and the authentication report as debug artifacts. These artifacts help the engineering team to debug issues that customers are facing with their DAST Scans. However, in many cases, customers are understandably reluctant to share such output at the risk of revealing confidential information.
Proposal
Allow better ways to redact sensitive information in DAST debug output. This will help us enable debug artifacts like the authentication report to be captured by default (#422115), rather than manually. Better debug artifacts will help significantly in debugging problematic scans.
Related Slack Discussion: internal link
Edited by Arpit Gogia