From ITSM to NIS2 – risk awareness as a success factor
Risk management within ITSM has long been seen as a necessary but sometimes forgotten area. Now it's different. Digitalization, increased threat scenarios and new regulations like NIS2 make risk management a core process – not just for IT, but for the entire business.
When IT is the business itself – not just a support – it is no longer enough to solve problems as they arise. Organizations need to anticipate them. This is where risk management makes the difference between reactive and proactive governance.
Risk management as a foundation in IT Service Management
In a modern IT Service Management effort , risk management is woven throughout the entire structure.
With every change, supplier change or incident there are risks – technical, legal, organisational. By systematically identifying, assessing and managing risks, decision-making improves, service becomes more stable and changes can be implemented safely.
Risk management is not about avoiding risks – it's about understanding them.
Which ones are acceptable? Which ones require action? And how do they affect the availability, confidentiality and integrity of the services you deliver?
NIS2 sheds light on risk management
The EU's NIS2 directive requires organizations to actively work on risk management and digital resilience.
The essence is clear, to be able to show how risks are identified, assessed, managed and followed up – in both technology, processes and supply chains.
NIS2 also makes risk management a management issue.
The board and management are responsible for ensuring that risk management is conducted systematically and that decisions are documented. Deficiencies can lead to sanctions – but above all to disruptions that affect the entire business.
From document to living process
Many organizations have risk registers but few have live risk management.
When risks are not linked to systems, processes or suppliers, risk management quickly becomes something theoretical.
By integrating risk management directly into ITSM processes, it becomes concrete.
A change can automatically trigger a risk assessment. A new contract can be linked to supplier risks. And analysis of incident data can reveal recurring vulnerabilities.
In this way, risk management does not become a document but a continuous part of operational management.
Next step – build risk management into practice
To succeed, three components are required:
- Structure – a method for how risks are identified, assessed and classified.
- Responsibility – clear roles and mandates for follow-up and decisions.
- Follow-up – ongoing reporting and visualization of risk levels in management forums.
When risk management is integrated into ITSM and follows NIS2 principles, digital resilience and a more secure foundation for future services are created.
Read more

Henrik Traveler
Commercial Product Manager
henrik.resare@easit.com
+46 70 249 36 06