title: Why I should Sanitizing manually input when .NET "do it" for me?
body: <p><em>One of the most prevalent attacks today is cross-site scripting (XSS), which is more of an attack on your application's users than on the application itself, but it exploits server-side application vulnerabilities all the same. The results can be devastating and can lead to information disclosure, identity spoofing, and elevation of privilege</em></p>
  
  <p>Reading <a href="http://msdn.microsoft.com/en-us/library/aa302426.aspx" rel="nofollow">this</a> document I see many suggestions about Sanitizing/Validation input on server side before manage them. </p>
  
  <p>Well, for what I know, using Stored Procedures (for the DB side) and .NET (to manage e get the responses) I'm quite sure.</p>
  
  <p>Can you show to me a scenario where both Stored Procedures and .NET could fail (without Sanitizing/Validation) and where I can be "unsafe"?</p>
  
  <p>As I say, I mean "security", not persistence/accuracy of data! There I agree on Sanitizing input...</p>