GUIDE · GOVERNANCE AND RISK

Managing cyber risk in your business: method, register and priorities

By the end of this guide you will know how to identify the cyber risks in your company, record them in a single document, assign an owner to each one and decide where to start. The method is designed for businesses without an in-house security team that still have to answer to clients, insurers and, where the law requires it, to authorities.

Updated october 2026
10 min read
Altovar Technical Editorial Team

1. Why cyber risk must be managed like a business risk

Cyber risk is the possibility that an event involving systems, data or people causes harm to the business: a halt in production, the loss of customer data, a fine, a fraud. For many small and medium businesses the subject has stayed in the hands of the IT department, as if it were only a technical problem. In reality it is about economic decisions: how long a stoppage can be tolerated, which data must never be lost, which activities can wait.

Managing risk means making these decisions explicit and written down. It is not necessary to eliminate every risk, which is impossible and expensive. What matters is knowing which risks exist, who is responsible for them and what has been decided to do about them. The method is the same one required by standards such as ISO/IEC 27001 and, for organisations within the scope of the NIS2 directive on the security of networks and information systems, by the Italian transposing legislation, Legislative Decree 138/2024. Even if your company is not subject to it, the method remains useful.

2. The method in five steps

The method described here is deliberately simple. It requires no expensive software or advanced risk analysis skills, but it forces you to answer the questions that matter: what could go wrong, what it would cost, how likely it is and what will be done about it. Growing businesses can later move to more structured methodologies without starting over, because the underlying questions remain the same.

Follow the steps in order and do not skip any. The most common mistake is to start from spectacular threats, such as a Hollywood-style attack, and forget the mundane but critical assets: the shared mailbox, the invoicing system, the file with orders to fulfil. Start with the assets and ask, for each one, what would happen if it were unavailable for a whole day. Only then move on to threats and the vulnerabilities linked to them.

  1. List the IT assets that matter to the business, such as the management system, email, customer records, the website and connected devices, with an owner for each.
  2. For each asset, describe the most plausible threat: stolen credentials, a server failure, human error, malware that encrypts files.
  3. Assess the impact on the business if the asset stopped working or were compromised, using a simple scale such as low, medium and high.
  4. Assess the likelihood using the same scale, based on facts such as past incidents, supplier reports and the results of checks.
  5. Decide how to treat high and medium risks, and record the decision with a date and an owner.

3. The risk register: what it contains

The risk register is the document in which the method takes shape. It should be single, easy to read and easy to update. If it is split into separate sheets for each department, nobody reads it in full and the entries end up contradicting each other. Each row is a risk linked to a specific asset, and each risk has a named owner: a person, not a generic area such as 'IT'.

The table shows the minimum fields. You can add others, such as the risk category or a reference to a contract, but avoid fields nobody will fill in. The register must be readable by management in a few minutes. If a field does not help make a decision, remove it. Choose the fields according to the decisions you need to take, not according to what the software happens to offer.

FieldWhat to writeGeneric example
IdentifierA short, unique code for each riskRIS-ACC for access risks
Asset involvedThe system or process exposedThe invoicing system
Threat and causeWhat could happen and whyCredentials of a team member used by a third party
Impact and likelihoodA qualitative level with a written reasonHigh impact and medium likelihood, because access does not require a second factor
TreatmentWhat will be done, by whom and by whenActivation of multi-factor authentication, IT owner, agreed date
Status and reviewCurrent status and date of the next checkOpen, to be reviewed at the next management meeting

4. Assessing likelihood and impact without inventing numbers

Assessing risk with precise numbers gives an illusion of accuracy. Probabilities of an attack, for example, are hard to estimate reliably for a single company, and anyone who presents them as certain is oversimplifying. For this reason a qualitative scale works better, with a few clearly defined categories such as low, medium and high. The result is a shared scale that management understands and can review over time.

The definitions should be written together with management. For impact you can say it is high when the business stops for a length of time that cannot be recovered, when personal data of customers is involved or when notification obligations apply. For likelihood, use facts: incidents that have already happened in the sector or in your company, supplier reports, the results of checks. Next to each assessment write the reasoning, because in a few months someone will need to understand why you decided as you did.

5. Choosing the treatment: reduce, transfer, accept, avoid

For each high or medium risk you have four options. You can reduce it, with technical or organisational controls such as multi-factor authentication or staff training. You can transfer part of it, through a contract with a supplier or through insurance. You can accept it, if the cost of a control exceeds the possible damage, but only explicitly and with a signature. Or you can avoid it, by eliminating the service or the data that creates it.

