After the great malware infestation of 2012, I hired a security specialist to analyze our vulnerabilities and make us safe. One of this things he did was to put a piece of software in front of our web server that rejects all sorts of special character strings that hackers use to attempt "SQL Injection Attacks".
That's a technique where the hacker puts a certain string of characters into text boxes, hoping that the database will respond to them as if they were valid commands, and yield control of the database and web site to the bad guy. Then they load malware, which they hope will spread to users.
So we have extremely sensitive filtering, and depending on where the special characters are in a post or poll, and what else is in the surrounding text boxes, the filter will trip and you see the "forbidden" page. That's all that shows to not give the hacker any clues as to what he did.
The filter has stopped millions of attempts (automated robots work on sites at the direction of hackers) to hack us, some of which could have been very successful and very disastrous. We use other pieces of software as well. We run a filter that blocks known spammer registrations and for fun I just checked the log and in the last 12 months it has blocked 398,000 bogus registration attempts, most from automated spambots.
Once I know about a certain issue, I ask Tyler to look at the text, and write an exception to the rule since we know that's something legitimate. Sometimes, loosening a rule will make us vulnerable, so we don't, and I try to handle the occurrences with the same advice Ed gave; Loose the special characters, especially in post titles.
Ain't that fascinating :tongue:
Tyler is looking at this specific issue now.