I am having a frequent issue of the SQL-INJ signatures matching and alarming on content that has no resemblance of a SQL injection attack.
Here is an example:
txtBio=
Julie0x20Brown:0x20Julie0x20‘
This flagged attack signature 200002175 - SQL-INJ create table.
Every day I get a couple thousand of these sort of false positives. If I disable on parameter then eventually I will have no paramaters being protected.
So that signature is fairly broad in its net cast (generic sql catch). I usually disable the generic one and leave all the more advanced mysql rules to provide protection.
I’ll need to look at the regex of the rule again, but if I recall it’s called in the rule that it may have a higher false positive rate.
Sorry for the brief response, in middle of a class.