Insights into Web Application Security Risk - Secure Java: For Web Application Development - page 104

table 5.1 threat Proiling table

Threat
Access

Threat
Description

Threat
Motive

Threat
Outcome

Asset Name Threat Actor

Customer
information

Malicious
application
user (hacker)

Over the
Internet—
Human actor
using
network
access

Attacker can
use the user
accounts of
other
legitimate
users of the
application

Deliberate Loss of

conidentiality
of customer
information

stakeholders in the application development process and acts as a much-needed input to the next
process, namely threat modeling.

5.4.4.2 Threat Modeling

hreat modeling is a commonly used term in the Web application security sphere. hreat model-
ing refers to a scenario formulated in which the threat exploiting the vulnerability is explored in
great detail to bring a perspective of realism into the threat analysis exercise. With respect to Web
applications, threat modeling is a highly technical exercise, where it is recommended that applica-
tion architects along with security specialists with some experience in Web application penetration
testing are involved to ensure that all possible threat scenarios are considered to ensure that efec-
tiveness of the threat modeling exercise permeates into an efective and comprehensive protection
strategy for the Web application.
Let us explore the threat-modeling process for the example used for the threat-proiling exer-
cise (see Table 5.2).

5.5 Risk Mitigation Strategy—Formulation of Detailed
Security Requirements for the Web Application
Mitigation of identiied risks is the primary goal of a risk management process for a Web appli-
cation. Controls need to be designed, developed, and implemented based on the outcome of the
entire risk assessment phase. he output of the risk assessment phase is the risk mitigation strategy
and the detailed security requirements for the Web application. Risk mitigation strategy should
not be confused with the risk mitigation phase, which is the phase succeeding the risk assessment
phase in the risk management cycle, where the risks to an existing application are mitigated dur-
ing the development and testing phase of the Application Development Life Cycle. Risk mitiga-
tion strategy is the output from the risk assessment phase, which forms the input for the actual
mitigation of risk in the risk mitigation phase. he risk assessment phase consisted of identifying
critical information assets to gain an understanding of what information needs to be protected.
he application environment and deployment architecture are understood to provide more clar-
ity on the type of application and its users. Security objectives are formulated to understand the
prime motivations and necessity for implementing security for the Web application. Subsequently,
threats that might adversely afect the Web application, are understood and detailed scenarios are