Transferring does not mean forgetting. A supplier contract may provide for liability and penalties, but it does not remove the duty to protect customer data nor the responsibility towards authorities, and insurance covers only some of the economic consequences. The chosen treatment must be recorded with an owner and a review date. A risk accepted without a stated reason is the most dangerous, because it disappears from the discussion.

6. Responsibilities, review and evidence to keep

Every risk needs an owner of the decision and an owner of the action, which in a small business may be the same person. Management approves the assessment and the most important decisions; the IT department or the supplier carries out the technical controls. Without this separation decisions get stuck between two people who each think it is the other's job. When the decision owner is absent, the choice must still remain in the hands of someone.

The register should be reviewed on a fixed schedule and after every significant event, such as an incident, the arrival of a new supplier or a change to a system. Keep evidence that the work has been done. An auditor, an insurer or an authority will first ask what you decided, when and on the basis of which information. Useful evidence is usually the following:

  • The register with the date of the last update and the history of changes
  • The minutes of the meeting in which management approved the assessments
  • Evidence of controls, such as backup results or access logs for sensitive data
  • Supplier reports on incidents, interventions and changes
  • The list of accepted risks, with the reasoning and the owner's signature

7. The method within the cluster: topics to explore

This guide is the starting point for a group of related topics. After the risk register, the most frequently asked questions concern the minimum security policy, the indicators to show management, the report for the board of directors, the assessment of IT suppliers, preparation for an external audit, the requirements of a cyber insurance policy, the organisational model for the administrative liability of entities, the role of a part-time security officer and the RACI matrix, that is, who does, who approves, who is consulted and who is informed.

The first topic to read is the minimum policy, because it sets the rules that the register refers to. If you need to present the subject to management, read the one on reporting straight after. The other topics make sense once the register already exists, because they tell you what to check and how to demonstrate it. Each topic refers back to the entries in the register, so its usefulness grows with the quality of your map.

8. How to start

The first concrete action this week is a list of the IT assets that matter, with the owner of each one next to it. No formal project is needed. A spreadsheet, a short meeting with whoever manages IT and a person in management who really knows the business are enough. Also set a date by which the list will be complete, so the work does not stay pending.

Straight after, arrange a meeting in which management assesses the first risks and chooses the measures to complete within the quarter. Once the list is ready, fill in the columns still missing from the register. The result will not be perfect, but it will be a document on which decisions can be made, and that is the starting point. Minute the decisions taken at that meeting, even if they are only partial.

Frequently Asked Questions

Do I need dedicated software for the risk register?

For most small and medium businesses a shared spreadsheet is sufficient, as long as it has an owner, a change history and access restricted to those who need to see it. A dedicated tool becomes useful when there are many risks, when several sites or suppliers must contribute or when evidence needs to be tracked in an orderly way. Choose according to who actually keeps it up to date.

Should the assessment be done by IT or by management?

Both should work together. IT knows the systems and the technical threats; management decides what impact is acceptable for the business. An assessment made only by the technical department tends to underestimate economic damage, while one made only by management tends to underestimate likelihood. What is needed is a discussion that puts the two points of view side by side and records the final decision.

How often should the register be updated?

It depends on how fast things change. As a rule, schedule a review at least once a year and update it whenever a system, a supplier or a way of working changes significantly. After an incident, review the related entries straight away. A register left untouched for many months quickly loses its value, because it no longer reflects the real business.

Is this method enough to comply with NIS2?

The method is a foundation, but it is not enough on its own. The NIS2 directive, transposed by Legislative Decree 138/2024, requires specific measures, documented risk management and incident handling with defined notification deadlines. If your company might fall within its scope, check with a consultant which obligations apply to you.

Does a cyber insurance policy remove the need to manage risks?

No. Insurance may cover some of the economic consequences of an incident, but it does not prevent it, does not restore the business on its own and does not cover all damage. Insurers also ask for evidence of active controls before granting a policy. The risk register is also the document that shows which controls really exist.

Where should a business with limited resources start?

Start with the assets that would cause the most damage if they stopped for a day: usually email, accounting, the management system and the customer archive. For each one, write who manages it, what data it contains and what would happen in case of a stoppage. With this first map you can choose a few priority actions to complete over the coming months, without having to tackle everything at once.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →