Plain-language guides to business cybersecurity and risk assessment

A Simple Risk Register Template You Can Adapt

cyber risk assessment template

Staring at a blank page? A cyber risk assessment template can be a simple risk register: one table listing each asset, threat, rating, owner and next action. Start small and refine it as you learn.

This guide sits within the wider topic of business cybersecurity, and it shows you how to build the register itself.

Item Value
Average global cost of a data breach $4.44 million (2025)
Change versus the 2024 record high Down 9%
Expected cost of cybercrime $23.84 trillion by 2027
CIS Risk Assessment Method, first version Version 1.0, published in 2018
Simple qualitative rating scale High, moderate and low

These figures come from Netwrix and CyberSaint. They can change, so check the sources before you rely on them.

What a cyber risk register is

An Upcover guide from March 2023 describes a risk register as a document organisations use to record their identified potential risks. It also captures the probability of each risk, its consequences for the business and the mitigation strategies meant to reduce it, according to that guide.

That makes it a practical template: you do not need special software, only a table that everyone on your team can read. The same guide says the format lets people see which risks the business faces and who is responsible for managing them.

Why bother? Netwrix reports that the average global cost of a data breach reached $4.44 million in 2025, according to IBM, down 9% from 2024’s record high, as covered in its template guide. Your own losses may be far smaller, but the figure shows why planning ahead is worth an afternoon.

The full process that feeds a register is covered in the guide to cybersecurity risk assessment.

The columns your template needs

Keep the first version narrow. Each column should answer one question you will actually use when deciding what to fix first.

  • Asset: what you are protecting, such as a website, a server, trade secrets or partner documents.
  • Threat: what could cause harm, such as a system failure, a natural disaster, a malicious action or a human error.
  • Vulnerability: the weakness a threat could use, such as an overprovisioned user account or a misconfiguration.
  • Likelihood: how probable it is that the threat uses the weakness.
  • Impact: the damage if it happens, such as financial loss, legal costs, data loss or downtime.
  • Rating: the overall level you assign from likelihood and impact.
  • Owner: the named person responsible for the risk.
  • Treatment: what you will do next, and by when.

The asset, threat and impact examples above follow the assessment steps in the Netwrix guide. The owner column matters just as much: the Upcover guide says a register should clearly assign responsibilities when managing identified risks, per its explanation.

cyber risk assessment template Chart review
People examine a sheet of colorful charts beside a laptop.

A worked example you can copy

The rows below are illustrative only. Swap in your own assets, and rate them honestly for your own business.

Asset Threat and weakness Likelihood Impact Rating Owner Treatment
Customer database Ransomware via a phishing email Moderate High High Operations manager Train staff, test restoring from backups
Email accounts Password guessing on accounts with weak passwords High Moderate High IT lead Enforce a password policy and sign-in checks
Shared file storage Overprovisioned accounts expose files Moderate Moderate Moderate Office manager Review who can open what
Public website Misconfiguration leaves a page exposed Low Moderate Low Web developer Check settings after every change
Office network Power or system failure stops work Low Moderate Low IT lead Document a recovery plan

Threat examples such as password-guessing, phishing and ransomware, and weaknesses such as overprovisioned user accounts and misconfigurations, are all named in the Netwrix guide.

How to fill it in, step by step

You can complete a first draft in one sitting. The Netwrix guide outlines the assessment flow in its overview, and it maps neatly onto the columns above.

  1. List your assets. Locate the valuable things that threats could hurt, from websites and servers to trade secrets and partner documents.
  2. Note the consequences. For each asset, write what damage would follow: financial losses, legal costs, data loss or system downtime.
  3. Name the threats. A threat is any event that can cause harm, including system failures, natural disasters, malicious actions and human errors.
  4. Find the vulnerabilities. These are weaknesses that could let a third party breach your security and harm your assets.
  5. Rate the risk. Risk is the chance that a threat exploits a weakness and harms an asset, so combine likelihood and impact into one rating.
  6. Assign an owner and a next action. A rating with nobody responsible tends to stay on the page and never get fixed.

How should you score likelihood and impact?

Netwrix explains that risk levels can use qualitative categories, such as high, moderate and low, or numerical values. It adds that smaller organisations may opt for a qualitative approach, at least initially, as described in its guide.

That is a sensible default for a first register. Words are easier to agree on in a meeting than decimals, and you can add numbers later if your decisions need them.

Once rated, work from the top. CyberSaint says templates help you prioritise vulnerabilities by potential impact and allocate resources to the most critical ones first, in its template guide.

If you want a structured method behind your scores, the CIS Risk Assessment Method is one option. Version 1.0 was published in 2018, and CyberSaint says it helps organisations align safeguards and controls with business objectives and risk tolerance, according to the same guide.

When you are ready to map your register to a framework, the overview of the nist cybersecurity framework for small business is a logical next step. The Upcover guide also notes that NIST released a report titled “Integrating Cybersecurity and Enterprise Risk Management (ERM)”, which stresses using a risk register, per that article.

Keeping the register useful

A register that is filled in once and forgotten is a document, not a tool. CyberSaint stresses that regular risk assessments are vital for business continuity, meeting compliance requirements and staying ahead of emerging threats, in its guide.

The same guide cites an expectation that the cost of cybercrime will reach $23.84 trillion by 2027. Treat that as a vendor estimate, but it explains why risk lists need regular attention.

A few habits keep it alive:

  • Update the register whenever you add a new system, supplier or kind of data.
  • Revisit it after any security incident or near miss.
  • Ask each owner to confirm their rows at every review.
  • Move finished items to a closed section instead of deleting them, so you keep a record.

Frequently asked questions

What is a cyber risk assessment template?

Show answer

It is a structured document, often a spreadsheet, that records your assets, threats, weaknesses, ratings and owners in one place. A risk register is the simplest version of it.

Should I rate risks with words or numbers?

Show answer

Either works. Netwrix says smaller organisations may opt for a qualitative approach, at least initially, so high, moderate and low is a reasonable start.

Who should own each risk?

Show answer

Pick a named person who can act on it. The Upcover guide says a register should clearly assign responsibilities for managing identified risks.

How often should I update the register?

Show answer

The sources reviewed here do not set a fixed schedule. Update it whenever your systems, suppliers or data change, and after any incident.