NIS2 / KSC Compliance in Poland
From scope assessment and Gap Analysis to ISMS and the implementation of practical organisational and technical security measures.
- ✓ Scope tailored to the project
- ✓ Reply within 1 business day
- ✓ Vendor-neutral
NIS2 is not another policy to sign. It changes how cybersecurity is managed.
The amendment to the Polish National Cybersecurity System Act (KSC), implementing the requirements of the NIS2 Directive, significantly expanded the number of organisations subject to cybersecurity obligations.
For essential and important entities, this means establishing a structured approach to risk management, responsibilities, incidents, suppliers, business continuity and the actual security of infrastructure and information systems.
sLogic Group helps organisations move from “does NIS2/KSC apply to us?” to an operational cybersecurity model. We start by determining scope and identifying gaps, then structure risk management, the ISMS and relevant processes, and help implement the required organisational and technical security measures.
Scope comes first
We analyse the organisation's activities, sector, size and other relevant criteria to determine the appropriate scope of NIS2/KSC preparation.
Compliance + technology
We do not stop at documentation. We also assess access, backup, monitoring, networking, vulnerabilities, suppliers and actual infrastructure security controls.
A system that actually works
Processes and documentation should be useful during normal operations, audits and real incidents — not simply exist on paper.
Compliance should not mean creating dozens of documents. An organisation should understand its risks, know who owns them and be prepared for situations in which preventive controls fail.
Not sure whether your organisation falls under KSC?
Start with scope assessment and an evaluation of your current level of readiness. We will identify the key gaps and define the right sequence of actions.
Key KSC deadlines
The amended Polish National Cybersecurity System Act entered into force on 3 April 2026. From that date, transition periods began for organisations meeting the statutory criteria.
KSC Register
A key deadline for entities subject to self-registration that already met the relevant criteria when the amended legislation entered into force.
Implementation of obligations
The main transition deadline covering, among other things, implementation of the ISMS, required security measures and readiness to use the S46 system.
First mandatory audit
A deadline applicable to specific essential entities that previously did not hold the status of an operator of essential services.
The exact timetable depends on how and when an organisation acquires essential or important entity status and when the statutory criteria are met. Deadlines should therefore always be assessed in the context of the specific organisation.
Does NIS2 / KSC apply to your organisation?
The first step is scope assessment and self-identification — determining whether the organisation meets the criteria for an essential or important entity.
The assessment may require consideration of:
- the nature of the organisation's activities,
- the sector and subsector specified in the legislation,
- the type of services provided,
- the size of the organisation,
- corporate or organisational relationships where relevant,
- specific statutory criteria,
- the applicable method of registration in the KSC Register.
The first step towards NIS2/KSC compliance is not buying a SIEM, EDR platform or new firewall. The first step is understanding the regulatory scope and the organisation's actual risks.
Where legal interpretation is required, the final qualification should also be confirmed with legal counsel experienced in KSC and cybersecurity regulation.
Which organisations may be covered by KSC?
The new framework covers a broad range of essential and important sectors and may apply to both private organisations and specific public-sector entities.
Energy and transport
Energy, fuels, gas, hydrogen and specific areas of road, rail, air and maritime transport.
IT and digital infrastructure
Digital infrastructure, electronic communications, ICT service management and specified categories of digital service providers.
Healthcare and public sector
Healthcare, selected pharmaceutical and medical-device activities and a broad group of public-sector entities.
Manufacturing and other sectors
Including selected manufacturing activities, chemicals, food, waste management, postal services and research.
The examples above are indicative only. Whether an organisation is subject to the legislation depends on the detailed statutory criteria.
Essential entity vs important entity
Essential entity
Subject to KSC requirements and the applicable supervisory regime. For certain essential entities, the legislation also provides for periodic mandatory cybersecurity audits.
Important entity
Also required to implement appropriate risk management, system security, incident management, supplier security and other measures required under KSC.
In both cases, cybersecurity measures should be appropriate and proportionate to risk, the nature of the organisation and the importance of its systems and services.
What does KSC implementation mean in practice?
KSC compliance is not a one-off audit or a collection of policies. The organisation needs an operational model for managing the security of networks and information systems.
Risk Management
Identification of assets, threats, vulnerabilities and potential impact, followed by conscious prioritisation of security actions.
ISMS
A coherent Information Security Management System covering responsibilities, processes, controls and oversight of their effectiveness.
Incident Management
Detection, classification, escalation, handling and reporting of incidents, together with lessons learned and corrective actions.
Supply Chain Security
Risk assessment of IT providers, cloud, SaaS, hosting, software suppliers and other critical external dependencies.
Business Continuity
Backup, Disaster Recovery, infrastructure resilience and the ability to restore critical services after a failure or cyber incident.
Access & Identity
Permissions, privileged accounts, MFA, administrative access and periodic access reviews.
Vulnerability Management
Identification, prioritisation and remediation of vulnerabilities together with a controlled patch-management process.
Management Oversight
Regular information about risk, progress and decisions requiring management involvement and approval.
Information Security Management System — ISMS
One of the fundamental elements of preparation is implementing an effective Information Security Management System (ISMS).
An ISMS should not be a collection of documents created solely for an inspection or audit. It should reflect how the organisation actually manages security and connect governance with the technical security of infrastructure and systems.
As part of the project, we can help structure areas including:
- cybersecurity roles and responsibilities,
- risk management,
- asset inventory,
- information classification,
- identity and access management,
- supplier security,
- change management,
- vulnerability and patch management,
- backup and business continuity,
- monitoring and logging,
- incident management,
- security reviews and reporting.
Documentation is only the beginning
One of the most common mistakes in compliance projects is treating cybersecurity as a documentation exercise.
A policy may require MFA — but MFA must actually be implemented. A backup procedure may be correct — but backups must be created and tested. A vulnerability-management process may be documented — but someone still has to execute it.
Define
We structure policies, responsibilities, processes, registers and requirements based on risk and regulatory scope.
Implement
We help introduce the required technical changes in access control, networking, backup, monitoring, logging and infrastructure security.
Verify
We check whether the controls actually operate and whether the organisation can demonstrate evidence of their effectiveness.
A security policy describing a control that has never actually been implemented does not improve the organisation's cyber resilience.
Cybersecurity risk assessment
Risk is the foundation of a rational cybersecurity programme. Organisations should not build their security environment around a list of popular products, but around actual threats and the importance of their systems and services.
The assessment may include:
- identification of critical assets,
- dependencies between systems and services,
- threats and vulnerabilities,
- potential incident impact,
- existing security controls,
- residual risk,
- risk treatment plans,
- risk and action owners.
A risk assessment should support decisions. If the organisation still does not know what to do first after completing it, it has failed to achieve its purpose.
Incidents and cyber resilience
An organisation must be prepared not only to prevent incidents, but also to detect, handle, escalate and report them appropriately.
We help structure:
- event and incident reporting,
- classification and priorities,
- roles and responsibilities,
- escalation procedures,
- communication with management and technical teams,
- cooperation with the appropriate CSIRT,
- information required for regulatory reporting,
- root cause analysis,
- corrective actions following incidents.
An important part of cyber resilience is also the ability to recover after a major incident. For this reason, we assess backup, Disaster Recovery, RPO, RTO and dependencies between critical services.
Monitoring, logging and threat detection
An organisation cannot respond to an event it is unable to detect.
Depending on requirements and risk, we can design or develop:
- infrastructure and service monitoring,
- centralised logging,
- SIEM,
- authentication monitoring,
- change and integrity monitoring,
- alerting and escalation,
- backup monitoring,
- security-event analysis processes.
Technical controls are selected according to risk and architecture — we do not assume that every organisation needs the same security product stack.
Supply chain security
Even well-secured internal infrastructure can remain exposed through cloud providers, SaaS platforms, hosting companies, IT service providers, software suppliers and other partners with access to systems or data.
We can help structure:
- a register of critical suppliers,
- supplier criticality classification,
- access to systems and data,
- security requirements,
- supplier risk assessments,
- SLAs and responsibilities,
- exit procedures,
- vendor lock-in and concentration risk.
S46 system and the KSC Register
The S46 system is one of the main communication tools for essential and important entities within the Polish national cybersecurity framework.
As part of the preparation process, we can help organise:
- the organisation's KSC Register status,
- information required for registration and updates,
- responsible points of contact,
- roles and deputies,
- operational readiness to use S46,
- integration of S46 responsibilities with the incident-management process.
NIS2 / KSC and ISO/IEC 27001
KSC and ISO/IEC 27001 are not the same thing. ISO/IEC 27001 certification does not automatically mean that all KSC obligations have been met, and KSC does not automatically require ISO/IEC 27001 certification.
ISO/IEC 27001
An international standard for systematic information security management based on risk, processes, oversight and continual improvement.
NIS2 / KSC
Legal requirements applicable to specific entities, covering areas such as risk management, security controls, incidents, suppliers and governance.
A well-functioning ISMS based on ISO/IEC 27001 principles can nevertheless provide a strong foundation for many areas that are also relevant under KSC.
How do we deliver an NIS2 / KSC project?
Scope & Gap Analysis
We determine regulatory scope, assess the current environment and identify the gap between the current security model and the required state.
Risk & Roadmap
We develop or update the risk assessment and create an implementation plan with priorities, responsibilities and dependencies.
Implementation
We implement agreed processes, documentation and organisational and technical security measures required to close identified gaps.
Verification
We verify the effectiveness of controls, evidence of process operation and organisational readiness for audit or regulatory review.
What does the organisation receive?
The exact deliverables depend on the project scope and may include:
Gap Analysis
A clear view of the current state, identified gaps and their relevance to the implementation programme.
Risk Register
A structured risk register, risk-treatment plan and ownership of agreed actions.
Roadmap
A sequence of actions based on risk, requirements, technical dependencies and organisational capabilities.
ISMS
ISMS structure, roles, policies, procedures, registers and mechanisms for oversight and continual improvement.
Technical Security Measures
Design and implementation of agreed improvements in access control, backup, monitoring, networking and infrastructure security.
Audit Readiness
Verification that processes operate in practice and that appropriate evidence is available to demonstrate their effectiveness.
You do not need to replace your entire infrastructure
An NIS2/KSC programme should not automatically mean buying a new firewall, SIEM, EDR platform, cloud environment and another set of security products.
We assess the existing environment first. If a current solution achieves the required objective and adequately addresses the relevant risk, we do not recommend replacing it simply to introduce another vendor.
We select technology according to risk and organisational requirements — we do not build a shopping list around a particular vendor.
Security still needs to be maintained after implementation
NIS2/KSC is not a one-off project that ends when the documentation is signed. Infrastructure, suppliers, risks, employees and threats continue to change.
The organisation should therefore regularly update its risk assessment, review the effectiveness of processes, track improvement actions and provide management with an up-to-date view of cybersecurity risk.
Ongoing oversight can also be provided through our CISO as a Service.
Why sLogic Group?
Governance + technology
We combine risk management and ISMS expertise with practical knowledge of infrastructure, networking, backup, monitoring, identity and cybersecurity.
Risk-based
Priorities are driven by actual risks and the importance of systems to the organisation — not by a predefined product checklist.
Vendor-neutral
We use existing solutions where they achieve the required objective. The project is not tied to a single vendor.
From assessment to implementation
We do not leave the organisation with documentation alone. We can also design and implement technical security improvements identified through the risk assessment.
Frequently asked questions
Does NIS2 apply in Poland?
Yes. The requirements of the NIS2 Directive were implemented into Polish law through the amendment to the National Cybersecurity System Act, which entered into force on 3 April 2026.
What is the deadline for registration in the KSC Register?
For entities subject to self-registration that met the criteria when the amended legislation entered into force, the key deadline is 3 October 2026. Other cases should be assessed individually.
What is the deadline for implementing KSC requirements?
For organisations subject to the main transition period, the key date is 3 April 2027. This covers implementation of applicable obligations and readiness to use the S46 system.
How do I determine whether my organisation is subject to KSC?
The organisation's activities should be assessed against the statutory criteria, particularly its sector, type of services, size and any specific provisions applicable to its situation.
Can a small company be subject to KSC?
Yes, in specific circumstances. Organisation size is an important criterion, but the legislation also provides for other conditions. A company should therefore not assume exemption solely on the basis of employee numbers.
Does ISO/IEC 27001 certification mean KSC compliance?
Not automatically. ISO/IEC 27001 can provide a strong foundation for systematic information security management, but KSC obligations need to be assessed separately.
Does KSC require ISO/IEC 27001 certification?
The requirement to implement an ISMS should not be treated as an automatic requirement to obtain ISO/IEC 27001 certification.
Is preparing security policies enough?
No. Documentation is only one element. Organisations must also implement and maintain appropriate organisational, operational and technical security measures.
Does NIS2 / KSC require a SIEM?
A single technology should not be treated as a universal requirement for every organisation. Security measures should be selected according to risk and the characteristics of the environment. A SIEM may be justified in some organisations, while an appropriate outcome may be achieved differently in others.
Can you implement technical security controls?
Yes. Depending on the identified gaps, we can design and implement improvements in areas such as backup, monitoring, logging, networking, access control, identity management and infrastructure security.
Can you prepare our organisation for an audit?
Yes. We can perform a Gap Analysis, structure the ISMS, risk management, processes and controls, and verify evidence demonstrating that they operate in practice.
What happens after implementation?
The organisation should continue to review risk, track actions and maintain its security management system. Where ongoing governance is required, sLogic Group can also provide CISO as a Service.
Do not leave NIS2 / KSC preparation until the audit.
Start with the right scope and a Gap Analysis. We can build the roadmap, structure the ISMS and implement security measures designed to work during a real incident — not only during an audit.