Identity Governance & Administration
sara.next
  1. sara.next
  2. News
  3. Blog

Blog · 21 November 2025

NIS2 in practice: how to avoid "emergency mode" in the face of growing cyber threats?

  • 3 min read

Did you know that Poland has become one of the main targets of cybercriminals on the world map? The latest data is alarming: we already account for 6% of all ransomware attacks worldwide – more than is recorded in the United States. In 2024 alone, as many as 130,000 incidents were reported to NASK. We are operating under "double risk". On the one hand there is an unprecedented scale of attacks on the energy, logistics and manufacturing sectors, and on the other – legislative chaos around the implementation of the NIS2 directive. Many Polish businesses have adopted a "wait for the act" strategy. At braf.tech we warn: this strategy may cost your company not only huge fines, but above all operational paralysis.

A false sense of time

The NIS2 directive already applies in Europe, but the Polish amendment to the National Cybersecurity System (KSC) act is still being prepared. This lulls businesses into complacency. Research shows that as many as 36% of security experts still do not know whether their organisation is covered by the new rules at all. The problem is that once the act comes into force, the clock will start ticking very fast. Companies will have just 30-60 days to register and about half a year to fully implement the requirements.

Why won't "emergency mode" work?

Implementing complex security processes under time pressure is a recipe for disaster. 75% of organisations in the EU have no dedicated budget for NIS2, and the labour market suffers from a huge shortage of specialists. If you only start looking for experts and solutions after the KSC act comes into force, you will be queuing alongside as many as 10,000 other entities that have suddenly become regulated.

Action plan: 5 steps you need to start today

Regardless of the stage Polish legislation is at, hackers do not take breaks. To avoid chaos, your organisation should take the following steps immediately: Step 1: Verify your status Don't wait for a letter from the authorities. Assess independently and critically whether your organisation is covered by NIS2/KSC. This is the most frequently overlooked, yet key, stage. 1–2 weeks Step 2: Create a map of critical systems Without knowing exactly what in your infrastructure is key to business continuity, it is impossible to assess risk. 2–4 weeks Step 3: Put identities and access in order (IGA) This is one of the most time-consuming elements of implementation. You need to know who has access to what and why. IGA systems such as sara.next automate this process, eliminating so-called ghost accounts and ensuring that roles comply with audit requirements. Managing permissions manually at the scale of NIS2 requirements is practically impossible. 4–12 weeks Step 4: Test reporting procedures NIS2 imposes strict time frames – an incident report must be sent within 24 hours. Is your team ready for this? 1–2 weeks Step 5: Scrutinise the supply chain Remember that NIS2 also makes you responsible for the security of your suppliers and partners. 3–6 weeks

Don't be caught off guard

The Polish economy is entering a period of turbulence. Cybercriminals have sped up, regulations are trying to catch up with them, and you are in the middle of this race. Don't let your company be an easy target. Start by putting your own house in order – especially in access management, which is the foundation of security (Zero Trust). If you need support with an audit or with implementing IGA tools, contact us. What next? Want to see how sara.next can help you meet NIS2 requirements in identity management? Book a free consultation with our expert — contact us.

See sara.next on your own scenarios

During the presentation we will walk through an access request, approval, automatic execution of the change and a review — using examples from your organisation.