Hands-on tutorial

Tutorials · Compliance

How to Build an Information Security Risk Register

A risk register turns worries into decisions. List your important assets, the threats to them, how likely and how harmful each one is, what you will do about it and who owns it.

Beginner12 min7 steps

Before you start

  • A spreadsheet or GRC tool
  • An asset list (sites, systems, data, devices)
  • One hour with an IT lead and a business owner

Step by step

  1. List what matters

    Start with ten to twenty assets: customer data, the payment system, the CCTV recordings, the internet links, the head-office network.

  2. Write each risk as a sentence

    Use the pattern: 'Because of <cause>, <event> may happen, leading to <impact>'. Example: 'Because guest Wi-Fi shares a VLAN with staff, an attacker may reach the POS, leading to card data loss.'

  3. Score likelihood and impact

    Use a 1–5 scale for each and multiply. Agree what each number means so scores are consistent.

  4. Choose a treatment

    Reduce (add a control), transfer (insurance or contract), avoid (stop the activity) or accept (with a named approver).

  5. Link controls to products

    For example: segment guest Wi-Fi with VLANs and NavGATE firewall rules, protect admin access with RADIUS/AAA, keep firmware current with NavCloud updates.

  6. Assign owners and dates

    Every risk needs one owner and a review date. Unowned risks are never treated.

  7. Review every quarter

    Re-score after changes, incidents or new projects and record the residual risk.

Pro tips

  • Keep the first version small; a used register beats a perfect one.
  • Show the top ten risks to management on one page.