Post: @Anonymous Coward
@Anonymous Coward →
Posted Friday 27th June 2008 01:29 GMT
In Microsoft and HP tackle SQL-injection scourge
"Scanning for SQL injection / XSS attacks should be the WebServers responsibility. I have never wanted to pass sql / script via a querystring or form field."
The result will be an overzealous webserver blocking legitimate queries, or blacklist filtering that will inevitably miss a certain type of string and still allow exploitation. If you have developers who have even a basic understanding of security, webserver filtering causes far more trouble than it's worth. At the most basic level, any app framework that doesn't allow named or positional parameters in SQL strings is seriously defective.
Anyway, if a site allows SQL injection, it is already broken even to non-malicious users. Better hope that your name doesn't contain an any quotes (eg John O'Toole or John "JJ" O'Toole) or that you don't need to enter an ampersand (John & Mary).
Most read
Popular Whitepapers
- Out-of-box comparison between Dell, HP, and IBM blade servers
Receiving, unpacking and installing each system in the server rack - Enterprise communications and collaboration in a fast changing world
Transform the productivity and profitability of large enterprises - Windows Server 2008 R2 Hyper-V Live Migration
Adopt virtualization easily - The data governance maturity model
Establishing the people, policies and technology that manage enterprise data - Simplifying communications, serving citizens
A Vodafone One briefing for local government - Email as part of a business continuity strategy
The general approaches available to ensure email continuity from a high level