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.
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
List what matters
Start with ten to twenty assets: customer data, the payment system, the CCTV recordings, the internet links, the head-office network.
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.'
Score likelihood and impact
Use a 1–5 scale for each and multiply. Agree what each number means so scores are consistent.
Choose a treatment
Reduce (add a control), transfer (insurance or contract), avoid (stop the activity) or accept (with a named approver).
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.
Assign owners and dates
Every risk needs one owner and a review date. Unowned risks are never treated.
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.
FAQ
Frequently asked questions
What is residual risk?
The risk that remains after your controls are in place.
Is a risk register required?
Most security standards and many regulators expect one, and it is the base for audits.
Keep learning
Related guides
GRC explained
Read more →Prepare an audit evidence pack
Read more →GDPR for Network Teams: Practical Security Controls and Checklist
What the EU General Data Protection Regulation expects from your network: security of processing, access control, logging, encryption, guest Wi-Fi data, CCTV, retention and breach readiness, with a checklist you can apply.
Read more →PCI DSS v4.0 for Networks: Segmentation, Firewalls and Wi-Fi
How the Payment Card Industry Data Security Standard applies to your network: defining the cardholder data environment, segmentation to reduce scope, firewall and router rules, wireless, logging, testing and secure management.
Read more →HIPAA Security Rule for Networks: Protecting ePHI in Clinics and Hospitals
What the US HIPAA Security Rule means for healthcare networks: risk analysis, access control, audit controls, integrity, transmission security, medical device segmentation and contingency planning.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.