{"id":3999,"date":"2026-07-14T09:05:00","date_gmt":"2026-07-14T07:05:00","guid":{"rendered":"https:\/\/www.lablogic.pl\/?p=3999"},"modified":"2026-11-14T15:25:54","modified_gmt":"2026-11-14T14:25:54","slug":"what-to-do-after-detecting-an-incident","status":"publish","type":"post","link":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/","title":{"rendered":"What to do after detecting an incident?"},"content":{"rendered":"\n<p class=\"ll-art-meta wp-block-paragraph\"><a href=\"https:\/\/www.lablogic.pl\/en\/michal-rutkowski\/\"><strong>Micha\u0142 Rutkowski<\/strong><\/a> \u2022 for security and IT teams and DPOs \u2022 published July 14, 2026 \u2022 updated October 19, 2026 \u2022 14 min read<\/p>\n\n\n\n<div class=\"wp-block-columns ll-art-shell is-layout-flex wp-container-core-columns-is-layout-7387b849 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column ll-art-rail is-layout-flow wp-block-column-is-layout-flow\">\n<div class=\"wp-block-group ll-art-railinner is-layout-constrained wp-block-group-is-layout-constrained\">\n\n\n\n<\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-column ll-art-main is-layout-flow wp-block-column-is-layout-flow\">\n<div class=\"wp-block-group ll-art-answer is-layout-constrained wp-block-group-is-layout-constrained\">\n<h2 id=\"krotka-odpowiedz\" class=\"wp-block-heading\">Short answer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">First confirm the event and secure the evidence, then limit the effects. The legal assessment runs in parallel from the first hours, not after the technical work is finished. Detection starts several independent clocks at once. An essential or important entity within the meaning of the Polish KSC Act sends the CSIRT an early warning of a significant incident without undue delay, within 24 hours at the latest, and the significant incident notification within 72 hours at the latest. Both deadlines run from detection of the incident, and separate rules apply to a trust service provider and to an important entity that is a public entity (Article 11(1a) and Article 12c). Entities in the banking and financial market infrastructure sectors report under DORA instead. The controller notifies a personal data breach to the President of the Personal Data Protection Office (UODO) without undue delay and, where feasible, within 72 hours of becoming aware of it. It does not notify where the breach is unlikely to result in a risk to the rights and freedoms of individuals. Where the risk is high, it also communicates the breach to the data subjects without undue delay, unless an exception under Article 34(3) GDPR applies. A processor notifies the breach to the controller, not to the authority. Contractual deadlines run from the moment set out in the contract. In the technical work the order of actions matters more than speed. Something done too early \u2014 for example restoring a system from backup before the evidence has been taken \u2014 closes off findings that cannot be reproduced later.<\/p>\n<\/div>\n\n\n\n<div class=\"wp-block-group ll-art-check ll-mi-wpis is-layout-constrained wp-block-group-is-layout-constrained\">\n<p class=\"wp-block-paragraph\"><strong>Have an incident right now? Choose what happened<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The \u201cI have an incident \u2013 what now?\u201d tool shows the first steps for the selected event and gives a preliminary indication of which deadlines under the GDPR and the Polish KSC Act are already running. At the end, you can download an action plan as a PDF. Free of charge, no account required and no cookies.<\/p>\n\n\n\n<div class=\"wp-block-group ll-mi-kafle is-layout-grid wp-container-core-group-is-layout-e54bb18c wp-block-group-is-layout-grid\" style=\"margin-top:20px\">\n<div class=\"wp-block-group ll-klik has-border-color has-background is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-39e845c6 wp-block-group-is-layout-flex\" style=\"border-color:#DCE5F0;border-style:solid;border-width:1px;border-radius:12px;background-color:#FFFFFF;padding-top:20px;padding-right:20px;padding-bottom:20px;padding-left:20px\">\n<figure data-spectra-id=\"spectra-f198b992-65c2-4509-a3fc-c27ab9d9ed24\" class=\"wp-block-image size-full is-resized\" ><img decoding=\"async\" src=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/11\/ll-mi-ransomware.svg\" alt=\"\" class=\"wp-image-6297\" style=\"width:44px;height:44px\"\/><\/figure>\n\n\n\n<div class=\"wp-block-group wp-container-content-ceb7f5b3 is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-7c2834e4 wp-block-group-is-layout-flex\" style=\"padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px\">\n<h3 class=\"wp-block-heading has-text-color\" style=\"color:#071E3D;margin-top:0;margin-bottom:0;font-size:16px;font-weight:600;line-height:1.4\">Files encrypted, someone demands a ransom<\/h3>\n\n\n\n<p class=\"ll-bez-tel has-text-color wp-block-paragraph\" style=\"color:#4A5A6A;margin-top:10px;margin-bottom:0;font-size:13px;line-height:1.45\">Ransomware attack \u2014 what to do in the first hour?<\/p>\n\n\n\n<p class=\"ll-klik-wiersz wp-block-paragraph\" style=\"margin-top:auto;margin-bottom:0;padding-top:10px;font-size:14px;font-weight:600;line-height:1.5\"><a class=\"ll-klik-cel\" href=\"https:\/\/www.lablogic.pl\/i\/en-wiedza#ransom\">Check<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-group ll-klik has-border-color has-background is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-39e845c6 wp-block-group-is-layout-flex\" style=\"border-color:#DCE5F0;border-style:solid;border-width:1px;border-radius:12px;background-color:#FFFFFF;padding-top:20px;padding-right:20px;padding-bottom:20px;padding-left:20px\">\n<figure data-spectra-id=\"spectra-c97b2ad0-4c54-4923-a54a-4c6f0c95f4a3\" class=\"wp-block-image size-full is-resized\" ><img decoding=\"async\" src=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/11\/ll-mi-phishing.svg\" alt=\"\" class=\"wp-image-6296\" style=\"width:44px;height:44px\"\/><\/figure>\n\n\n\n<div class=\"wp-block-group wp-container-content-ceb7f5b3 is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-7c2834e4 wp-block-group-is-layout-flex\" style=\"padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px\">\n<h3 class=\"wp-block-heading has-text-color\" style=\"color:#071E3D;margin-top:0;margin-bottom:0;font-size:16px;font-weight:600;line-height:1.4\">An employee gave away a password via a fake email<\/h3>\n\n\n\n<p class=\"ll-bez-tel has-text-color wp-block-paragraph\" style=\"color:#4A5A6A;margin-top:10px;margin-bottom:0;font-size:13px;line-height:1.45\">Phishing \u2014 is it already a notifiable incident?<\/p>\n\n\n\n<p class=\"ll-klik-wiersz wp-block-paragraph\" style=\"margin-top:auto;margin-bottom:0;padding-top:10px;font-size:14px;font-weight:600;line-height:1.5\"><a class=\"ll-klik-cel\" href=\"https:\/\/www.lablogic.pl\/i\/en-wiedza#phish\">Check<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-group ll-klik has-border-color has-background is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-39e845c6 wp-block-group-is-layout-flex\" style=\"border-color:#DCE5F0;border-style:solid;border-width:1px;border-radius:12px;background-color:#FFFFFF;padding-top:20px;padding-right:20px;padding-bottom:20px;padding-left:20px\">\n<figure data-spectra-id=\"spectra-70b6bb4c-bbec-42c2-a3d9-74ff7cc9320d\" class=\"wp-block-image size-full is-resized\" ><img decoding=\"async\" src=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/11\/ll-mi-konto.svg\" alt=\"\" class=\"wp-image-6294\" style=\"width:44px;height:44px\"\/><\/figure>\n\n\n\n<div class=\"wp-block-group wp-container-content-ceb7f5b3 is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-7c2834e4 wp-block-group-is-layout-flex\" style=\"padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px\">\n<h3 class=\"wp-block-heading has-text-color\" style=\"color:#071E3D;margin-top:0;margin-bottom:0;font-size:16px;font-weight:600;line-height:1.4\">Someone has taken over a mailbox or a Microsoft 365 account<\/h3>\n\n\n\n<p class=\"ll-bez-tel has-text-color wp-block-paragraph\" style=\"color:#4A5A6A;margin-top:10px;margin-bottom:0;font-size:13px;line-height:1.45\">Compromised account \u2014 who has to be notified?<\/p>\n\n\n\n<p class=\"ll-klik-wiersz wp-block-paragraph\" style=\"margin-top:auto;margin-bottom:0;padding-top:10px;font-size:14px;font-weight:600;line-height:1.5\"><a class=\"ll-klik-cel\" href=\"https:\/\/www.lablogic.pl\/i\/en-wiedza#account\">Check<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-group ll-klik has-border-color has-background is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-39e845c6 wp-block-group-is-layout-flex\" style=\"border-color:#DCE5F0;border-style:solid;border-width:1px;border-radius:12px;background-color:#FFFFFF;padding-top:20px;padding-right:20px;padding-bottom:20px;padding-left:20px\">\n<figure data-spectra-id=\"spectra-f92d97a8-f3c3-42af-b4c6-63ac2f17ebc9\" class=\"wp-block-image size-full is-resized\" ><img decoding=\"async\" src=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/11\/ll-mi-laptop.svg\" alt=\"\" class=\"wp-image-6295\" style=\"width:44px;height:44px\"\/><\/figure>\n\n\n\n<div class=\"wp-block-group wp-container-content-ceb7f5b3 is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-7c2834e4 wp-block-group-is-layout-flex\" style=\"padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px\">\n<h3 class=\"wp-block-heading has-text-color\" style=\"color:#071E3D;margin-top:0;margin-bottom:0;font-size:16px;font-weight:600;line-height:1.4\">A work laptop or phone has gone missing<\/h3>\n\n\n\n<p class=\"ll-bez-tel has-text-color wp-block-paragraph\" style=\"color:#4A5A6A;margin-top:10px;margin-bottom:0;font-size:13px;line-height:1.45\">Lost laptop with data \u2014 do I notify the President of UODO?<\/p>\n\n\n\n<p class=\"ll-klik-wiersz wp-block-paragraph\" style=\"margin-top:auto;margin-bottom:0;padding-top:10px;font-size:14px;font-weight:600;line-height:1.5\"><a class=\"ll-klik-cel\" href=\"https:\/\/www.lablogic.pl\/i\/en-wiedza#device\">Check<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-group ll-klik has-border-color has-background is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-39e845c6 wp-block-group-is-layout-flex\" style=\"border-color:#DCE5F0;border-style:solid;border-width:1px;border-radius:12px;background-color:#FFFFFF;padding-top:20px;padding-right:20px;padding-bottom:20px;padding-left:20px\">\n<figure data-spectra-id=\"spectra-11868df8-9191-489f-9d9e-69a8a018c6bc\" class=\"wp-block-image size-full is-resized\" ><img decoding=\"async\" src=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/11\/ll-mi-email.svg\" alt=\"\" class=\"wp-image-6292\" style=\"width:44px;height:44px\"\/><\/figure>\n\n\n\n<div class=\"wp-block-group wp-container-content-ceb7f5b3 is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-7c2834e4 wp-block-group-is-layout-flex\" style=\"padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px\">\n<h3 class=\"wp-block-heading has-text-color\" style=\"color:#071E3D;margin-top:0;margin-bottom:0;font-size:16px;font-weight:600;line-height:1.4\">An email with personal data went to the wrong person<\/h3>\n\n\n\n<p class=\"ll-bez-tel has-text-color wp-block-paragraph\" style=\"color:#4A5A6A;margin-top:10px;margin-bottom:0;font-size:13px;line-height:1.45\">Email to the wrong person \u2014 is it a breach?<\/p>\n\n\n\n<p class=\"ll-klik-wiersz wp-block-paragraph\" style=\"margin-top:auto;margin-bottom:0;padding-top:10px;font-size:14px;font-weight:600;line-height:1.5\"><a class=\"ll-klik-cel\" href=\"https:\/\/www.lablogic.pl\/i\/en-wiedza#missent\">Check<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-group ll-klik has-border-color has-background is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-39e845c6 wp-block-group-is-layout-flex\" style=\"border-color:#DCE5F0;border-style:solid;border-width:1px;border-radius:12px;background-color:#FFFFFF;padding-top:20px;padding-right:20px;padding-bottom:20px;padding-left:20px\">\n<figure data-spectra-id=\"spectra-f82afc3b-c9a4-455e-9fe0-dbdff493ae40\" class=\"wp-block-image size-full is-resized\" ><img decoding=\"async\" src=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/11\/ll-mi-dostawca.svg\" alt=\"\" class=\"wp-image-6291\" style=\"width:44px;height:44px\"\/><\/figure>\n\n\n\n<div class=\"wp-block-group wp-container-content-ceb7f5b3 is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-7c2834e4 wp-block-group-is-layout-flex\" style=\"padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px\">\n<h3 class=\"wp-block-heading has-text-color\" style=\"color:#071E3D;margin-top:0;margin-bottom:0;font-size:16px;font-weight:600;line-height:1.4\">A supplier wrote that data has leaked<\/h3>\n\n\n\n<p class=\"ll-bez-tel has-text-color wp-block-paragraph\" style=\"color:#4A5A6A;margin-top:10px;margin-bottom:0;font-size:13px;line-height:1.45\">Breach at a supplier \u2014 what must the controller do?<\/p>\n\n\n\n<p class=\"ll-klik-wiersz wp-block-paragraph\" style=\"margin-top:auto;margin-bottom:0;padding-top:10px;font-size:14px;font-weight:600;line-height:1.5\"><a class=\"ll-klik-cel\" href=\"https:\/\/www.lablogic.pl\/i\/en-wiedza#vendor\">Check<\/a><\/p>\n<\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-group ll-klik has-border-color has-background wp-container-content-08fe4579 is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-39e845c6 wp-block-group-is-layout-flex\" style=\"border-color:#DCE5F0;border-style:solid;border-width:1px;border-radius:12px;background:linear-gradient(135deg,#F7FAFE 0%,#E4EFFB 100%);padding-top:20px;padding-right:20px;padding-bottom:20px;padding-left:20px\">\n<figure data-spectra-id=\"spectra-43ccaea0-3ff6-4861-88ec-b671bd1a9f9e\" class=\"wp-block-image size-full is-resized\" ><img decoding=\"async\" src=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/11\/ll-mi-inne.svg\" alt=\"\" class=\"wp-image-6293\" style=\"width:44px;height:44px\"\/><\/figure>\n\n\n\n<div class=\"wp-block-group wp-container-content-ceb7f5b3 is-vertical is-content-justification-stretch is-layout-flex wp-container-core-group-is-layout-7c2834e4 wp-block-group-is-layout-flex\" style=\"padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px\">\n<h3 class=\"wp-block-heading has-text-color\" style=\"color:#071E3D;margin-top:0;margin-bottom:0;font-size:16px;font-weight:600;line-height:1.4\">Something is wrong, but I don&#8217;t know what<\/h3>\n\n\n\n<p class=\"ll-bez-tel has-text-color wp-block-paragraph\" style=\"color:#4A5A6A;margin-top:10px;margin-bottom:0;font-size:13px;line-height:1.45\">You don&#8217;t need to know what the event is called. The tool asks, step by step, what happened, when it was detected, whose data is involved and whether you are covered by the KSC Act.<\/p>\n\n\n\n<p class=\"ll-klik-wiersz wp-block-paragraph\" style=\"margin-top:auto;margin-bottom:0;padding-top:10px;font-size:14px;font-weight:600;line-height:1.5\"><a class=\"ll-klik-cel\" href=\"https:\/\/www.lablogic.pl\/i\/en-wiedza#other\">Start with the questions<\/a><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n<h2 id=\"dlaczego\" class=\"wp-block-heading\">Why this question arises at all<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Most organizations have an incident response procedure, and most of those procedures describe the technical path. They say who takes the report, how to classify it, when to escalate. The question &#8220;what next&#8221; comes up at a different moment \u2014 once the event is confirmed, part of the systems is down, and several people are waiting for a decision at the same time. The procedure then says who is to do something, but rarely says in what order, and what not to do.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second source of doubt is regulatory. The same event can trigger obligations under two or three regimes at once, and each of them counts time from something different. An essential or important entity within the meaning of the Polish KSC Act (Act on the National Cybersecurity System) responds to a significant incident from the moment it is detected. A controller within the meaning of the GDPR responds to a personal data breach from the moment it becomes aware of it. According to the EDPB the controller becomes aware when it has a reasonable degree of certainty that a security incident has led to personal data being compromised (Guidelines 9\/2022, paragraph 31). Those two moments may fall in the same hour, but for events spread over time they can be days apart.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The third source is the most practical. The first hours decide what the organization will have available later. Traces in systems have limited durability. Logs rotate, volatile memory disappears after a restart, virtual machine snapshots are overwritten. A team that instinctively restores the service is acting rationally from a continuity perspective \u2014 and is at the same time destroying the material on which the assessment of the event&#8217;s scope, the content of the report to the authority and the conversation with the insurer were meant to rest.<\/p>\n\n\n\n<h2 id=\"co-ustalic\" class=\"wp-block-heading\">What must be determined before the decision<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Is the event confirmed and what exactly did it cover<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A signal is not yet an incident. According to the Minister of Digital Affairs, the moment of detection is the identification of the event as an incident, not the moment it occurred (Q&amp;A 6.5). The Minister also points out that the entity may obtain the information about the event from a service provider. Before the organization launches a full response, someone has to confirm that the event actually happened and provisionally establish its scope. That means which systems, which data, which period, whether access is still ongoing. The verification should be short and documented to the hour, because the rest of the chronology is counted from it. The Minister links the moment of detection to the moment at which the entity can establish that the event is an incident (Q&amp;A 6.5). Prolonging the verification should therefore not move that moment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Scope is established along three dimensions at once. These are what stopped working, what was changed and what may have been disclosed. The third dimension tends to be examined last. Any of the three, however, can decide the obligations towards the data protection authority. A personal data breach is a breach of security leading to unauthorised disclosure of or access to the data, but also to their accidental or unlawful destruction, loss or alteration (Article 4(12) GDPR). The EDPB states that the controller should not wait for a detailed forensic examination and (early) mitigation steps before assessing the risk (Guidelines 01\/2021, paragraph 9). If a personal data breach cannot be ruled out, assume for working purposes that it may have occurred. Both tracks then run in parallel, because narrowing the findings is easier than making up lost time.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Who runs the case and who takes which decisions<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In an effective response three roles are separated. Someone runs the case and keeps the chronology. Someone decides on technical action \u2014 cutting off a network segment, disabling an account, holding back a restore. Someone prepares the legal qualification and the reports. On the GDPR side the data protection officer advises, while the decision to notify is taken and signed by a person representing the controller. On the cybersecurity side this role belongs to the person responsible for obligations under the KSC Act.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">These roles can be combined in a smaller organization, but they have to be named before the event. Under the KSC Act, responsibility for performing the obligations relating to incident handling and reporting rests with the head of the entity and does not disappear by delegating tasks to someone else \u2014 the Act provides for a separate financial penalty for the head of the entity, among other things for failing to perform the obligations relating to incident reporting and reporting duties. That penalty may first be imposed after 3 April 2028 (Article 35 of the amending act). The deferral does not change the notification deadlines. A simple organizational conclusion follows. Senior management has to learn about a significant incident early enough for reporting decisions to be taken within the deadline, not after it has passed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which clocks are already running<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The deadlines have to be known in advance, because during the event there is no time to work them out.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>KSC Act \u2014 essential and important entities.<\/strong> The early warning of a significant incident is due without undue delay, no later than 24 hours from the moment of detection. The significant incident notification is due without undue delay, no later than 72 hours \u2014 <strong>also from the moment of detection, not from the early warning<\/strong>. This is the most common distortion in secondary sources and the most expensive one in practice, because it creates the illusion of three extra days.<\/li>\n\n\n\n<li><strong>KSC Act \u2014 reporting after the notification.<\/strong> An interim report is submitted only at the request of the competent CSIRT. The final report \u2014 no later than one month from the date of the notification. If incident handling has not been completed by then, the entity submits a progress report and files the final report within one month of completion. The channel is the S46 central ICT system.<\/li>\n\n\n\n<li><strong>GDPR \u2014 the controller.<\/strong> A breach is notified to the President of UODO without undue delay and, where feasible, no later than 72 hours after having become aware of it \u2014 unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. The standard is &#8220;without undue delay&#8221;; 72 hours is a limit, not an allowance to be used up. A notification made after that point is accompanied by reasons for the delay. Where the full set of information cannot be gathered, the rules allow it to be provided in phases.<\/li>\n\n\n\n<li><strong>GDPR \u2014 the processor.<\/strong> A processor that has become aware of a breach notifies the controller without undue delay. According to EDPB Guidelines 9\/2022 the controller in principle becomes aware of the breach at the moment the processor has informed it of the breach. The data processing agreement should therefore set a specific time and channel for notification, and how to count the deadline is described in <a href=\"https:\/\/www.lablogic.pl\/en\/how-to-count-72-hours-for-breach-notification\/\">How to count the 72 hours for notifying a personal data breach?<\/a>.<\/li>\n\n\n\n<li><strong>Sectoral and contractual commitments.<\/strong> Financial entities have separate deadlines under the DORA Regulation and the technical standards adopted under it, and many customer contracts contain their own information commitments, usually shorter than the statutory ones. Essential and important entities in the banking and financial market infrastructure sectors report major ICT-related incidents under DORA, not under the KSC Act (Article 8i(1) of the Act). The obligations under the GDPR and under contracts run in parallel with the deadlines under the KSC Act or DORA.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Two transitional rules change the addressee of notifications and the moment from which the deadlines bind the organization.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Who the report actually goes to.<\/strong> The Act directs reports to the competent sectoral CSIRT, but the transitional provisions state that, until a communication is issued confirming that this CSIRT has reached operational capability, reports go to the competent CSIRT MON, CSIRT NASK or CSIRT GOV. The competent authorities have eighteen months from the entry into force of the amendment to establish the sectoral CSIRTs. Until such a communication is issued for a sector, the addressee is a national-level CSIRT. The exception is sectors in which a sectoral cybersecurity team was established before 2025 (Article 44(3) of the amending act). Such a team became the sectoral CSIRT on the entry into force of the amendment (Article 46 of the amending act) and is the addressee. Check which of these states your procedure reflects. Notifications are submitted through the S46 system (Article 11(2) of the Act). According to the Minister of Digital Affairs, the system routes them to the competent CSIRT and the teams forward notifications to one another according to competence (Q&amp;A 6.13 and 7.2).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>From when the reporting deadlines bind the organization.<\/strong> Entities that met the criteria for an essential or important entity on 3 April 2026 have until 3 April 2027 to implement the obligations under Chapter 3 of the Act (Article 33(1) of the amending act). Those obligations include notification of significant incidents. An entity that meets the criteria later has 12 months from the day it meets them to implement those obligations (Article 16 of the Act). For former operators of essential services, the period for moving to the new rules on notifying significant incidents ended on 3 October 2026 (Article 33(4) of the amending act).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Separate rules apply to two groups. A trust service provider reports a significant incident within 24 hours of detection. An important entity that is a public entity is exempt from submitting the early warning and the reports \u2014 interim, progress and final.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An organization\u2019s qualification decides which of these clocks can apply to it at all. Whether any of them has started depends on the nature of the event. Organizations that do not have this settled in writing usually start by <a href=\"https:\/\/www.lablogic.pl\/en\/nis2-ksc\/\">establishing the scope of obligations under NIS2 and KSC<\/a> before merging the reporting paths into a single procedure.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When an event is a significant incident<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Classification is not an intuitive judgement. The thresholds for treating an incident as significant \u2014 by type of event in particular sectors and subsectors \u2014 are set by the Council of Ministers by regulation, taking into account the number of users affected by the disruption, the duration of the incident\u2019s impact on the service, the geographical reach and other sector-specific factors. Excluded from that delegation are entities for which the European Commission has set thresholds in Implementing Regulation 2024\/2690. Some entities in the digital infrastructure, ICT service management and digital providers sectors apply them directly. Until a new national regulation is issued, the thresholds in the Regulation of the Council of Ministers of 31 October 2018 apply, until 3 April 2027 at the latest (Article 32(1) of the amending act). It covers the sectors and subsectors of the former Annex 1 to the Act. An organization outside the scope of both the 2018 regulation and Regulation 2024\/2690 has no threshold in implementing provisions today. It assesses the event against the definition of a significant incident in the Act (Article 2(7)).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The practical conclusion is that the thresholds have to be written into the procedure <strong>before<\/strong> the event, stating which source applies to the organization. Working this out during the first day eats up time that is not there.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What to secure before restoration begins<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Limiting the effects and gathering evidence are not mutually exclusive, but they require an order. Before the environment is restored it is worth securing images of the affected systems and volatile memory, exporting logs from systems with short retention and saving the configuration in its pre-change state. Isolating a network segment is safer than switching a machine off, because it stops the attacker without erasing the state of the system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In parallel, a single chronology of the event is kept. The record of who established or changed what, and when, later forms the basis of the report, the settlement with the insurer and the answers to the authority&#8217;s questions. Reconstructing that timeline a week after the event, from the memory of several people, produces a result that cannot be defended.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Who else has to be told<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Beyond the authorities, the circle of those informed is set by the rules, by contractual relationships and by the actual impact of the event \u2014 in that order, because the first element tends to be overlooked.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The KSC Act imposes two information obligations on essential and important entities towards the users of their services. In the case of a significant cyber threat, the entity informs the users who may be affected about the preventive measures available to them; it informs them about the threat itself where doing so will not increase the level of risk to the security of the systems. In the case of a significant incident that has an adverse effect on the provision of services \u2014 it informs users about the incident. These are obligations, not communication decisions. Once their conditions are met, the question is \u201chow and when\u201d, not \u201cwhether\u201d.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Next come the contractual relationships. Where the organization is a processor, its first addressees are the controllers for whom it processes data \u2014 and it is they, not it, who decide whether to notify the authority. Notifying the data subjects is a separate decision. It arises where there is a high risk to their rights and freedoms and has to take place without undue delay (Article 34(1) GDPR). It is not required where the affected data were protected by measures such as encryption that render them unintelligible to unauthorised persons, where the controller has subsequently eliminated the likelihood of a high risk or where it would involve disproportionate effort (Article 34(3) GDPR). In the last case a public communication or a similar measure informing individuals equally effectively takes its place. How to assess the risk is described in <a href=\"https:\/\/www.lablogic.pl\/en\/does-every-data-breach-need-to-be-reported\/\">Does every data breach need to be reported?<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Internal communication requires the same discipline as external. A single source of information, one approved message and a clear statement of what is not yet known reduce the number of versions circulating around the organization \u2014 and it is those versions that most often end up outside it in a form nobody approved.<\/p>\n\n\n\n<h2 id=\"pierwsza-doba\" class=\"wp-block-heading\">The first day \u2014 a checklist<\/h2>\n\n\n\n<div class=\"wp-block-group ll-art-check is-layout-constrained wp-block-group-is-layout-constrained\">\n<h3 class=\"wp-block-heading\">Hours 0\u20134<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Confirm the event and record the date and time at which it was identified as an incident.<\/li>\n\n\n\n<li>Appoint the person running the case and start a single, shared chronology.<\/li>\n\n\n\n<li>Secure logs, system images and volatile memory before any restoration.<\/li>\n\n\n\n<li>Stop the spread. Isolate the segment, withdraw access, force a change of credentials.<\/li>\n\n\n\n<li>Establish the preliminary scope. This means the systems, the categories of data, the period and the estimated number of people whose data may have been affected.<\/li>\n\n\n\n<li>Check which regimes apply to the organization and enter into the chronology the hours at which the deadlines expire. The deadlines for the early warning (24 h) and the significant incident notification (72 h) run from detection of the incident, not one from the other. The 72 h GDPR deadline runs from becoming aware of the breach.<\/li>\n\n\n\n<li>Inform senior management to the extent needed to take decisions on reporting.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">The first day<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Notify suppliers and the controllers towards whom the organization has contractual or statutory obligations.<\/li>\n\n\n\n<li>Prepare and send the early warning if the event is a significant incident \u2014 to the CSIRT competent today, not the target one.<\/li>\n\n\n\n<li>Decide whether a duty to inform the users of the services has arisen, and prepare the wording of the message.<\/li>\n\n\n\n<li>Carry out the risk assessment for individuals and decide whether to notify the President of UODO or not \u2014 together with the reasoning.<\/li>\n\n\n\n<li>Decide whether to communicate the breach to the data subjects. Where the risk is high, the communication is sent without undue delay unless an exception under Article 34(3) GDPR applies.<\/li>\n\n\n\n<li>Record the breach in the breach documentation regardless of whether it was notified.<\/li>\n<\/ul>\n<\/div>\n\n\n\n<div class=\"wp-block-group ll-art-zdanie is-layout-constrained wp-block-group-is-layout-constrained\">\n\n<p class=\"wp-block-paragraph\">Remember<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The sequence only has value once a specific role \u2014 not a department \u2014 has been assigned to each point before the event.<\/p>\n\n<\/div>\n\n\n\n<h2 id=\"bledy\" class=\"wp-block-heading\">Most common mistakes<\/h2>\n\n\n\n<ul class=\"wp-block-list ll-art-errors\">\n<li><strong>Restoring the service before securing the evidence.<\/strong> The most common mistake and the hardest to repair. After a restore from backup it is usually no longer possible to establish how long access lasted or what was taken.<\/li>\n\n\n\n<li><strong>Adding 72 hours to the early warning.<\/strong> Both KSC deadlines run from detection of the incident. A procedure under which the notification is to be made \u201cwithin 72 hours of the early warning\u201d plans to miss the deadline.<\/li>\n\n\n\n<li><strong>One field for the date of detection of the incident and of becoming aware of the breach.<\/strong> These are two separate findings. One concerns the impact on the service, the other the exposure of data. They may fall at the same moment \u2014 but with a single field the documentation cannot show when and on what basis the controller became aware of the breach.<\/li>\n\n\n\n<li><strong>Writing the target addressee of reports into the procedure.<\/strong> Sectoral CSIRTs are only being set up. Until the communication on the operational capability of the competent sectoral CSIRT, notifications go to CSIRT MON, NASK or GOV. The exception is a sector in which a sectoral cybersecurity team was established before 2025. There the addressee is already the sectoral CSIRT.<\/li>\n\n\n\n<li><strong>Assuming that a report to the CSIRT exhausts the obligations.<\/strong> Reports under different regimes have different addressees, different scope and different deadlines. None of them replaces the others. Nor do they replace the duty to inform the users of the services. In the banking and financial market infrastructure sectors the DORA report takes the place of the notification under the KSC Act, but not of the notification to the President of UODO (Article 8i(1) of the KSC Act, Article 33(1) GDPR).<\/li>\n\n\n\n<li><strong>Treating loss of availability as a purely technical matter.<\/strong> Loss of access to personal data caused by a security incident is a personal data breach just as much as its disclosure, even if the backup worked.<\/li>\n\n\n\n<li><strong>Scattered communication.<\/strong> Parallel messages from IT, customer service and the board, differing in content, create a bigger problem later than the event itself.<\/li>\n\n\n\n<li><strong>Closing the case once the service is back.<\/strong> Without the final report, the conclusions and changes to safeguards, the organization returns to exactly the state in which the incident was possible.<\/li>\n<\/ul>\n\n\n\n<h2 id=\"wnioski\" class=\"wp-block-heading\">Conclusions and next steps<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After detecting an incident an organization takes not one decision but a sequence of decisions with different owners and different deadlines. Speed only helps where the order is right. That order is confirmation, securing the evidence and limiting the effects. Legal qualification and notifications run in parallel. Then come information for users, restoration and conclusions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Five things are worth settling before the next event. Who has the right to declare an incident confirmed, and where that moment is recorded. What the minimum set of evidence secured every time looks like, regardless of the type of event. Which classification thresholds apply to the organization and where they come from. Which regimes apply to it, who prepares the report under each of them and to whom it is addressed. Who approves messages going outside.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An organization that has these elements settled spends the first hours on substantive work. An organization that does not spends them working out who is responsible for what \u2014 and it is usually that, rather than the scale of the event itself, that decides how the matter looks later in the documents.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Related materials<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/does-every-data-breach-need-to-be-reported\/\">Does every data breach need to be reported?<\/a><\/strong> \u2014 the notification threshold and the assessment of risk to the rights and freedoms of individuals, that is, the decision to which the first-day sequence leads.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/cybersecurity-incident-vs-personal-data-breach\/\">Cybersecurity incident vs personal data breach: what is the difference?<\/a><\/strong> \u2014 two qualifications of one event and two starting points for the deadlines.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/does-every-organization-fall-under-nis2\/\">Does every organization fall under NIS2?<\/a><\/strong> \u2014 the entity qualification that decides whether, alongside the GDPR obligations, deadlines towards the CSIRT are also running.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/where-should-the-board-begin-preparing-for-nis2\/\">Where should the board begin preparing for NIS2?<\/a><\/strong> \u2014 the order of senior management actions once the entity&#8217;s status is established, including assigning responsibility for incident handling.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/what-should-a-personal-data-breach-register-contain\/\">What should a personal data breach register contain?<\/a><\/strong> \u2014 what of the first 24 hours ends up in the documentation.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/who-needs-nis2-training-besides-the-board\/\">Who else needs NIS2 training besides the management board?<\/a><\/strong> \u2014 the circle of people beyond the head of the entity and how to derive it from Articles 8 and 11.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/what-does-a-significant-incident-report-to-a-csirt-contain\/\">What does a significant incident report to a CSIRT contain?<\/a><\/strong> \u2014 the four submissions to a CSIRT, their deadlines and the content the Act requires<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/how-to-count-72-hours-for-breach-notification\/\">How to count the 72 hours for notifying a personal data breach?<\/a><\/strong> \u2014 when the controller&#8217;s deadline starts and how to count it on days off work.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/how-to-notify-data-subjects-of-a-breach\/\">How do you notify data subjects of a breach and what must the communication contain?<\/a><\/strong> \u2014 the content and channel of the communication to data subjects when the risk assessment indicates a high risk.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/processor-breach-notification-to-the-controller\/\">How and when must a processor notify a personal data breach to the controller?<\/a><\/strong> \u2014 the deadline and content of the notification when the organisation is a processor.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/incident-response-exercise\/\">How to prepare an incident response exercise?<\/a><\/strong> \u2014 preparing an exercise that tests this sequence before a real event.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n\n<ul class=\"wp-block-list ll-art-sources\">\n<li>Regulation (EU) 2016\/679 of the European Parliament and of the Council (GDPR), Articles 4(12), 33 and 34, consolidated text \u2014 EUR-Lex: <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/PDF\/?uri=CELEX:02016R0679-20160504\" target=\"_blank\" rel=\"noreferrer noopener\">eur-lex.europa.eu<\/a><\/li>\n\n\n\n<li>Act of July 5, 2018 on the National Cybersecurity System, Article 2(7), Articles 8i, 11\u201312c and 16, consolidated text \u2014 Chancellery of the Sejm, ISAP: <a href=\"https:\/\/isap.sejm.gov.pl\/isap.nsf\/DocDetails.xsp?id=WDU20180001560\" target=\"_blank\" rel=\"noreferrer noopener\">isap.sejm.gov.pl<\/a> (in Polish)<\/li>\n\n\n\n<li>Act of January 23, 2026 amending the Act on the National Cybersecurity System and certain other acts (Journal of Laws 2026, item 252), Articles 32, 33, 35, 42, 44 and 46 \u2014 transitional provisions on incident reporting, Journal of Laws: <a href=\"https:\/\/dziennikustaw.gov.pl\/D2026000025201.pdf\" target=\"_blank\" rel=\"noreferrer noopener\">dziennikustaw.gov.pl<\/a> (in Polish)<\/li>\n\n\n\n<li>Regulation of the Council of Ministers of October 31, 2018 on the thresholds for recognising an incident as significant (Journal of Laws 2018, item 2180) \u2014 Chancellery of the Sejm, ISAP: <a href=\"https:\/\/isap.sejm.gov.pl\/isap.nsf\/DocDetails.xsp?id=WDU20180002180\" target=\"_blank\" rel=\"noreferrer noopener\">isap.sejm.gov.pl<\/a> (in Polish)<\/li>\n\n\n\n<li>Commission Implementing Regulation (EU) 2024\/2690 of October 17, 2024 \u2014 EUR-Lex: <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX:32024R2690\" target=\"_blank\" rel=\"noreferrer noopener\">eur-lex.europa.eu<\/a><\/li>\n\n\n\n<li>Reporting a personal data breach \u2014 Personal Data Protection Office (UODO): <a href=\"https:\/\/uodo.gov.pl\/pl\/492\/2278\" target=\"_blank\" rel=\"noreferrer noopener\">uodo.gov.pl<\/a> (in Polish)<\/li>\n\n\n\n<li>What is the deadline for notifying a breach to the President of UODO? \u2014 Personal Data Protection Office (UODO): <a href=\"https:\/\/uodo.gov.pl\/pl\/525\/2584\" target=\"_blank\" rel=\"noreferrer noopener\">uodo.gov.pl<\/a> (in Polish)<\/li>\n\n\n\n<li>Questions and answers on the amendment to the Act on the National Cybersecurity System, October 2026 version, Q&amp;A 6.5, 6.13 and 7.2 \u2014 Ministry of Digital Affairs: <a href=\"https:\/\/cyber.gov.pl\/assets\/pdf\/faq-ksc.pdf\" target=\"_blank\" rel=\"noreferrer noopener\">cyber.gov.pl<\/a> (in Polish)<\/li>\n\n\n\n<li>Guidelines 9\/2022 on personal data breach notification under GDPR, version 2.0, adopted March 28, 2023, paragraphs 31 and 44 \u2014 European Data Protection Board: <a href=\"https:\/\/www.edpb.europa.eu\/system\/files\/documents\/2023-04\/edpb_guidelines_202209_personal_data_breach_notification_v2.0_en.pdf\" target=\"_blank\" rel=\"noreferrer noopener\">edpb.europa.eu<\/a><\/li>\n\n\n\n<li>Guidelines 01\/2021 on examples regarding personal data breach notification, version 2.0, adopted December 14, 2021, paragraph 9 \u2014 European Data Protection Board: <a href=\"https:\/\/www.edpb.europa.eu\/our-work-tools\/our-documents\/guidelines\/guidelines-012021-examples-regarding-personal-data-breach_en\" target=\"_blank\" rel=\"noreferrer noopener\">edpb.europa.eu<\/a><\/li>\n<\/ul>\n\n\n\n<div class=\"wp-block-group ll-art-cta is-layout-constrained wp-block-group-is-layout-constrained\">\n<h2 class=\"wp-block-heading ll-nietoc\">Settle the order of actions before you need it<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If incident response in your organization currently rests on the experience of a few people and on decisions taken in the middle of the event, it is worth putting that process in order calmly. Support with incidents and breaches covers assessment of the situation, decisions on reporting, communication and remedial action.<\/p>\n\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/www.lablogic.pl\/en\/incident-response\/\">Support with incidents and breaches<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>First confirm the event and secure the evidence, then limit the effects, and run the legal assessment in parallel from the first hours. Detection starts several independent clocks, depending on the entity\u2019s status and whether personal data are affected. In technical work the order of steps matters more than speed.<\/p>\n","protected":false},"author":2,"featured_media":5571,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ll_stan_prawny":"November 2026","footnotes":""},"categories":[71],"tags":[],"class_list":["post-3999","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-incidents"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"After detecting an incident the order matters. Confirmation, securing evidence, the deadlines already running, reports. See the first-day sequence.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Micha\u0142 Rutkowski\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"LabLogic - Micha\u0142 Rutkowski | DPO, GDPR, NIS2 and cybersecurity in practice\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"The first day after an incident\" \/>\n\t\t<meta property=\"og:description\" content=\"The order of steps decides whether you meet the deadlines.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t\t<meta property=\"article:section\" content=\"Incidents and Breaches\" \/>\n\t\t<meta property=\"article:tag\" content=\"incidents\" \/>\n\t\t<meta property=\"article:tag\" content=\"breaches\" \/>\n\t\t<meta property=\"article:tag\" content=\"deadlines\" \/>\n\t\t<meta property=\"article:tag\" content=\"compliance\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-07-14T07:05:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-11-14T14:25:54+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"The first day after an incident\" \/>\n\t\t<meta name=\"twitter:description\" content=\"The order of steps decides whether you meet the deadlines.\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#article\",\"name\":\"What to do after detecting an incident \\u2014 the first hours\",\"headline\":\"What to do after detecting an incident?\",\"author\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\"},\"publisher\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#organization\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg\",\"width\":1200,\"height\":630,\"caption\":\"What to do after detecting an incident? \\u2014 LabLogic article graphic by Micha\\u0142 Rutkowski\"},\"datePublished\":\"2026-07-14T09:05:00+02:00\",\"dateModified\":\"2026-11-14T15:25:54+01:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#webpage\"},\"articleSection\":\"Incidents and Breaches\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#listItem\",\"position\":1,\"name\":\"LabLogic\",\"item\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/baza-wiedzy\\\/incidents\\\/#listItem\",\"name\":\"Incidents and Breaches\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/baza-wiedzy\\\/incidents\\\/#listItem\",\"position\":2,\"name\":\"Incidents and Breaches\",\"item\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/baza-wiedzy\\\/incidents\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#listItem\",\"name\":\"What to do after detecting an incident?\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#listItem\",\"name\":\"LabLogic\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#listItem\",\"position\":3,\"name\":\"What to do after detecting an incident?\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/baza-wiedzy\\\/incidents\\\/#listItem\",\"name\":\"Incidents and Breaches\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#organization\",\"name\":\"LabLogic\",\"description\":\"LabLogic is the advisory practice of Micha\\u0142 Rutkowski, based in Gdynia, Poland. It acts as an external data protection officer and supports NIS2 and Polish KSC Act implementation, incident and breach response, and AI Act readiness for medium and large organisations, on site in the Tricity area and remotely across Poland.\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/\",\"email\":\"m.rutkowski@lablogic.pl\",\"foundingDate\":\"2004\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/cropped-lablogic-site-icon-512.png\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#organizationLogo\",\"width\":512,\"height\":512},\"image\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#organizationLogo\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/michal-rutkowski-iod\"],\"additionalType\":\"https:\\\/\\\/schema.org\\\/ProfessionalService\",\"legalName\":\"LabLogic Consulting Micha\\u0142 Rutkowski\",\"address\":{\"@type\":\"PostalAddress\",\"streetAddress\":\"ul. Wolno\\u015bci 15\",\"postalCode\":\"81-327\",\"addressLocality\":\"Gdynia\",\"addressRegion\":\"pomorskie\",\"addressCountry\":\"PL\"},\"vatID\":\"PL9580972114\",\"taxID\":\"9580972114\",\"areaServed\":{\"@type\":\"Country\",\"name\":\"Poland\"},\"knowsAbout\":[\"GDPR\",\"Data Protection Officer (DPO)\",\"NIS2 Directive\",\"Polish National Cybersecurity System Act (KSC)\",\"Cybersecurity incident and data breach response\",\"EU AI Act\",\"ISO\\\/IEC 27001\",\"Information security management\"],\"founder\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\"},\"hasOfferCatalog\":{\"@type\":\"OfferCatalog\",\"name\":\"Services\",\"itemListElement\":[{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"External Data Protection Officer (DPO)\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/external-dpo\\\/\"}},{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"NIS2 and KSC implementation support\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/nis2-ksc\\\/\"}},{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"Incident and data breach response\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/incident-response\\\/\"}},{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"GDPR and NIS2 training\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/training\\\/\"}},{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"AI Act: roles, obligations and preparation\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/ai-act\\\/\"}}]}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/michal-rutkowski\\\/\",\"name\":\"Micha\\u0142 Rutkowski\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski-portret\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/michal-rutkowski-iod-dpo-rodo-nis2-lablogic.webp\",\"width\":864,\"height\":1080,\"caption\":\"Micha\\u0142 Rutkowski\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/michal-rutkowski-iod\"],\"jobTitle\":\"Data Protection Officer (DPO), NIS2\\\/KSC and cybersecurity advisor\",\"description\":\"Data protection and cybersecurity practitioner, owner of LabLogic. Since 2004 he has supported medium and large organisations: audits, implementations, incidents and training.\",\"email\":\"m.rutkowski@lablogic.pl\",\"knowsAbout\":[\"GDPR\",\"Data Protection Officer (DPO)\",\"NIS2 Directive\",\"Polish National Cybersecurity System Act (KSC)\",\"Cybersecurity incident and data breach response\",\"EU AI Act\",\"ISO\\\/IEC 27001\",\"Information security management\"],\"worksFor\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#webpage\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/\",\"name\":\"What to do after detecting an incident \\u2014 the first hours\",\"description\":\"After detecting an incident the order matters. Confirmation, securing evidence, the deadlines already running, reports. See the first-day sequence.\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\"},\"creator\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#mainImage\",\"width\":1200,\"height\":630,\"caption\":\"What to do after detecting an incident? \\u2014 LabLogic article graphic by Micha\\u0142 Rutkowski\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/what-to-do-after-detecting-an-incident\\\/#mainImage\"},\"datePublished\":\"2026-07-14T09:05:00+02:00\",\"dateModified\":\"2026-11-14T15:25:54+01:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/\",\"name\":\"Micha\\u0142 Rutkowski - LabLogic\",\"alternateName\":\"LabLogic\",\"description\":\"DPO, GDPR, NIS2 and cybersecurity in practice\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"What to do after detecting an incident \u2014 the first hours","description":"After detecting an incident the order matters. Confirmation, securing evidence, the deadlines already running, reports. See the first-day sequence.","canonical_url":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#article","name":"What to do after detecting an incident \u2014 the first hours","headline":"What to do after detecting an incident?","author":{"@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski"},"publisher":{"@id":"https:\/\/www.lablogic.pl\/#organization"},"image":{"@type":"ImageObject","url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg","width":1200,"height":630,"caption":"What to do after detecting an incident? \u2014 LabLogic article graphic by Micha\u0142 Rutkowski"},"datePublished":"2026-07-14T09:05:00+02:00","dateModified":"2026-11-14T15:25:54+01:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#webpage"},"isPartOf":{"@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#webpage"},"articleSection":"Incidents and Breaches"},{"@type":"BreadcrumbList","@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/#listItem","position":1,"name":"LabLogic","item":"https:\/\/www.lablogic.pl\/en\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/baza-wiedzy\/incidents\/#listItem","name":"Incidents and Breaches"}},{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/baza-wiedzy\/incidents\/#listItem","position":2,"name":"Incidents and Breaches","item":"https:\/\/www.lablogic.pl\/en\/baza-wiedzy\/incidents\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#listItem","name":"What to do after detecting an incident?"},"previousItem":{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/#listItem","name":"LabLogic"}},{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#listItem","position":3,"name":"What to do after detecting an incident?","previousItem":{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/baza-wiedzy\/incidents\/#listItem","name":"Incidents and Breaches"}}]},{"@type":"Organization","@id":"https:\/\/www.lablogic.pl\/#organization","name":"LabLogic","description":"LabLogic is the advisory practice of Micha\u0142 Rutkowski, based in Gdynia, Poland. It acts as an external data protection officer and supports NIS2 and Polish KSC Act implementation, incident and breach response, and AI Act readiness for medium and large organisations, on site in the Tricity area and remotely across Poland.","url":"https:\/\/www.lablogic.pl\/en\/","email":"m.rutkowski@lablogic.pl","foundingDate":"2004","logo":{"@type":"ImageObject","url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/08\/cropped-lablogic-site-icon-512.png","@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#organizationLogo","width":512,"height":512},"image":{"@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#organizationLogo"},"sameAs":["https:\/\/www.linkedin.com\/in\/michal-rutkowski-iod"],"additionalType":"https:\/\/schema.org\/ProfessionalService","legalName":"LabLogic Consulting Micha\u0142 Rutkowski","address":{"@type":"PostalAddress","streetAddress":"ul. Wolno\u015bci 15","postalCode":"81-327","addressLocality":"Gdynia","addressRegion":"pomorskie","addressCountry":"PL"},"vatID":"PL9580972114","taxID":"9580972114","areaServed":{"@type":"Country","name":"Poland"},"knowsAbout":["GDPR","Data Protection Officer (DPO)","NIS2 Directive","Polish National Cybersecurity System Act (KSC)","Cybersecurity incident and data breach response","EU AI Act","ISO\/IEC 27001","Information security management"],"founder":{"@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski"},"hasOfferCatalog":{"@type":"OfferCatalog","name":"Services","itemListElement":[{"@type":"Offer","itemOffered":{"@type":"Service","name":"External Data Protection Officer (DPO)","url":"https:\/\/www.lablogic.pl\/en\/external-dpo\/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"NIS2 and KSC implementation support","url":"https:\/\/www.lablogic.pl\/en\/nis2-ksc\/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Incident and data breach response","url":"https:\/\/www.lablogic.pl\/en\/incident-response\/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"GDPR and NIS2 training","url":"https:\/\/www.lablogic.pl\/en\/training\/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"AI Act: roles, obligations and preparation","url":"https:\/\/www.lablogic.pl\/en\/ai-act\/"}}]}},{"@type":"Person","@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski","url":"https:\/\/www.lablogic.pl\/michal-rutkowski\/","name":"Micha\u0142 Rutkowski","image":{"@type":"ImageObject","@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski-portret","url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/08\/michal-rutkowski-iod-dpo-rodo-nis2-lablogic.webp","width":864,"height":1080,"caption":"Micha\u0142 Rutkowski"},"sameAs":["https:\/\/www.linkedin.com\/in\/michal-rutkowski-iod"],"jobTitle":"Data Protection Officer (DPO), NIS2\/KSC and cybersecurity advisor","description":"Data protection and cybersecurity practitioner, owner of LabLogic. Since 2004 he has supported medium and large organisations: audits, implementations, incidents and training.","email":"m.rutkowski@lablogic.pl","knowsAbout":["GDPR","Data Protection Officer (DPO)","NIS2 Directive","Polish National Cybersecurity System Act (KSC)","Cybersecurity incident and data breach response","EU AI Act","ISO\/IEC 27001","Information security management"],"worksFor":{"@id":"https:\/\/www.lablogic.pl\/#organization"}},{"@type":"WebPage","@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#webpage","url":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/","name":"What to do after detecting an incident \u2014 the first hours","description":"After detecting an incident the order matters. Confirmation, securing evidence, the deadlines already running, reports. See the first-day sequence.","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/www.lablogic.pl\/en\/#website"},"breadcrumb":{"@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#breadcrumblist"},"author":{"@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski"},"creator":{"@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski"},"image":{"@type":"ImageObject","url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg","@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#mainImage","width":1200,"height":630,"caption":"What to do after detecting an incident? \u2014 LabLogic article graphic by Micha\u0142 Rutkowski"},"primaryImageOfPage":{"@id":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/#mainImage"},"datePublished":"2026-07-14T09:05:00+02:00","dateModified":"2026-11-14T15:25:54+01:00"},{"@type":"WebSite","@id":"https:\/\/www.lablogic.pl\/en\/#website","url":"https:\/\/www.lablogic.pl\/en\/","name":"Micha\u0142 Rutkowski - LabLogic","alternateName":"LabLogic","description":"DPO, GDPR, NIS2 and cybersecurity in practice","inLanguage":"en-US","publisher":{"@id":"https:\/\/www.lablogic.pl\/#organization"}}]},"og:locale":"en_US","og:site_name":"LabLogic - Micha\u0142 Rutkowski | DPO, GDPR, NIS2 and cybersecurity in practice","og:type":"article","og:title":"The first day after an incident","og:description":"The order of steps decides whether you meet the deadlines.","og:url":"https:\/\/www.lablogic.pl\/en\/what-to-do-after-detecting-an-incident\/","og:image":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg","og:image:secure_url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg","og:image:width":1200,"og:image:height":630,"article:section":"Incidents and Breaches","article:tag":["incidents","breaches","deadlines","compliance"],"article:published_time":"2026-07-14T07:05:00+00:00","article:modified_time":"2026-11-14T14:25:54+00:00","twitter:card":"summary_large_image","twitter:title":"The first day after an incident","twitter:description":"The order of steps decides whether you meet the deadlines.","twitter:image":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg"},"aioseo_meta_data":{"post_id":"3999","title":"What to do after detecting an incident \u2014 the first hours","description":"After detecting an incident the order matters. Confirmation, securing evidence, the deadlines already running, reports. See the first-day sequence.","keywords":null,"keyphrases":{"focus":{"keyphrase":"what to do after detecting an incident","score":69},"additional":[{"keyphrase":"security incident response","score":69},{"keyphrase":"reporting a significant incident to CSIRT","score":69},{"keyphrase":"first day after an incident","score":78},{"keyphrase":"incident reporting deadline","score":69}]},"primary_term":null,"canonical_url":null,"og_title":"The first day after an incident","og_description":"The order of steps decides whether you meet the deadlines.","og_object_type":"article","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":"","og_custom_url":null,"og_article_section":"Incidents and Breaches","og_article_tags":[{"label":"incidents","value":"incidents"},{"label":"breaches","value":"breaches"},{"label":"deadlines","value":"deadlines"},{"label":"compliance","value":"compliance"}],"twitter_use_og":true,"twitter_card":"summary_large_image","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"Article","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":"-1","robots_max_videopreview":"-1","robots_max_imagepreview":"large","priority":0,"frequency":"default","local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":{"faqs":[],"keyPoints":[],"schemas":[],"titles":[],"descriptions":[],"socialPosts":{"email":{"subject":"","preview":"","content":""},"linkedin":[],"twitter":[],"facebook":[],"instagram":[]}},"created":"2026-08-18 22:31:50","updated":"2026-11-14 14:26:54","seo_analyzer_scan_date":null,"focus_keyword":"what to do after detecting an incident","additional_keywords":[{"word":"security incident response","score":69,"items":{"introductionKeyword":{"score":3},"keyphraseLength":{"score":9},"keyphraseDensity":{"score":4},"functionWordsInKeyphrase":{"score":9},"textCompetingLinks":{"score":9},"imageKeyphrase":{"score":3}}},{"word":"reporting a significant incident to CSIRT","score":69,"items":{"introductionKeyword":{"score":3},"keyphraseLength":{"score":9},"keyphraseDensity":{"score":4},"functionWordsInKeyphrase":{"score":9},"textCompetingLinks":{"score":9},"imageKeyphrase":{"score":3}}},{"word":"first day after an incident","score":78,"items":{"introductionKeyword":{"score":3},"keyphraseLength":{"score":9},"keyphraseDensity":{"score":9},"functionWordsInKeyphrase":{"score":9},"textCompetingLinks":{"score":9},"imageKeyphrase":{"score":3}}},{"word":"incident reporting deadline","score":69,"items":{"introductionKeyword":{"score":3},"keyphraseLength":{"score":9},"keyphraseDensity":{"score":4},"functionWordsInKeyphrase":{"score":9},"textCompetingLinks":{"score":9},"imageKeyphrase":{"score":3}}}],"truseo_locale":null},"spectra_blocks_featured_image_url":{"thumbnail":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1-150x150.jpg","width":150,"height":150},"medium":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1-300x158.jpg","width":300,"height":158},"medium_large":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1-768x403.jpg","width":768,"height":403},"large":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1-1024x538.jpg","width":1024,"height":538},"full":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-what-to-do-after-detecting-an-incident-en-1.jpg","width":1200,"height":630}},"spectra_blocks_author_info":{"display_name":"Micha\u0142 Rutkowski","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/29f5af5a0ce65a4307813722032192bdf08e740cbda98b61aa73b548422ff768?s=96&d=mm&r=g","author_link":"https:\/\/www.lablogic.pl\/en\/author\/michal-rutkowski\/","description":"Micha\u0142 Rutkowski \u2014 praktyk ochrony danych i cyberbezpiecze\u0144stwa, w\u0142a\u015bciciel LabLogic. Od 2004 roku pracuje na styku technologii, ochrony danych i zarz\u0105dzania ryzykiem. Pe\u0142ni funkcj\u0119 zewn\u0119trznego IOD\/DPO, prowadzi audyty RODO, kwalifikacj\u0119 i wdro\u017cenia NIS2 oraz ustawy o KSC, wspiera organizacje przy incydentach i naruszeniach ochrony danych, szkoli zarz\u0105dy, kadr\u0119 kierownicz\u0105 oraz zespo\u0142y IT i compliance. Pracuje ze \u015brednimi i du\u017cymi organizacjami, w tym z sektora finansowego i bran\u017c regulowanych."},"_links":{"self":[{"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts\/3999","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/comments?post=3999"}],"version-history":[{"count":12,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts\/3999\/revisions"}],"predecessor-version":[{"id":6389,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts\/3999\/revisions\/6389"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/media\/5571"}],"wp:attachment":[{"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/media?parent=3999"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/categories?post=3999"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/tags?post=3999"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}