A simple cyber risk assessment (cyber risk assessment simple) means writing down what could go wrong, estimating how likely each item is and how much damage it would do, and then ranking them to decide what to fix first. NIST SP 800-30 Rev. 1 explains that risk is typically a function of the adverse impact if an event occurs and the likelihood that it occurs. This article offers a method you can run in one spreadsheet, adapted from that idea; it does not replace a full formal assessment.

Terms to know first

These terms are used throughout. We explain them in our own plain words, except the definition of "risk", which comes from NIST SP 800-30.

  • Asset: anything of value to the organization, such as customer data, the accounting system, the website, email, and the people who use them
  • Threat: something that could cause harm, such as an attacker, malware, a staff mistake or a power cut
  • Vulnerability: a weakness that lets a threat succeed, such as unpatched software or an account without multi-factor authentication
  • Likelihood: how probable it is that the event happens
  • Impact: how much damage the organization suffers if it does, in money, time, reputation and service
  • Risk: NIST SP 800-30 says it is typically a function of the impact that would arise and the likelihood of the event
INFOGRAPHIC
Write a risk you can score

Too vague to score

  • Hackersno idea what is harmed
  • Weak securityno event described
  • Data losswhich data, which way?

Specific enough to score

  • Who does what to which assetnames actor and asset
  • What happens nextstates the business effect
  • Reason for the scorewritten beside each value

The NIST SP 800-30 approach

NIST SP 800-30 Rev. 1 (September 2012) divides the risk assessment process into 4 steps, as follows.

  • Prepare for the assessment: set the scope, purpose and method
  • Conduct the assessment: identify threat sources and events, vulnerabilities, likelihood and impact, then determine the level of risk
  • Communicate the results: share them with decision makers and others who need them
  • Maintain the assessment: review it over time

SP 800-30 also describes 3 assessment approaches: qualitative (levels such as low, moderate, high), semi-quantitative (scales or numbers standing in for levels), and quantitative. NIST warns that qualitative assessments have a narrow range of values, which makes risks hard to compare, and that different experts can produce very different results unless each value is clearly defined. It recommends annotating every value with reasons. NIST also says an assessment is valid only for a limited time, because systems, threats and environments change.

A simple 6-step method (adapted from the above; the steps are our own)

This method uses a plain 1 to 5 scale, which is our own adaptation and not a NIST scale. It fits on one spreadsheet. There are 6 steps, as follows.

  • Set the scope: pick one area, such as the email and accounting systems; do not start with the whole organization
  • List the key assets: write no more than 10 whose loss would stall the business
  • Write the risk scenarios: one line per item, stating who or what does what to which asset, and what happens
  • Score likelihood and impact: 1 to 5 each, with a short reason
  • Multiply and rank: risk score = likelihood x impact
  • Choose a response and assign an owner: reduce, transfer (for example by buying insurance), avoid, or accept, with a review date
INFOGRAPHIC
The simple 6-step method
1
Set the scope
pick one area
2
List key assets
no more than 10
3
Write scenarios
one line each
4
Score
likelihood and impact, 1-5
5
Multiply and rank
likelihood x impact
6
Choose a response
assign an owner

The scoring scales (our own example)

The scales below are our own. Adjust the numbers to fit your size. The likelihood levels are as follows.

  • 1 Very low: not expected within 3 years
  • 2 Low: may happen once in 1 to 3 years
  • 3 Moderate: may happen about once a year
  • 4 High: expected several times a year
  • 5 Very high: happens monthly or is happening now

The impact levels are as follows.

  • 1 Minor: fixed within a few hours
  • 2 Low: one team's work stops for about a day
  • 3 Moderate: key work is disrupted for several days
  • 4 High: a core service stops for a week or more, or customer data leaks
  • 5 Severe: the business may not be able to continue

The risk score is likelihood times impact, which gives a value from 1 to 25. We split it into 4 bands: 1 to 4 low, 5 to 9 moderate, 10 to 16 high, and 20 to 25 critical (our own view). Scores 17 to 19 cannot be produced by multiplying numbers from 1 to 5, so there is no such band.

