Cybersecurity Risk Assessment and Safeguards
A practical guide to identifying cybersecurity risks, choosing safeguards, and reviewing the risk that remains.
From Threats to Priorities
Distinguish the terms
assessment helps an organization decide which safeguards best protect its people, information, systems, and operations. The terms , , and describe different parts of that decision:
A is a circumstance or event that could cause harm. It may be deliberate, accidental, or environmental, such as a fire, flood, or power failure.
A is a weakness a could exploit.
connects the chance of an adverse event with how serious its consequences could be.
A does not by itself establish the level of . To assess , ask whether there is a plausible path from the , through a , to harm to an asset. Existing safeguards matter too: they may affect how likely the event is or how severe its consequences could be.
A simple illustrative model is . This is a way to organize priorities, not a precise measurement. Whether an organization uses qualitative labels such as low, medium, and high or a more detailed method, its estimates involve uncertainty. Record assumptions and update the assessment when conditions change.
Assess a plausible scenario
Start with important assets and consider what harm could follow if they were lost, misused, disclosed, or unavailable. Then examine each plausible scenario by asking:
What asset and consequence are involved? Identify what could be affected and what disruption or exposure would mean.
What event could happen, and what could cause it? Consider sources such as attackers, insiders, contractors, suppliers, human error, or equipment and facility failures, as well as environmental events.
What weakness could be exploited, and what safeguards already exist? This links the event to a possible route to harm and accounts for protections in place.
How likely is it, and how serious would the impact be? Estimate both rather than treating one as a substitute for the other.
How should it be prioritized, and what assumptions might change the estimate? Make uncertainty visible instead of presenting the rating as certain.
For example, a moderately likely account compromise may still deserve urgent attention if it could expose sensitive customer records or provide broad administrative access. The important reasoning is not just that account compromise is possible: its potential consequences make the scenario significant. No exact score follows from the example; it illustrates why likelihood and impact must be considered together.
How Attack Paths Reach Assets
Trace how a could reach an asset
An is a sequence of weaknesses or actions that could let a reach an asset. Its starting point might be phishing or social engineering; a compromised, misused, or overly privileged account; an exposed or unpatched system; third-party access; physical access; an accidental action; or insider misuse. These routes can involve people, technology, suppliers, or facilities.
Paths can combine. In the source example, a phishing message may lead to a stolen account. Excessive permissions could then let that account reach shared files, while weak monitoring may delay detection. Each step contributes something different: the initial action obtains access, permissions determine what that access can reach, and monitoring affects how quickly unusual activity is noticed.
Thinking in paths helps connect a possible to an asset and its consequences. It also helps identify where safeguards might interrupt the route, rather than assuming that one weakness explains the whole scenario.
Choosing Complementary Safeguards
Match safeguards to the scenario
Choose safeguards for the specific scenario identified in the assessment. A safeguard may reduce the likelihood of an event, limit its impact if it occurs, or do both. Using means combining complementary protections: one safeguard may fail, but other layers can interrupt different stages of a path or reduce the resulting harm.
The choice should fit the value and sensitivity of the assets, the organization’s tolerance, and practical requirements. Safeguards fall into three broad groups, and a scenario may call for protections from more than one group.
Technical safeguards
Technical safeguards are built into systems and technology. Examples include multi-factor authentication (MFA); least privilege and role-based permissions; separate administrator accounts; timely access removal when roles change; secure configuration and remediation; limiting unnecessary internet-facing services; network segmentation; encryption; endpoint protection; logging and monitoring; and tested backups.
The source’s phishing example shows how layers can complement one another. If phishing could expose an employee’s password, MFA can make password theft alone less useful; least privilege can limit the account’s reach; and monitoring can help identify unusual activity. These safeguards address different aspects of the same scenario rather than relying on one control to solve every problem.
Physical and administrative safeguards
Physical safeguards protect facilities, equipment, and the people who use them. Examples include locked doors and server rooms, badges, visitor sign-in and escort procedures, guards or cameras where warranted, secure storage for portable devices, and environmental protections such as fire detection and backup power. A badge system is more effective when access rights are reviewed and doors are not routinely held open for unknown visitors; the safeguard’s practical operation matters, not just its presence.
Administrative safeguards are policies, responsibilities, and work practices. Examples include written access-control and acceptable-use policies; awareness training; screening and onboarding; prompt offboarding; supplier security requirements; incident-response plans; and periodic access reviews. Training is more useful when it teaches practical actions, such as verifying unusual payment requests through a separate channel, and gives people a clear way to report suspected incidents.
Across all three groups, the goal is to address the assessed scenario with suitable, complementary protections—not to select safeguards in isolation from the assets, risks, and practical requirements involved.
Responding to and Reviewing Results
Choose a response and check the result
Compare the expected reduction from a safeguard with its cost, operational impact, and implementation effort. Address high-impact scenarios first, while also looking for low-cost safeguards that could reduce several risks at once.
If a cannot be eliminated, an authorized decision-maker may accept it, transfer some consequences through contractual or insurance arrangements, or avoid the activity that creates it. These are different responses: accepting leaves the in place as a decision; transferring addresses some consequences; avoiding removes the activity that gives rise to the .
After implementing safeguards, assess whether they are effective and consider —the that remains. Do not assume that putting a safeguard in place has eliminated the scenario. Reassess after significant changes, incidents, new vulnerabilities, or changes to suppliers or business operations. In this way, assessment connects a plausible scenario to a priority, a response, and a continuing review.