Skip to content

DOMAIN 1 · Security and Risk Management

Risk assessment and treatment

Build defensible risk scenarios, compare qualitative and quantitative analysis, and connect residual risk to accountable decisions.

Risk assessment supports a decision under uncertainty. Before scoring anything, establish the purpose, scope, time horizon, assumptions, and information sources. An assessment for choosing a supplier needs different evidence from an assessment of a production system’s resilience. NIST SP 800-30 describes four stages: prepare, conduct, communicate, and maintain.1

The assessment should say who will use its results and which decisions it can support. A precise-looking score is unhelpful when its underlying scenario is vague.

Distinguish a threat source, a threat event, a vulnerability, and an adverse consequence. A criminal group is a source; credential theft is an event; missing phishing-resistant authentication may enable the event; fraudulent changes to payment instructions are a business consequence. Existing controls and the operating environment affect likelihood and impact.1

A useful scenario states an affected asset, the event, enabling conditions, and the resulting harm. It also records uncertainty: an estimate based on verified incident history deserves different confidence from an unsupported guess.

Approach What it expresses Main caution
Qualitative Defined categories such as low, moderate, high Labels must have shared meanings
Quantitative Numerical estimates of frequency or loss Sparse evidence can create false precision
Semi-quantitative Numerical scales representing categories A score of four is not necessarily twice a score of two

NIST permits different analytical approaches and emphasizes communicating their assumptions and limitations.1 Do not combine ratings from unrelated scales as though they were measurements with identical units.

Work through an illustrative loss estimate

Section titled “Work through an illustrative loss estimate”

A common learning model uses single loss expectancy, SLE = asset value × exposure factor. Annualized loss expectancy is ALE = SLE × annualized rate of occurrence. These are simplified teaching calculations rather than a complete NIST assessment method.

Suppose an incident would cause an estimated ¥2 million loss and its annual occurrence rate is 0.2. The modeled ALE is ¥400,000. A control costing ¥150,000 annually that reduces the modeled rate to 0.05 produces an estimated annual loss reduction of ¥300,000. Its net modeled benefit is ¥150,000 before other costs.

Every number is an assumption for this example. A severe one-off consequence, legal obligation, correlated incidents, or unreliable estimate can make an ALE-only decision inappropriate.

Possible responses include avoiding the risky activity, reducing risk through controls, sharing or transferring financial consequences, and accepting risk within authority. These options can be combined. Insurance may transfer some financial loss while operational disruption and accountability remain.

An ISMS connects assessment to planning and resource allocation.2 Document the treatment owner, deadline, expected effect, evidence, and remaining uncertainty. Risk acceptance should be explicit and authorized; failure to fix a problem does not itself establish acceptance.

Residual risk is the risk remaining after implemented responses and controls. Record the assumptions used to evaluate it. Proposed controls do not reduce current risk until they operate effectively. Explain dependencies: a backup control depends on recoverability, access protection, and tested restoration, not merely a successful backup job.

Communicate important risks in business terms and maintain the assessment when threats, assets, suppliers, or controls change.1

Vulnerability severity is not organizational risk by itself. An exposed weakness on a critical service and the same weakness on an isolated test system may have different consequences. A risk register is not an assessment completed forever: unresolved decisions, changing assumptions, and effectiveness evidence need continued attention.

Connect risk decisions to governance and ISMS and use information classification to understand impact.

  1. NIST, SP 800-30 Rev. 1: Guide for Conducting Risk Assessments, sections 2.3 and 3. ↩ ↩2 ↩3 ↩4

  2. JIPDEC, ISMSユーザーズガイド, 2025, sections 6.1.2–6.1.3, 7 and 8; original summary, no standard text reproduced. ↩

Independent, unofficial study notes. Not endorsed or reviewed by ISC2. CISSP is a registered trademark of ISC2.

Editorial policy & attribution