1. Why start with a plan rather than a product
NIS2 is the European Directive on the security of network and information systems, transposed in Italy by Legislative Decree 138/2024. It requires organisations within its scope to manage cyber risks in a structured way, document their choices and report significant incidents to the authorities. It is not a list of tools to buy. Buying a more powerful firewall or a monitoring service does not demonstrate compliance, because audits look above all at the process: who decides, how risks are analysed and what happens when something goes wrong.
That is why the first step is a work plan with owners, deadlines and expected results. A written plan forces you to clarify the scope, to distinguish what is already done from what is missing and to estimate the real effort. Without a plan, compliance becomes a series of unconnected purchases, and documentation is prepared only when someone asks for it. The plan is also the tool through which management approves priorities and accepts residual risks.
2. Prerequisites: what you need before you start
Before opening a working file, it is worth checking that you have a few basic elements. They do not need to be perfect: it is enough that they exist and are up to date enough to allow reasoning. The absence of one of these elements does not block the work, but it makes the first analysis cycle longer, and it should be recorded in the plan as an activity to complete.
- An internal sponsor with a real mandate, usually a member of management or a manager who can take spending decisions.
- An up-to-date list of the systems, sites and suppliers that touch the business, even if incomplete.
- A first view of the business-critical services and how long each can be unavailable without serious damage.
- Access to contracts with IT suppliers and to existing policies, even if dated or poorly applied.
- A shared calendar with the people who need to take part: the work does not belong only to the IT department.
3. Establishing whether NIS2 applies to you
The first decision is to establish whether your organisation falls within the scope of the Directive. It depends on the sector of activity, the size and the role you play in the supply chain. The Directive distinguishes essential entities from important entities, with different supervisory regimes. Do not stop at the name of the sector: check with your legal adviser whether your activities fall within the categories provided and which size thresholds apply to your case.
If the answer remains uncertain, the work is not wasted. The systems inventory and the risk analysis are needed anyway, and registration with the competent national authority is an administrative step to assess together with your adviser. Record the conclusion in a document signed by management, with a date and reasons, so the decision remains traceable even when people change. Document this conclusion too, because the first question in an inspection is precisely how the decision was taken.
4. The steps of the plan, in order
The activities below follow a logical sequence. Each step produces a result that the next one needs, so skipping a step usually means redoing work later. You can adapt the names and timings to your organisation, but keep the sequence. Each step also indicates the owner and the expected result, so that the plan becomes a control tool and not just a list of intentions. When a step does not produce its result, go back and correct the previous one instead of moving forward.
- Appoint a compliance lead and assign them the mandate in writing, with budget and timelines.
- Build the inventory of systems, data, sites and suppliers, indicating an internal owner for each.
- Carry out a gap analysis, meaning compare the current state with the required measures and note the differences.
- Analyse the risks to critical services, estimating likelihood and impact with a simple, repeatable method.
- Define the priority measures: business continuity, access management, updates, backups and training.
- Prepare policies and procedures, especially for incident management and notification to the authorities.
- Update supplier contracts, adding security requirements and incident communication obligations.
- Have the plan approved by the governing bodies and schedule training for those who take decisions.
- Verify the results through periodic checks and update the plan whenever the scope or systems change.
5. Common mistakes
The mistakes that slow down compliance almost always repeat in the same way. Recognising them early lets you correct course before spending budget and time on unproductive activities. The list below comes from the general experience of organisations facing the legislation for the first time. A very common mistake is underestimating the time needed for training and for reviewing contracts, which often require more steps than expected.
- Treating NIS2 as a purely technical project, without involving management and administration.
- Buying tools before the risk analysis, with the result of covering the wrong problem.
- Writing generic policies that nobody applies and that do not describe the real systems.
- Failing to clarify who is responsible when a supplier does not meet its commitments or does not report a problem.
- Forgetting systems that are not on the inventory, such as cloud services activated by individual departments without IT knowing.
- Considering the work finished after the first draft, without verifying that the measures really work.
6. How to tell whether compliance is working
A completed plan does not prove that the organisation is compliant. The useful question is whether each area produces the expected evidence and whether that evidence is up to date. The table below proposes some checks to repeat at regular intervals. For each area, keep a document that proves the result, not just the intention. The plan also makes these limits visible to management, which can then decide with full knowledge which measures to defer and which not to.
| Area | Verification question | Evidence to keep |
|---|---|---|
| Governance | Has management approved the plan and does it know its status? | Signed minutes or decision, with date |
| Inventory | Does every critical system have a named owner? | Register updated with the date of the last review |
| Incidents | Who decides and who notifies when something happens? | Written procedure and minutes of a tabletop test |
| Continuity | Has the restoration of critical data been tested? | Restoration test report |
| Suppliers | Do contracts include security requirements and prompt notice obligations? | Clauses included and list of assessed suppliers |
7. Guides that go deeper into individual steps
This guide gives you the overall sequence. The details of each step are covered in dedicated guides in the same series, which you should read when you reach the corresponding step. The questions that go deeper into the plan concern four areas: clarifying whether and how you are involved in the scope of the legislation, understanding which incident notification obligations exist and with what timelines, translating risk management measures into verifiable controls, and building the documents that demonstrate the work done.
Other guides in the series cover the training of governing bodies, the content of supplier contracts, preparation for an inspection by the authority and the minimum list of documents to have ready. The recommended first read is the one on classifying entities, because it determines the scope and therefore which obligations apply. Right after it, the guide on incident notification is worth reading, since it has very tight timelines and must be organised in advance.
8. How to start
The first action this week is simple: schedule a one-hour meeting with management, the IT lead and whoever manages administration and contracts. Put three items on the agenda: who will be the compliance lead, which services are critical according to the people who use them every day, and whether the classification needs to be examined with an adviser before going further.
After the meeting, prepare the minimum inventory of systems and suppliers, with an owner for each, and schedule the reading of the related guides. Do not aim for perfection on the first pass. A simple plan, approved by management and updated regularly, is worth far more than a complete document that stays in a drawer. Each guide has a precise role in the sequence, and reading them in the suggested order saves time for those who must coordinate the work.
Frequently Asked Questions
Does NIS2 also apply to small companies?
It depends on the sector and the size. The legislation identifies categories of activity and size thresholds, and for some activities the scope applies regardless of size. Do not assume either that the company is excluded or that it is involved. Check your specific case with a legal adviser and keep the reasoning for the decision in writing.
How long does compliance take?
It varies with the scope, the complexity of the infrastructure and how well documented the processes already are. An organisation with simple systems and a structured IT provider can complete the first phase in a relatively short time, while organisations with several sites or many suppliers need longer. Time depends more on decisions than on the technical side, which is why it is worth planning it with management.
Do I have to appoint a security officer?
The Directive requires that responsibilities be clear, but it does not in every case mandate a person with a specific title. In practice you need someone with a mandate and time to coordinate the work. This can be an internal employee or an external contact, provided that management knows the role, has accepted it in writing and knows whom to contact in the event of an incident.
Can my IT provider do all the compliance work for me?
A managed provider can help you with the inventory, the technical analysis, monitoring and the preparation of controls. However, governance decisions, acceptance of residual risks and responsibilities towards the authority remain with the organisation. Before signing, ask the provider explicitly what the service covers and which activities remain your responsibility.
Is a certification needed to demonstrate compliance?
There is no single certification that closes the matter. Some organisations use recognised standards, such as ISO/IEC 27001 on information security management systems, to structure the work, which can then be aligned with NIS2 requirements. Assess with your adviser whether it makes sense for you, considering costs, timelines and the actual benefit for risk management.
Where should I start if I have little time?
Start with the activities that cannot wait: appointing a contact person, creating an inventory of critical systems and setting a written procedure for incident notification, which has very tight timelines. The rest of the plan can be developed progressively, provided that you have planned it, approved it and documented it. One concrete step today is more useful than a perfect project that starts in months.