For Business · NIS2 and UKSC 2026
NIS2 and UKSC — sensible compliance, not panic
The amended Polish Cybersecurity Act (UKSC) has been in force since April 3, 2026. It's not rocket science — most requirements you're already implementing to some degree. Our job is not to build everything from scratch, but to leverage what works, add missing elements, and help document compliance. Every offering of ours starts with an audit — without it, we don't know what really needs to be done.
How we work
6 stages of NIS2 compliance
Every offering starts with an audit — without it, we can't tell what really needs to be done in your company. We can run the entire process end-to-end or support you only in selected stages. It all depends on what you already have and who works for you.
1. Compliance audit (gap analysis)
The starting point of every project. We check whether NIS2 applies to you, in what scope, where you are today, and where the requirements want you to be. If you already have ISO 27001 or GDPR policies — we don't throw them out, just check what still needs to be added. Result: a concrete list of gaps with priorities and estimated costs.
2. Self-identification
We check whether your company qualifies as an essential or important entity — by sector, size, and revenue. We help prepare the application for the S46 register. The deadline is 6 months from when you meet the criteria — it's not enough that the company has 50 people; the sector and service type matter.
3. Risk analysis
NIS2 doesn't mandate specific tools — it requires risk analysis. We do it together with you: identifying critical assets, threat scenarios, likelihood, and impact. Without this, further decisions are blind — both about what's worth investing in and what can be avoided.
4. ISMS and documentation
The Information Security Management System (ISMS) is the heart of compliance. Policies, procedures, roles, and responsibilities. We create documentation compliant with UKSC and readable for your team — not photocopied templates, but living documents. We build on ISO 27001 if you already have it, or build from scratch.
5. Technical controls implementation
Only those that follow from the risk analysis. MFA, EDR/XDR, SIEM, network segmentation, MDM for phones, backup with restore testing, vulnerability management. We use what you already have in your infrastructure — we only buy and deploy missing elements. We start with the highest risks.
6. Incident procedures and continuity
NIS2 requires reporting of major incidents in 24h (initial) and 72h (detailed). We prepare an incident response procedure, the path to CSIRT, report templates, business continuity plan (BCP), and disaster recovery plan (DRP) — with testing. Without this, reporting during a real incident is improvisation.
Does NIS2 apply to me?
Check self-identification — it's your obligation
UKSC doesn't designate companies through administrative decision — you have the obligation to verify yourself whether you're subject to the regulations. Lack of self-identification doesn't protect against penalties. The most common criteria: sector + company size.
Start with a quick self-assessment
Before you order an audit — check yourself where you are. We have 2 free tools: NIS2 applicability calculator and a full IT security self-assessment.
Essential entities
Mostly large companies (250+ employees or EUR 50M+ revenue) from sectors: energy, transport, banking, financial market infrastructure, healthcare, drinking water and wastewater, digital infrastructure, ICT service management, public administration, space. Penalties up to EUR 10M or 2% of turnover.
Important entities
Medium-sized companies (50+ employees or EUR 10M+ revenue) from sectors: postal and courier services, waste management, chemical production, food production and distribution, manufacturing (various categories), digital service providers, scientific research. Penalties up to EUR 7M or 1.4% of turnover.
Indirectly — supply chain
Even if you're not formally subject to NIS2, you can be covered by requirements through contracts. Large essential entities must verify supplier security — which translates into contractual clauses, security questionnaires, audits at your premises. It's often easier to meet the requirements than lose the client.
Personal liability of management
This is the biggest mental shift compared to the previous law. The head of the entity (board, director) bears personal liability for negligence — administrative penalty up to 600% of remuneration. The board must also undergo mandatory cybersecurity training. This is no longer an "IT department" matter.
The hardest part isn't technology, it's the approach
NIS2 is not a magical requirement. It's discipline.
Most companies that come to us for help today already have 60-70% of requirements met — they just don't know it or haven't documented it. MFA on the admin account? You have it. Backup with tests? Usually works. Password policies? Set in AD. Our role isn't to build something new — just to look at what you have from the NIS2 perspective and show what specifically is missing. Without burying your head in the sand, but also without panic.
Order compliance audit →FAQ