•Phases of risk management
•Phases of risk management
Risk assessment
Risk assessment
•Likelihood and impact
Enterprise risk management (ERM) frameworks
Mostcompanies will institute enterprise risk management (ERM) policies and procedures,
based on frameworks such as NIST’s Risk Management Framework (RMF) or ISO 31K.
* Risk and control assessment (RCA)
Most companies will institute enterprise risk management (ERM) policies and procedures,
based on frameworks such as NIST’s Risk Management Framework (RMF) or ISO 31K.
These legislative and framework compliance requirements are often formalized as
a Risk and Control Self-Assessment (RCSA). An organization may also contract an
external party to lead the process, in which case it is referred to as a Risk and Control
Assessment (RCA).
A RCSA is an internal process undertaken by stakeholders to identify risks and the
effectiveness with which controls mitigate those risks. RCSAs are often performed
through questionnaires and workshops with department managers. The outcome of an
RCSA is a report. Up-to-date RCSA reports are critical to the external audit process.
Risk Types
External
•Cyber threat actors and natural or person-made disaster
Internal
•Risks that arise from assets that are owned/managed
Multiparty
•Ripple impacts in the supply chain
Intellectual property (IP) theft
Software compliance/licensing
•Shadow IT
Legacy systems
Concrete values to risk factors (quantitative assessment)
* Exposure Factor (EF)
Single Loss Expectancy (SLE)—the amount that would be lost in a single
occurrence of the risk factor. This is determined by multiplying the value of the
asset by an Exposure Factor (EF). EF is the percentage of the asset value that would
be lost.
* Annualized Rate of Occurrence (ARO)
Annualized Loss Expectancy (ALE)—the amount that would be lost over the
course of a year. This is determined by multiplying the SLE by the Annualized Rate
of Occurrence (ARO).
Difficulty of forecasting likelihood
Difficulty of assessing impact/cost
The problem with quantitative risk assessment is that the process of determining and
assigning these values is complex and time consuming. The accuracy of the values
assigned is also difficult to determine without historical data (often, it has to be based
on subjective guesswork). However, over time and with experience, this approach can
yield a detailed and sophisticated description of assets and risks and provide a sound
basis for justifying and prioritizing security expenditure
Qualitative Risk Assessment
Inherent risk
Level of risk before any type of mitigation has been attempted
Risk Posture
The overall status of
risk management is referred to as risk posture. Risk posture shows which risk response
options can be identified and prioritized.
Risk posture and prioritization
Risk posture and prioritization [potential prioritization]
•Regulatory requirements
•High value asset, regardless of threat likelihood
•Threats with high likelihood
•Procedures, equipment, or software that increase the likelihood of threats
•Return on Security Investment (ROSI)
Risk mitigation/remediation
Risk mitigation (or remediation) is the overall process of reducing exposure to orthe effects of risk factors.
Risk mitigation/remediation
•Deploy countermeasure
•Reduce likelihood or impact or both
risk deterrence (or reduction)
If you deploy a countermeasure that reduces exposure to
a threat or vulnerability that is risk deterrence (or reduction). Risk reduction refers
to controls that can either make a risk incident less likely or less costly (or perhaps
both).
Risk Avoidance and Risk Transference
Avoidance
•Stop doing the risky activity
Transference
•Assignrisk to a third-party
•Cybersecurity insurance
•Limits to transference
cybersecurity insurance
Specific cybersecurity
insurance or cyberliability coverage protects against fines and liabilities arising from
data breaches and DoS attacks.
Risk acceptance/tolerance
Residual risk
Likelihood and impact after mitigation
Risk appetite
* Established at an organization or project level
Control risk
Loss of countermeasure effectiveness over time
Control risk is a measure of how much less effective a security control has become
over time. For example, antivirus became quite capable of detecting malware on the
basis of signatures, but then less effective as threat actors started to obfuscate code.
Control risk can also refer a security control that was never effective in mitigating
inherent risk. This illustrates the point that risk management is an ongoing process,
requiring continual reassessment and re-prioritization.
Risk Awareness
Business impact analysis (BIA)
Business impact analysis (BIA) reports for threat scenarios
•Calculate impact as costs
•Justifies and prioritizes investment in security controls
Business impact analysis (BIA) is the process of assessing what losses might occur
for a range of threat scenarios. For instance, if a DDoS attack suspends an e-commerce
portal for five hours, the business impact analysis will be able to quantify the losses
from orders not made and customers moving permanently to other suppliers based
on historic data. The likelihood of a DoS attack can be assessed on an annualized basis
to determine annualized impact, in terms of costs. You then have the information
required to assess whether a security control, such as load balancing or managed
DDoS mitigation, is worth the investment.
Business continuity planning/continuity of operations planning (COOP)
Business continuity planning/continuity of operations planning (COOP)
•Identifies controls and processes that maintain critical workflows
Where BIA identifies risks, business continuity planning (BCP) identifies controls and
processes that enable an organization to maintain critical workflows in the face of
some adverse event.