- What Are the Incident Reporting Deadlines Under the KSC?
- Why Isn't an S46 Account Enough to Report an Incident?
- What Should an Organization Do in the First Hours of an Incident?
- How Can You Prepare an S46 Notification Without Knowing All the Details?
- How Can You Test Your Incident Reporting Procedure Before a Real Attack?
17 November 2026
Incident Reporting Under the KSC and the S46 System. What Must Be Done Within 24 and 72 Hours?


- What Are the Incident Reporting Deadlines Under the KSC?
- Why Isn't an S46 Account Enough to Report an Incident?
- What Should an Organization Do in the First Hours of an Incident?
- How Can You Prepare an S46 Notification Without Knowing All the Details?
- How Can You Test Your Incident Reporting Procedure Before a Real Attack?
Simply having an account in the S46 system does not mean an organization is ready to report a significant incident. Poland’s National Cybersecurity System Act (KSC) sets clear deadlines: 24 hours for an early warning and 72 hours for an incident notification. To meet these deadlines, an organization must have monitoring, incident classification procedures, and clearly assigned responsibilities in place beforehand. When an incident is detected, there should be no doubt about who makes decisions and who contacts the CSIRT.
What Are the Incident Reporting Deadlines Under the KSC?
Essential and important entities subject to reporting requirements must report significant incidents according to the schedule set out in Article 11 of the KSC. Reports are submitted through the S46 Cyber Hub system to the relevant sectoral CSIRT or, if none has been designated, to the appropriate national-level CSIRT: NASK, GOV, or MON.
What Must Be Reported Within 24 Hours, 72 Hours, and One Month?
| Deadline | Reporting requirement and information required |
|---|---|
| Within 24 hours of detection | An early warning, including available information about suspected malicious activity and possible cross-border impacts. |
| Within 72 hours of detection | A significant incident notification, including an initial assessment of its nature, scale, impact, and available indicators of compromise. |
| Within one month of notification | A final report covering the incident timeline, causes, impact, and measures taken. |
If the incident is still being handled, a progress report must be submitted, followed by a final report within one month of completing the response. Trust service providers are subject to a separate 24-hour deadline for reporting significant incidents.
Why Isn’t an S46 Account Enough to Report an Incident?
An S46 account allows an organization to submit information, but it does not replace incident detection and assessment. Organizations need designated CSIRT contacts, the necessary system permissions, and appointed deputies.
The ability to detect security events is equally important. Monitoring, log analysis, and SIEM and EDR tools help identify breaches more quickly and establish when they were detected. A lack of monitoring does not suspend statutory reporting obligations.
Who Detects an Incident, and Who Decides Whether to Report It?
Responsibilities should be assigned before an incident occurs:
- SOC/IT – detects events, conducts investigations, and preserves data.
- CISO – coordinates incident assessment and classification against the applicable thresholds.
- Compliance – checks reporting obligations and deadlines.
- Designated person – submits the incident notification to the CSIRT.
- Management board – makes decisions about business impact and resources.
The procedure must also work outside normal business hours.
What Should an Organization Do in the First Hours of an Incident?
The first priority is to activate the incident response procedure, assess the scale of the event, and contain its impact. At the same time, the team must determine whether the incident needs to be reported. This assessment should not be postponed until the technical investigation is complete.
Crisis Response Team, Escalation, and Evidence Preservation
The crisis response team should include representatives from IT, security, compliance, communications, and business operations, along with a decision-maker from the management board.
During the first few hours, the team should:
- Activate the escalation matrix and assign responsibility for reporting.
- Establish a secure communication channel that does not depend on potentially compromised infrastructure.
- Contain the attack while preserving evidence.
- Maintain a log of events and decisions, recording the date, time, and name of the person responsible.
Logs, memory dumps, and disk images should be preserved before taking any action that could permanently destroy evidence. These materials also help prepare the 72-hour incident notification.
Can Your Organization Report an Incident Within the Legal Deadline?
Only a tested procedure can answer that question, not an S46 account alone. The team must be able to detect an incident, assess its severity, activate the escalation process, and submit the required information.Tenesys experts help organizations assess their incident response readiness, put procedures in order, and test how well they work.
How Can You Prepare an S46 Notification Without Knowing All the Details?
The early warning must be submitted on time, even if the incident investigation is still ongoing. The phased reporting process allows organizations to provide more information at each subsequent stage.
What Information Should Be Collected for the Early Warning and 72-Hour Notification?
A template prepared in advance should include:
- The date and time of detection and contact details.
- A description of the event and its initial classification.
- The impact on services, customers, and business continuity.
- Information about possible cross-border impacts.
- Available indicators of compromise and actions taken.
Unconfirmed information should be clearly marked. The organization should also record when the notification was submitted and keep confirmation of its receipt.
If S46 is unavailable, the organization should use the alternative reporting channel specified by the relevant CSIRT.
How Can You Test Your Incident Reporting Procedure Before a Real Attack?
The best approach is to run a tabletop exercise: a simulated incident in which participants carry out their assigned decision-making and communication tasks. The exercise shows whether the procedure works under time pressure.
Tabletop Exercise: Scenario, Roles, and Success Criteria
Example scenario: At 2:00 a.m. on Saturday, the SOC detects suspicious activity that could disrupt a service. The team must assess the event and decide what to do next.
The exercise should answer the following questions:
- How long does it take to notify the CISO and assemble the crisis response team?
- Who classifies the incident and determines whether reporting is required?
- Does the person responsible for reporting have access to S46 and the necessary permissions?
- Can the team prepare a sample early warning within 24 hours?
- Can the team collect the information needed for the notification within 72 hours?
The exercise should produce a report identifying delays, missing procedures, and the people responsible for making improvements.
Simply confirming that the test took place is not enough. The report must show which tasks were completed correctly and which need improvement.
A KSC and NIS2 compliance audit can also help by assessing incident response processes and identifying gaps in organizational procedures.

Author
Bartosz Pyrczak
Head of Growth
Head of Growth at Tenesys. Connects people, builds relationships, and ensures the company grows in the right direction. Convinced that in IT sales, the one who listens better than they speak wins. Privately a traveler and cyclist.
Read also:
How to Prepare an Information Security Management System for KSC Compliance?
An Information Security Management System (ISMS) is not simply a collection of policies and procedures. It is a way to manage risk, put security controls in place, and check how well they work. The amended Act on the National Cybersecurity System (KSC) places obligations in this area on essential and important entities. Organizations must therefore…How to prepare your company for KSC by April 3, 2027?
April 3, 2027 is not the date to start working on KSC. By then, organizations covered by the transition period should have implemented the required obligations and started using the S46 System. For management boards, CISOs, IT and compliance teams, this means one thing: the regulations need to be turned into a clear action plan….KSC 2026–2028 – who does the Act apply to, what needs to be implemented, and by when?
The amendment to the Act on the National Cybersecurity System, which implements the NIS2 Directive, has been in force since 3 April 2026. For many companies and institutions, this means new obligations related to cybersecurity, incident reporting, audits, and management accountability. Before an organization starts planning KSC implementation, it should determine two things: whether it…




