A Prototypical Risk Analysis

A majority of risk analysis process descriptions emphasize that risk identification, ranking, and mitigation is a continuous process and not simply a single step to be completed at one stage of the development lifecycle. Risk analysis results and risk categories thus drive both into requirements (early in the lifecycle) and into testing (where risk results can be used to define and plan particular tests).
Risk analysis, being a specialized subject, is not always best performed solely by the design team without assistance from risk professionals outside the team. Rigorous risk analysis relies heavily on an understanding of business impact, which may require an understanding of laws and regulations as much as the business model supported by the software. Also, human nature dictates that developers and designers will have built up certain assumptions regarding their system and the risks that it faces. Risk and security specialists can at a minimum assist in challenging those assumptions against generally accepted best practices and are in a better position to "assume nothing."
A prototypical risk analysis approach involves several major activities that often include a number of basic sub steps.

Learn as much as possible about the target of analysis.
- Read and understand the specifications, architecture documents, and other design materials. - Discuss and brainstorm about the target with a group. - Determine system boundary and data sensitivity/criticality. - Play with the software (if it exists in executable form). - Study the code and other software artifacts (including the use of code analysis tools). - Identify threats and agree on relevant sources of attack (e.g., will insiders be considered?).

Discuss security issues surrounding the software.
- Argue about how the product works and determine areas of disagreement or ambiguity. - Identify possible vulnerabilities, sometimes making use of tools or lists of common vulnerabilities.
- Map out exploits and begin to discuss possible fixes.
- Gain understanding of current and planned security controls.

Determine probability of compromise.
- Map out attack scenarios for exploits of vulnerabilities. - Balance controls against threat capacity to determine likelihood.

Perform impact analysis.
- Determine impacts on assets and business goals.
- Consider impacts on the security posture.

Rank risks

Develop a mitigation strategy. - Recommend countermeasures to mitigate risks.

Report findings
- Carefully describe the major and minor risks, with attention to impacts.
- Provide basic information regarding where to spend limited mitigation resources.

A number of diverse approaches to risk analysis for security have been devised and practiced over the years. Though many of these approaches were expressly invented for use in the network security space, they still offer valuable risk analysis lessons.