Risk analysis for information security: a step-by-step method

Line drawing of a balance scale with a document folder on one pan and a warning triangle on the other, the triangle in blue

A method a mid-sized company can run with its own people in a few workshops: what to prepare, the eight steps, how to write the risk register and when to do it again.

In short

An information security risk analysis finds what could harm the information your business depends on, rates each risk by likelihood and consequence, and decides what to do about it. Prepare scope and rating scales, list the information that matters, identify threats and weaknesses, rate, prioritise, choose treatment, name owners and repeat when something changes.

Most companies already know their biggest worries. What they lack is a repeatable way to compare them, justify the spending and show a customer or supervisor why they chose the measures they did. This guide is written by Devies, a Gothenburg-based product and engineering consultancy, for IT leaders, security leads and managers who have to run a risk analysis (riskanalys) for information security, often for the first time. It builds on the ISO/IEC 27005 and NIST SP 800-30 approaches but keeps the method small enough for a company of a few hundred people.

What is an information security risk analysis?

An information security risk analysis is a structured review of what could go wrong with the confidentiality, integrity or availability of your information, how likely that is, how much it would hurt and what you will do about it.

Some definitions keep the work precise:

  • A risk is the combination of an event that could happen and its consequence for the business, for example "a supplier's support account is taken over and customer data is downloaded".
  • A threat is what could cause the event: a criminal group, a careless mistake, a power cut.
  • A vulnerability is the weakness the threat uses: a shared password, a missing backup, an unpatched server.
  • Risk treatment is the decision you make: reduce the risk, avoid it, share it, for example through a contract or insurance, or accept it.

People also search for this as an information security risk assessment. The terms are used interchangeably; strictly, assessment covers identifying, analysing and evaluating, while analysis is the middle part, but nobody needs to argue the difference in a workshop. The analysis is also different from threat modelling. Threat modelling looks at one system's design and data flows, while the risk analysis looks at the whole business. If you build software, use both: the risk analysis tells you which systems deserve a threat modelling workshop.

What do you need before you start?

You need a clear scope, agreed rating scales and the right people in the room, because without them every rating becomes an opinion.

NIST SP 800-30 Revision 1, NIST's guide for conducting risk assessments, splits the process into four steps: prepare, conduct, communicate results and maintain. Preparation is the step most teams skip. Before the first workshop, agree on:

  • Scope. One business area, product or process at a time, for example "order to delivery" or "the customer portal and its support".
  • Rating scales. Three to five levels for likelihood and for consequence, each with a plain description. "High consequence: customers cannot order for more than a day, or personal data on many customers is exposed."
  • Risk appetite. Which level management accepts without further action, and who may accept higher risks.
  • Participants. The people who run the process, someone from IT, a person who knows the suppliers, and a decision maker for the final session.

How do you run a risk analysis, step by step?

Run the risk analysis as eight short steps, from the information you protect to the owner who acts, and record every step in one register.

Risk matrix grid with dots for rated risks, one high risk in blue moving along an arrow to a lower cell after treatment
  1. List the information and systems in scope. Customer records, prices, source code, contracts, production data and the systems and suppliers that hold them, including paper and shared drives.
  2. Value each item. Rate how bad it would be if it leaked, was changed without authority or became unavailable. This classification (informationsklassning) tells you where to spend the effort.
  3. Identify threats. For the highest-valued items, ask who or what could cause harm: criminals, insiders, mistakes, suppliers, outages, physical events.
  4. Identify vulnerabilities and existing controls. Note the weaknesses each threat could use, and the controls already in place, so you rate the real situation rather than the worst case.
  5. Rate likelihood and consequence. Use the agreed scales. Discuss differences of opinion briefly and record the reasoning, not only the number.
  6. Evaluate and prioritise. Compare each risk with the risk appetite. Risks above it go to treatment, the rest are documented and accepted.
  7. Choose treatment and owners. For each prioritised risk pick an option, the specific measure, an owner and a deadline. Rate the residual risk you expect after the measure.
  8. Get acceptance and communicate. Management accepts the residual risks in writing, and the people affected learn what changes for them.

A risk analysis for information security (riskanalys informationssäkerhet) is useful only when it ends in decisions. If step 7 produces a list of "consider" items without owners, the analysis has not finished.

