Cybersecurity

NIS2 readiness, audits and network protection.

I help public offices and companies prepare for NIS2 and the Polish National Cybersecurity System Act (KSC). I usually start with a gap assessment, then put in place what is missing: network security, backups, procedures and monitoring.

How I can help

Compliance

Audits and NIS2 readiness

  • Security audits against the applicable regulations
  • KRI audits for public sector bodies
  • Gap assessment against NIS2 and the KSC Act
  • Security strategy and a roadmap to compliance
  • Policies, procedures and GDPR documentation
Details

Protection

Network and access security

  • Configuring next-generation firewalls (NGFW)
  • Multi-factor authentication (MFA)
  • Network segmentation and traffic control
  • Secure remote access over VPN
  • Hardening servers and directory services
Details

Testing

Penetration testing

  • Testing web platforms and applications
  • Tests as part of a full security audit
  • Infrastructure vulnerability scanning
  • A report with risk ratings and recommendations
  • Retest after fixes are in place
Details

Monitoring

SIEM, SOC and incident response

  • Network and system monitoring in SIEM/XDR (Wazuh)
  • SOC service with event correlation and alerts
  • Security incident management
  • Help with the incident reporting required by the KSC Act
  • Analysis of logs from FortiAnalyzer and servers
Details

Resilience

Data recovery after an attack

  • Fast recovery of data lost in cyberattacks
  • Ransomware-resistant (immutable) backups
  • Regular recovery tests
  • Business continuity and disaster recovery plan
More on the IT infrastructure page

Not sure where to start?

Start with a gap assessment. Afterwards you know where you stand against the requirements and what to do first.

How the audit works

NIS2 and the KSC Act in Poland

Poland implements the NIS2 Directive through an amendment to the National Cybersecurity System Act (KSC). It covers essential and important entities, including public administration bodies. Each organisation determines for itself whether the act applies to it.

24 h
early warning of a significant incident
72 h
incident notification
1 month
final report with the root cause
  1. 3 April 2026

    The amended National Cybersecurity System Act, implementing the NIS2 Directive, comes into force.

  2. 3 October 2026

    Deadline for registering in the list of essential and important entities (wykaz-ksc.gov.pl). If the act applies to an organisation that has not registered yet, it should do so as soon as possible.

  3. 3 April 2027

    End of the period for adapting systems and procedures, including putting an information security management system in place.

When to get in touch

A few typical situations and what I do about them.

“We don't know whether NIS2 applies to us.”

I look at the sector, size and type of activity. If the act applies, I help with registration and an adaptation plan. If it does not, I prepare a written justification in case anyone asks.

“We have a KRI audit or an inspection in a few months.”

I review the documentation and how work is done in practice, then point out the gaps and the order in which to fix them. That way there are no surprises during the audit.

“We have a firewall, but nobody looks at the logs.”

I collect logs from firewalls, servers and Active Directory in one place (SIEM) and set up alerts. If the organisation has no on-call staff, I suggest an external SOC that works around the clock.

“Someone clicked a link in an e-mail and we don't know what to do next.”

I help assess the scale of the incident, secure the evidence and meet the deadlines: 24 hours for an early warning to CSIRT and 72 hours to report a personal data breach to the Polish data protection authority (UODO).

“We need a penetration test before the system goes live.”

I test the application and infrastructure from the internal network and from the internet. The report with risk ratings and recommendations is ready about two weeks after testing ends.

Inside a gap assessment

A review of security documentation and organisation against KRI, ISO/IEC 27001 and the KSC Act. It usually takes 3 to 6 weeks.

Stages

  1. Agreeing the scope and collecting documents
  2. Document analysis and requirements mapping
  3. Interviews with the people responsible for each area
  4. Gap analysis with impact and priority ratings
  5. Report and remediation plan
  6. Closing meeting with management

Rating scale for each requirement

  • Compliant
  • Partially compliant
  • Non-compliant
  • Not addressed
  • Not applicable

What you get

  • Management reportmaturity level, key risks and priorities in a few pages for management
  • Gap analysisa matrix: requirement, source, document, rating, gap, recommendation and priority
  • Documentation mapwhich documents are current and which need fixing, merging, withdrawing or rewriting
  • Action planwhat to do within 30 days, 1 to 3 months, 3 to 6 months and in the longer term
  • Results presentationa walk-through of the main gaps and recommendations with the people who will implement them

How NIS2 readiness works

  1. 1

    Gap assessment

    Current state, gaps and risks written up in one report.

  2. 2

    Plan and priorities

    A schedule of actions ordered by risk and budget.

  3. 3

    Putting safeguards in place

    MFA, segmentation, backups, procedures and staff training.

  4. 4

    Monitoring and testing

    SIEM/SOC, penetration tests and regular reviews.

Penetration testing

Tests from the internal network and from the internet. The basic scope takes about a day, the extended scope two days, and the report is ready in about two weeks.

Basic scope

  • Reconnaissance: websites, DNS, RIPE database, e-mail headers, job adverts
  • Scanning IP addresses and TCP/UDP ports using different methods
  • Identifying systems, applications, devices and software versions
  • Attempts to intercept traffic and sessions (ARP spoofing, man in the middle)
  • Attempts to take over devices: switches, cameras, UPS units, admin panels, storage arrays and server remote management controllers
  • Analysis of local network traffic at every layer

Extended scope

Everything in the basic scope, plus:

  • Review of system, device and database configuration against good practice
  • Search for known vulnerabilities (CVEs) in the detected software versions
  • Scanning with two independent tools
  • Report of missing patches and updates
  • Risk ratings and advice on which fixes to start with

Frequently asked questions

Does the amended KSC Act apply to my organisation?

The act covers essential and important entities in the sectors it lists, including public bodies. Each organisation determines for itself whether it is covered. I can carry out this analysis and prepare a justification for the decision.

How is a gap assessment different from a KRI audit?

A KRI audit is a mandatory information security audit, carried out at least once a year by bodies performing public tasks in Poland. A gap assessment is the first review before any changes: it shows where the organisation stands against KRI, ISO/IEC 27001 and the KSC Act, and where to start.

How long does a gap assessment take?

Usually 3 to 6 weeks from receiving the documentation. It depends on the number of documents and on the availability of the people responsible for each area.

Does the audit include technical testing?

No. A gap assessment covers documentation and the way work is organised. Penetration tests, vulnerability scanning or a review of Active Directory and firewall configuration can be ordered separately or added to the audit.

How quickly must an incident be reported?

Under NIS2 and the KSC Act: an early warning within 24 hours, a notification within 72 hours and a final report within one month. If the incident involves personal data, the breach must also be reported to the data protection authority (UODO) within 72 hours.

Is an external SOC enough to comply with the KSC Act?

No. Monitoring helps detect and report incidents, but policies, risk analysis, the business continuity plan and training remain the organisation's responsibility. An auditor checks both areas.

Let's see how your organisation measures up to NIS2.

A gap assessment shows where you stand against NIS2 and the KSC Act, what to do first and how long it will take.

Book a consultation