A worked example (our own example)

Imagine a company of 80 people that keeps files on a file server and uses online email and online accounting. Everything below is invented, not data from any real company, and each score is our own judgement.

  • R1 Ransomware encrypts the file server and the backups sit on the same network: likelihood 4 x impact 5 = 20 critical
  • R2 A staff email account is taken over by phishing (tricking someone into entering their password) because multi-factor authentication is not on: 4 x 4 = 16 high
  • R3 A laptop is lost with customer files that are not encrypted: 3 x 4 = 12 high
  • R4 The online accounting provider is down for a day: 3 x 2 = 6 moderate
  • R5 The website is defaced through an outdated plugin: 2 x 2 = 4 low
INFOGRAPHIC
How the R1 score arises
01
Scenario
ransomware encrypts files
02
Likelihood 4
high: several times a year
03
Impact 5
severe: business at risk
04
Score 20
4 x 5 = 20, critical

Ranked by score, the order is R1, R2, R3, R4, R5, which is the order to fix them. Suppose the company adds backups that are kept off the network and cannot be changed. The impact of R1 might fall from 5 to 3, so the new score is 4 x 3 = 12 high. If it turns on multi-factor authentication, the likelihood of R2 might fall from 4 to 2, so the new score is 2 x 4 = 8 moderate. The after-fix numbers are our own estimates, so have the owners review them before relying on them.

When the simple method is not enough

A 1 to 5 scoring table is fast and easy to communicate, but it is coarse. The numbers come from human judgement, and they only rank items within the same list. If you need a formal method or figures in money, look at the 3 sources below.

  • NIST SP 800-30 Rev. 1, full text: has example tables, assessment scales and templates for recording results at each step; free to read
  • ISO/IEC 27005: the standard giving guidance on managing information security risk, 2022 edition; it is paywalled and we did not read its contents, so what we say comes only from ISO's catalog listing
  • FAIR (Factor Analysis of Information Risk): a model that expresses risk in money by estimating how often a loss event happens and how large each loss is; The Open Group has adopted it as the standard called Open FAIR

You can build on this assessment. In CSF 2.0, the Subcategory ID.RA-05 says threats, vulnerabilities, likelihoods and impacts are used to understand risk and inform how to prioritize the response. For the framework overview, see NIST CSF 2.0: The Six Functions and How to Use Them. If your organization is looking at an information security management system, see ISO/IEC 27001:2022 for Beginners, and for ranking software flaws, see CVSS, EPSS and KEV.

Common mistakes

  • Starting with the whole organization at once: the list gets too long for anyone to finish; start with a small scope
  • Writing risks too broadly: "hackers" or "weak security" cannot be scored because it is unclear what is harmed
  • Scoring without writing reasons: NIST warns that different assessors can produce different results, and written reasons make results repeatable
  • Having one person score alone without asking the owners: the people who use a system know its real impact better than the IT team (our view)
  • Filing the result away: with no owner and no date, the risk stays as it was
  • Assessing once and stopping: NIST says an assessment is valid only for a limited time

Start today

  • Pick one area: for example email and the accounting system
  • List no more than 10 assets: and name an owner for each
  • Write 5 to 10 risk scenarios: one line each
  • Ask the owners to help score them: use the 1 to 5 scales in this article or adjust them, and write a short reason
  • Fix the top 2 first: name an owner and a review date

If you want an overview of the safeguards you already have before you begin assessing, try the self-assessment.

References and further reading

The NIST SP 800-30 content comes from the full document, which we opened and read. The FAIR information comes from the FAIR Institute web page and The Open Group blog post, both opened. We have not read the Open FAIR standards themselves. ISO/IEC 27005 is paywalled and we did not read it. The 1 to 5 scales, the 80-person company example, and anything marked as our view are our own and do not come from these sources. This article is not legal or insurance advice.