11.07.2015 Views

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

630 Part V: Assessing Your <strong>Security</strong>ASP.NET Pages <strong>and</strong> ControlsUse the review questions in this section to review your ASP.NET pages <strong>and</strong> controls.For more information about the issues raised in this section, see Chapter 10,“Building Secure ASP.NET Pages <strong>and</strong> Controls.”● Do you disable detailed error messages?● Do you disable tracing?● Do you validate form field input?● Are you vulnerable to XSS attacks?● Do you validate query string <strong>and</strong> cookie input?● Do you rely on HTTP headers for security?● Do you secure view state?● Do you prevent XSS?● Are your global.asax event h<strong>and</strong>lers secure?● Do you provide adequate authorization?Do You Disable Detailed Error Messages?If you let an exception propagate beyond the application boundary, ASP.NET canreturn detailed information to the caller. This includes full stack traces <strong>and</strong> otherinformation that is useful to an attacker. Check the element <strong>and</strong>ensure that the mode attribute is set to “On” or “RemoteOnly”.Do You Disable Tracing?Trace information is also extremely useful to attackers. Check the element toensure that tracing is disabled.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!