Plain-language guides to business cybersecurity and risk assessment

How to Run a Cybersecurity Risk Assessment Step by Step

cybersecurity risk assessment

Worried you don’t know where your biggest security gaps are? A cybersecurity risk assessment finds them in three stages: prepare, conduct, maintain. Follow NIST’s published process and you’ll turn vague worry into a ranked list of risks.

This page is part of a wider look at business cybersecurity, so read it alongside the other topics there.

Item Value
Reference guide NIST SP 800-30 Rev. 1, Guide for Conducting Risk Assessments
Published September 17, 2012
Replaced SP 800-30 from July 2002
Stages in the process Three: prepare, conduct, maintain
Levels of the risk management hierarchy Three tiers

These figures come from the NIST Computer Security Resource Center page and the NIST publication page. Publication details can change, so check the source before you rely on them.

What a cybersecurity risk assessment actually does

A cybersecurity risk assessment is a structured way to work out what could go wrong with your systems and data, how badly, and what to fix first. It gives you evidence for decisions instead of gut feeling.

NIST describes the output as information that lets senior leaders decide on appropriate courses of action in response to identified risks. In plain terms, the assessment exists to support a decision about money, time and priorities, not to produce a document that sits in a drawer.

The reference most people start from is NIST’s Special Publication 800-30 Rev. 1. It was written to guide risk assessments of federal information systems and organizations, and it amplifies the guidance in Special Publication 800-39. As of the September 2012 publication, NIST states that nongovernmental organizations may use it on a voluntary basis, so a business can borrow the method without being bound by it.

The three stages NIST describes

NIST breaks the work into three steps: prepare for the assessment, conduct the assessment, and maintain the assessment. The guide also explains how risk assessments and other organizational risk management processes complement and inform each other.

cybersecurity risk assessment Whiteboard discussion
Two colleagues stand beside a whiteboard, with one gesturing toward its surface.

The guide also notes that risk assessments are carried out at all three tiers of the risk management hierarchy. For a small or mid-sized business, you can read that loosely: some risks concern the whole organization, some concern a business process, and some concern one system.

The rest of this page walks through each stage in turn, with practical choices a business owner or IT lead can make.

Prepare: set the scope and ground rules

Preparation is where most assessments are won or lost. If you skip it, you end up with a long list of worries and no way to compare them.

Before you look for a single weakness, settle these points:

  • Purpose: what decision will the results support, such as a budget request, a customer questionnaire or an insurance renewal?
  • Scope: which systems, sites, suppliers and data types are in or out.
  • Assumptions and limits: what you will take as given, and what you cannot assess this round.
  • Rating scale: how you will describe likelihood and impact, for example low, medium and high, with a sentence defining each.
  • People: who owns each system and who signs off on the final ranking.

Write the scale down in plain language. Two people rating the same risk should land on roughly the same answer.

Conduct: find threats, weaknesses and rank the risks

The conduct stage is the core of the work. NIST’s own keywords for the guide include threat sources, the risk model and residual risk, which hint at the order of thinking.

  1. List your assets: the systems, data and services the business cannot do without.
  2. Identify threats: who or what could cause harm, from criminals and careless mistakes to supplier failure and outages.
  3. Identify weaknesses: unpatched software, shared passwords, missing backups, over-broad access.
  4. Estimate likelihood and impact for each threat and weakness pairing, using your agreed scale.
  5. Combine the two into a risk rating and rank the results.
  6. Decide a response for each risk: reduce it, transfer it, avoid it or accept it, with a named owner.

Record everything in a risk register, one row per risk. A cyber risk assessment template can give you ready-made columns so you aren’t starting from a blank page.

Technical checks feed this stage. The guide on vulnerability scan vs penetration test explains how those two methods differ, which helps you pick the right evidence for the weaknesses you list.

Maintain: keep the assessment alive

An assessment goes stale as soon as your business changes. New software, a new supplier, a new office or a staff departure can all shift the ratings.

NIST treats maintaining the assessment as a stage in its own right rather than an afterthought. Practical habits that fit that stage:

  • Review the register on a fixed schedule that you set, and after any major change.
  • Track each action to completion and re-rate the risk afterwards.
  • Note the residual risk you have accepted, and who accepted it.
  • Report the top risks to leadership in a short, plain summary.

Residual risk is what remains after your controls are in place. Writing it down keeps accepted risks visible instead of forgotten.

Common mistakes to avoid

The most common failure is scope creep: trying to assess everything at once and finishing nothing. Start with the systems that hold your most sensitive data or keep revenue flowing, then widen the scope next round.

A second mistake is treating the exercise as an IT-only task. Finance, operations and HR know which processes would hurt most if they stopped, so involve them when you list assets and rate impact.

A third is buying tools before ranking risks. Cost-benefit thinking, another keyword on NIST’s page, means matching the size of the control to the size of the risk it reduces.

Frequently asked questions

Do I have to follow NIST SP 800-30 to run a cybersecurity risk assessment?

Show answer

No. As of the September 2012 publication, NIST states that nongovernmental organizations may use it on a voluntary basis. You can adapt the three-stage approach to your own size and needs.

Where should I start if I have never done an assessment?

Show answer

Begin with the prepare, conduct and maintain structure. Agree your scope and rating scale, list your most important assets, and rank a small first set of risks before widening the scope.

Who should see the results?

Show answer

Senior leaders, because NIST frames the assessment as the information they need to decide how to respond to identified risks. System owners should also see the items assigned to them.

Is a risk assessment the same as a vulnerability scan?

Show answer

No. A scan is one technical input that helps you spot weaknesses. The assessment goes further by weighing threats, likelihood and impact so you can rank what to fix.