What does a good risk register look like?

A good risk register is one table that anyone in management can read in five minutes, with one row per risk and the decision visible on every row.

The rows below are an illustrative example for a mid-sized product company, not data from a real organisation.

Risk

Likelihood

Consequence

Treatment

Owner

Residual

Ransomware encrypts the ERP system and its backups

Likelihood

Medium

Consequence

High

Treatment

Reduce: offline backups, tested restore

Owner

IT manager

Residual

Low

Supplier support account used to download customer data

Likelihood

Medium

Consequence

High

Treatment

Reduce: MFA, time-limited access, logging

Owner

Head of customer service

Residual

Medium

Invoice fraud through a changed bank account

Likelihood

High

Consequence

Medium

Treatment

Reduce: call-back routine on a known number

Owner

CFO

Residual

Low

Office flood destroys paper contracts

Likelihood

Low

Consequence

Low

Treatment

Accept and scan key contracts

Owner

Office manager

Residual

Low

Keep the register alive. Each row should link to the measure in your task tool, and the owner reports status at the management review. Devies saw the value of this when working with Zenseact, where internal processes for risk analyses of cloud platforms and applications were adapted and security requirements were translated into development tasks; see the Zenseact client case.

How often should you repeat the analysis?

Repeat the risk analysis at least once a year and whenever something important changes, because risks move with your systems, suppliers and threats.

Typical triggers are a new system or major supplier, a reorganisation, a significant incident, a new law or a large customer demand. For companies covered by NIS2, the duty is explicit. As of November 2026, Article 21(2)(a) of the NIS2 Directive (EU) 2022/2555 lists "policies on risk analysis and information system security" first among the minimum measures, and Article 21(1) asks for measures that are proportionate to the entity's exposure, size and the likelihood and severity of incidents. In Sweden these duties apply through the Cybersecurity Act (cybersäkerhetslagen).

Product companies have a second reason. The Cyber Resilience Act, Regulation (EU) 2024/2847, requires in Article 13(2) and (3) a documented cybersecurity risk assessment for each product with digital elements, updated during the support period. That is a product-level analysis, but the same scales and register format make it easier to run.

The risk analysis is the engine of an information security management system. For how it fits with policies, controls and review, read information security vs cybersecurity, and what an ISMS is.

Devies

Want a second opinion?

Devies, a Gothenburg-based product and engineering consultancy, works on questions like this with Nordic product and IT teams. Tell us where you are and we will suggest a sensible first step.

Talk to Devies

Frequently asked questions

How long does an information security risk analysis take?

For one business area in a mid-sized company, plan for a preparation meeting, two or three workshops of two to three hours and a decision meeting with management. The first round takes longest, because you have to agree on scales and list the information assets. Later updates are faster, since you review an existing register rather than start from a blank page. Larger scopes should be split into several analyses.

What is the difference between risk analysis and risk assessment?

In everyday use the terms mean the same thing. In ISO terminology, risk assessment is the whole sequence of identifying, analysing and evaluating risks, while risk analysis is the middle part, where you understand the risk and estimate its likelihood and consequence. For a company running its first analysis the distinction rarely matters. What matters is that the work ends in treatment decisions with owners.

Which method should we use for a risk analysis?

Use a simple qualitative method first: three to five levels for likelihood and consequence, described in plain business terms, and one shared register. ISO/IEC 27005 and NIST SP 800-30 both describe this kind of approach. Quantitative methods that estimate money and probability can help for a few large decisions, but they need data most mid-sized companies do not have at the start.

Who should take part in the risk analysis?

Invite the people who run the business process in scope, someone from IT who knows the systems, a person responsible for suppliers and, for the final session, a manager who can accept risks and approve spending. Security specialists facilitate and challenge the ratings. Leaving the analysis to IT alone tends to miss business consequences, paper routines and supplier risks.

Sources

Here’s more

Join Our Newsletter

We handle your data according to our privacy policy.

Shopping Cart

We use cookies

We use cookies to improve your experience on this website. You may choose which types of cookies to allow and change your preferences at any time. Disabling cookies may impact your experience on this website. You can learn more by viewing our Cookie Policy.

Check out

Contact Form text

We will contact you text

We handle your data according to our privacy policy.