Bypass leaked credentials scan
Is it possible to bypass the leaked credentials scan entirely? Ever since this was added I'm seeing increased response times from my API and a ton of warnings in the WAF action logs. In one case it detected leaked credentials in a .mp3 file? I'd like to disable this scan completely if possible.
