← All issues
Week 11 brings three major signals: MSB prepares NIS2 sanctions, the EU AI Office publishes initial guidelines for high-risk systems, and a Swedish logistics company is hit by ransomware that paralyzes its entire order chain. Meanwhile, pressure mounts on the financial sector ahead of the DORA deadline.
NIS2
MSB publishes guidance on NIS2 sanctions
The Swedish Civil Contingencies Agency (MSB) has published guidance describing how sanctions under the NIS2 directive will be applied in Sweden. The document outlines criteria for assessing violations and factors that influence the severity of sanctions.
The guidance makes clear that organizations able to demonstrate an active and documented security process will receive more lenient assessments in the event of violations. MSB emphasizes that sanctions are not intended to punish, but to drive organizations toward better risk management. Maximum fine levels can reach 10 million euros or 2 percent of global annual turnover for essential entities.
For executives and boards, this means personal accountability is increasing. NIS2 contains provisions on management liability, meaning board members can be held personally responsible if the organization fails to meet basic cybersecurity and risk management requirements.
What it means for you
Document your measures now. An active compliance history mitigates sanctions. Ensure the board is informed about their personal liability under NIS2.
Source: MSB →
AI Act
EU AI Office publishes first guidelines for high-risk systems
The European AI Office has released its first draft guidelines for the classification of high-risk systems under the AI Act. The guidelines clarify which AI applications fall under stricter requirements and what obligations operators must fulfill.
Among the areas identified as high-risk are AI systems used in recruitment, credit scoring, critical infrastructure and law enforcement. Operators of such systems must carry out impact assessments, ensure human oversight and maintain technical documentation throughout the system's lifecycle.
The guidelines are open for comments until April 2026, but the signal is clear: organizations already using AI in decision-making processes need to start mapping their exposure now. Waiting until the regulation takes full effect will leave too little time for adaptation.
What it means for you
Map which of your AI systems may be classified as high-risk now. Start with recruitment, credit processes and customer management.
Source: EU AI Office →
Cyber
Swedish logistics company paralyzed by ransomware attack
A mid-sized Swedish logistics company has been hit by a ransomware attack that knocked out its entire order management system. The incident caused delivery delays across multiple regions and exposed significant gaps in the company's incident response capabilities.
According to reports, it took over a week to restore critical systems, during which time the company was forced to handle orders manually. The attack came through a compromised supplier portal, underscoring the risks in the supply chain. The cost of the disruption is estimated at several million kronor on top of the ransom demand itself.
The incident illustrates an increasingly common pattern: attackers are targeting mid-sized companies that often lack dedicated security teams but handle large volumes of data. A functioning incident response plan with regular exercises could have shortened the recovery time significantly.
What it means for you
Incident preparedness is not optional. Test your recovery plan quarterly and include the supply chain in your risk analysis.
Source: SVT Nyheter →
DORA
DORA deadline approaching for the financial sector
With less than six months until full application of DORA (Digital Operational Resilience Act), pressure is mounting on Swedish financial institutions to secure their ICT risk management frameworks. Supervisory authorities have signaled that enforcement actions will begin immediately upon the compliance date.
DORA requires financial companies to map and manage risks associated with third-party IT service providers, including cloud providers. The regulation also demands that companies establish robust processes for incident reporting and conduct regular tests of their digital resilience.
The Swedish Financial Supervisory Authority (Finansinspektionen) has flagged that many Swedish firms still have gaps in their third-party management and incident reporting processes. Companies that fail to meet the requirements risk not only fines but also restrictions on their operations and damage to customer and investor confidence.
What it means for you
Prioritize third-party risk management and ICT incident reporting. Ensure that your IT supplier agreements meet DORA requirements.
Source: Finansinspektionen →
Weekly reflection
This week shows a clear pattern: regulations have moved from theory to enforcement. Organizations still treating compliance as an IT project risk falling behind. The key is to anchor security and compliance in business strategy, not as a side project but as a prerequisite for doing business.
Want to learn more? Book a call with Novudom
Contact us