our f5 waf attach signatures is treating email addresses as risk and blocking the traffic. email address for people with surname 'parent' is not allowed. do we have a solution on how to allow this traffic without compromising attack signatures
We would need more info, and possibly the request payload triggering the event. But my feeling is that you should be able do diasable that specific signature on the specific parameter where the email address is used. That way, you do not completely disable the signature for the whole policy.
But if you provide the detailed payload causing the issue, I will be able to be more specific.