Security of ASP.NET web applications

Question

0.00/5 (No votes)

See more:

While providing security to web applications we are avoiding special characters inputs from GUI.
But any client want to allowed the special characters in some fields then how to handle special characters validations.

Posted 7-Apr-13 19:03pm

Milind Panchal

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rekhash · Answer 1 · 2013-04-09T17:50:00

Solution 2

http://msdn.microsoft.com/en-us/library/330a99hc(v=vs.71).aspx[^]
http://msdn.microsoft.com/en-IN/library/330a99hc(v=vs.100).aspx[^]
ASP.NET web application security review: Do's & Don'ts[^]

Posted 9-Apr-13 17:50pm

Rekhash

_Maxxx_ · Answer 2 · 2013-04-07T19:13:00

I'm assuming you are talking about preventing SQL injection by stopping users typing their user name as

max;delete from customer;

for example?

But then a customer of yours comes along and wants to enter a lit of items separated by semi-colons?

Essentially you just need to make sure you aren't vulnerable to injection attacks regardless of the text entered.

Don't build your SQL strings by concatenation, for example.

Use stored procedures rather than direct SQL (a matter of preference)

Use parameterised queries

Utilise a database user that does not have access to tables directly (i.e. only through SP and Views)