Risk Part1 Flashcards
General
applies to systems and software over its lifecycle. Our focus is risks relating to software engineering project management, however the scope of ISO16085 is wider as it covers the entire lifecycle of systems and software.
Information Security Risk Management - application security
Focus on development of insecure applications as a project management risk. The scope of ISO27034-5 is wider, as for example it encourages the establishment of libraries of reusable application security functions that may be shared both within and between organizations.
Risk Management Process
The process includes context establishment, risk assessment, risk treatment, risk acceptance, risk monitoring, and communication. These steps are relevant in various fields, including software engineering and project management.
Residual Risk
the portion of risk that remains after implementing controls or countermeasures.
Risk Assessment
process of identifying risks to operations, assets, individuals, organizations etc resulting from the operation of a system.
Risk Identification
Finding, Recognizing and describing risk (NIST def.)
Risk Estimation
Assigning values to the probability and consequences of a risk, enabling the calculation of risk exposure (ISO/IEC27005)
Risk Evaluation
Comparing risk analysis results to criteria to determine whether risk is acceptable or tolerable (NIST).
Risk Estimation
Involves assigning values to the probability and consequences of a risk. This allows calculation of risk exposure: Risk Exposure (RE) = Risk Probability x Risk Impact.
The units for Risk Exposure and impact may be monetary or other quantifiable measures
Mapping of Risks on a Risk Matrix
The values assigned to Risk Probability and Risk Impact are used to plot risks on a risk matrix. This helps to categorize risk based on their severity and likelihood.
Listing of Risks in a Risk Register
A risk register contains a list of organizational risks, identified by the following attributes:
- Unique identifier
- Description of the Risk
- Impact in monetary terms
- Probability
- Risk Rating (meaning the RE)
- Risk Owner (Ideally and individual)
- Dates of risk identification
- Actions being taken
- Owner of actions being taken
- Date for completion
Risk Appetite
level of risk that an organization will tolerate
Risk Acceptance - Governance
the risk is accepted by the information owner, not the CISO. Same in SE Project Management. It is usually the risk owner who decides how to manage risk
Risk acceptance can happen because
- It can be temporary, because the organization plans to address the risk in the future
- It can be because the cost of addressing the risk is higher than the cost of risk materialization
- It can be because the risk is below the organization’s risk appetite
Qualitative Risk Assessment
- Risk Exposure = Risk Probability x Risk Impact
- Evaluates risk without relying on precise probabilities or values, often comparing similar risks
- Useful for risks that are hard to quantify.