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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

100 Part II:Designing Secure <strong>Web</strong> <strong>Application</strong>sHow to Use This ChapterThis chapter gives you the questions to ask when performing a thorough review ofyour architecture design. The following are recommendations on how to use thischapter:● Integrate a security review into your architecture design process. Start early on,<strong>and</strong> as your design changes, review those changes with the steps given in thischapter.● Evolve your security review. This chapter provides questions that you can ask toimprove the security of your design. To complete the review process, you mightalso need to add specific questions that are unique to your application.● Know the threats you are reviewing against. Chapter 2, “<strong>Threats</strong> <strong>and</strong>Countermeasures,” lists the threats that affect the various components <strong>and</strong> layersthat make up your application. Knowing these threats is essential to improving theresults of your review process.Architecture <strong>and</strong> Design Review ProcessThe architecture <strong>and</strong> design review process analyzes the architecture <strong>and</strong> design froma security perspective. If you have just completed the design, the designdocumentation can help you with this process. Regardless of how comprehensiveyour design documentation is, you must be able to decompose your application <strong>and</strong>be able to identify key items, including trust boundaries, data flow, entry points, <strong>and</strong>privileged code. You must also know the physical deployment configuration of yourapplication. Pay attention to the design approaches you have adopted for those areasthat most commonly exhibit vulnerabilities. This guide refers to these as applicationvulnerability categories.Consider the following aspects when you review the architecture <strong>and</strong> design of yourapplication:● Deployment <strong>and</strong> infrastructure. You review the design of your application inrelation to the target deployment environment <strong>and</strong> the associated security policies.You also consider the restrictions imposed by the underlying infrastructure-layersecurity.● <strong>Application</strong> architecture <strong>and</strong> design. You review the approach to critical areas inyour application, including authentication, authorization, input validation,exception management, <strong>and</strong> other areas. You can use the application vulnerabilitycategories as a roadmap <strong>and</strong> to ensure that you do not miss any key areas duringthe review.● Tier-by-tier analysis. You walk through the logical tiers of your application <strong>and</strong>examine the security of ASP.NET <strong>Web</strong> pages <strong>and</strong> controls, <strong>Web</strong> services, servicedcomponents, Microsoft .NET Remoting, data access code, <strong>and</strong> others.

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

Saved successfully!

Ooh no, something went wrong!