Risk management is a repeatable way to make security decisions: identify what could harm an organization’s assets, assess which risks matter most, and decide what to do about them. It is needed because assets and threats differ in importance, while money and staff time are limited. Protecting everything equally is neither practical nor necessarily useful. section 2.0 section 2.2
A risk assessment is a snapshot. Risk management continues beyond that snapshot because assets are added or retired, their value changes, and new threats and vulnerabilities emerge. Decisions should be documented and revisited as conditions change. section 2.2 section 2.1.3
The process has two main stages—risk assessment and risk treatment—with several practical steps:
- Identify assets, vulnerabilities, existing controls, and plausible threats. section 2.2.1 section 2.4
- Analyze each risk’s likelihood and its potential impact on the organization. section 2.2.1
- Evaluate and prioritize risks so the most significant ones receive attention first. section 2.2.1
- Treat the risks, then keep monitoring them as circumstances change. section 2.2.1 section 2.3
Choosing where to act first
Suppose an organization finds weak multi-factor authentication and a minor user-interface misconfiguration. The first could allow authentication bypass with critical impact; the second could cause user confusion with negligible impact. Comparing likelihood and impact helps direct attention toward the higher risk rather than treating both weaknesses alike. section 2.1.3
|
Vulnerability
|
Threat
|
Impact
|
Likelihood
|
Risk Level
|
|
Lack of software installation control
|
Installation of malicious software (‘malware”)
|
Critical
|
Likely
|
VERY HIGH
|
|
Weak or no multi-factor authentication
|
Authentication bypass
|
Critical
|
Likely
|
HIGH
|
|
Outdated or unpatched firmware
|
Exploitation of known vulnerabilities
|
Moderate
|
Possible
|
MEDIUM
|
|
Minor UI misconfiguration
|
User confusion
|
Negligible
|
Rare
|
LOW
|
|
…
|
…
|
…
|
…
|
…
|
Compare the listed vulnerabilities, threats, likelihoods, impacts, and risk levels to see how a risk assessment supports prioritization. section 2.1.3
Treatment does not always mean adding a security control. Controls can reduce likelihood or impact; replacing a vulnerable system can avoid a risk; insurance can transfer risk. An organization may also consciously accept a risk after weighing its costs and benefits. No choice removes every risk. The risk that remains after treatment is residual risk, which must be evaluated for acceptance or further action. Choices depend on organizational goals, resources, and willingness to accept risk. section 2.2.1 section 2.3 section 2.6





