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.

lxxx<strong>Improving</strong> <strong>Web</strong> <strong>Application</strong> <strong>Security</strong>: <strong>Threats</strong> <strong>and</strong> CountermeasuresAn outline of the threat modeling process covered in the guide is shown in Figure 4.Threat Modeling Process1. Identify Assets2. Create an Architecture Overview3. Decompose the <strong>Application</strong>4. Identify the <strong>Threats</strong>5. Document the <strong>Threats</strong>6. Rate the <strong>Threats</strong>Figure 4The Threat Modeling ProcessThe steps shown in Figure 4 are described below:1. Identify assets.Identify the assets of value that your systems must protect.2. Create an architecture overview.Use simple diagrams <strong>and</strong> tables to document the architecture of your application,including subsystems, trust boundaries, <strong>and</strong> data flow.3. Decompose the application.Decompose the architecture of your application, including the underlying network<strong>and</strong> host infrastructure design, to create a security profile for the application. Theaim of the security profile is to uncover vulnerabilities in the design,implementation, or deployment configuration of your application.4. Identify the threats.Keeping an attacker’s goals in mind, <strong>and</strong> with knowledge of your application’sarchitecture <strong>and</strong> potential vulnerabilities, you identify the threats that couldimpact the application.5. Document the threats.Document each threat using a common threat template that defines a core set ofattributes that you should capture for each threat.

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

Saved successfully!

Ooh no, something went wrong!