What a protection plan is and where the deadlines come from
The critical infrastructure protection plan (known in Poland as POIK) is a document describing how a plant protects the elements on which the continuity of an essential service depends: facilities, installations, control systems, people and processes. It is not a list of safeguards bought once and forgotten. It describes risks, measures, responsibilities and evidence that the measures work.
The framework is set by the Polish act implementing the CER directive (Journal of Laws 2026, item 815). The deadlines run from the notice of entry in the register of critical entities: risk assessment within 9 months, implementation of measures within 3 months after the assessment, documentation within 15 months of entry. A significant incident must be reported within 24 hours of occurrence or detection, with a report within 30 days. The reporting path is described in Art. 6zv(1)(4): the competent authority and the Director of the Government Centre for Security (RCB), the Head of the Internal Security Agency (ABW) and the national-level CSIRT.
Protection plan versus resilience plan
The terminology can be confusing. The term POIK comes from the earlier legal regime for critical infrastructure, while the CER directive speaks of the resilience of a critical entity. In practice, a plant should maintain one coherent set of documents in which the protection plan and the resilience elements do not drift apart. Confirm the scope and name of the document in the text of the act and with the competent authority for your sector.
What a protection plan should contain
A good plan answers five questions: what are we protecting, against what, with which measures, who is responsible, and how do we know it works. Each question should have its own chapter in the document, with numbered requirements that can be referenced in an audit.
The requirement of Art. 6zt, worth treating as the backbone of the document, is to cover physical protection with access control and the personnel security of employees and external suppliers in one system. For that reason the plan cannot be a collection of three independent procedures: security, occupational health and safety (OHS), and cybersecurity.
- A description of the infrastructure and the essential service, including dependencies on suppliers and technical networks.
- The risk assessment result, with the method used, the scenarios and the justification for accepting residual risk.
- Physical protection measures: zones, access control, procedures for contractors and visitors.
- Personnel security measures: vetting, training, permissions, accountability.
- Measures for OT and IT systems, including segmentation and remote access management.
- An incident response plan with the 24-hour reporting path and the 30-day report.
- Business continuity and recovery rules for after an event.
- Roles, responsibilities and a schedule of reviews and exercises.
Deadlines after entry in the register (months from entry)
How to develop the plan step by step
The safest approach is to run the work as a project with three time gates matching the statutory deadlines. Below is a sequence that works in industrial plants, where part of the knowledge sits in operations, part in OHS and part in the IT and automation department.
Stage 1: risk assessment (within 9 months of entry)
Start with an inventory of the assets and processes of the essential service, then build scenarios of natural, technical and man-made threats and those arising from supplier dependencies. Make sure people from operations, security, OHS and OT take part in the assessment. An assessment prepared by a single department usually misses dependencies that only surface during an actual event.
Stage 2: implementing measures (3 months after the assessment)
The assessment yields a list of measures. Assign each one an owner, a deadline and evidence of completion. Three months is short, so schedule measures that require investment in a plan with justification, and launch organisational measures and procedures immediately.
Stage 3: documentation (15 months from entry)
Assemble the plan from the results of stages 1 and 2 and attach the evidence register and the review schedule. Check completeness by cross-checking: every risk has a measure, every measure has an owner, every owner has evidence of completion.
Approvals and sign-off
The plan must be agreed with the parties it concerns: the services responsible for protection and security, where needed the sector authorities, and internally the management that accepts the residual risk. Confirm the approval procedure, the addressees and the deadlines in the act and in the notices of the competent authority, because they depend on the sector.
A practical tip: prepare a working package for approval, not just the plan itself. The package contains the plan, a zone map, a list of external companies with their access scopes, a responsibility matrix and a list of evidence. The reviewer gets the full picture, and the plant reduces the number of rounds of questions.
Evidence for the audit
An audit does not assess a document but whether the described measures work. For that reason, collect evidence as you go, not a week before the inspection. Standards help structure the evidence: ISO 22301 for business continuity, ISO 27001:2022 for the information security management system and IEC 62443 for OT (zones, conduits, security levels SL 1–4). A certificate does not mean compliance with NIS2 or with the Polish act on critical entity resilience, but it provides a coherent evidence framework.
For an industrial plant, the strongest evidence is what is generated automatically: access control event logs, the training and permissions register, the history of work permits and an on-site presence list with event times.
- Plan versions with date, author, approver and a description of changes.
- Exercise reports with the list of participants and conclusions.
- A register of training and permissions for employees and external companies, with expiry dates.
- Access control records and the list of people present on site.
- An incident register with reporting times and reports.
How InnerWeb supports documentation
InnerWeb is a software producer whose products complement a plant's existing systems and supply evidence for audits. The audit trail records who changed a permit or permission, and when. The register of external companies and visitors is linked to QR gate control in the security panel, and the evacuation list shows who is on site at a given moment, with a printout for coordinators. Staff location from BLE beacons works without GPS and supports the assessment of who was in a zone.
These are tools that help meet the requirements, not a replacement for the plan. The plan and the risk decisions remain with the plant.
Checklist
Video
Frequently asked questions
When do the deadlines for the protection plan start?
From the notice of entry in the register of critical entities: risk assessment within 9 months, implementation of measures within 3 months after the assessment, documentation within 15 months of entry. The date of entry is confirmed by the authority's decision.
Does an ISO 27001 certificate replace the protection plan?
No. A certificate does not mean compliance with NIS2 or with the Polish act on critical entity resilience. Standards serve as evidence frameworks, while the plan must meet the requirements of the act for your entity.
Who should own the document?
One designated person with managerial authority, usually the protection officer, with a team of co-authors from operations, OHS, security and OT. The owner is responsible for keeping it current and for the reviews.
What evidence is strongest in an audit?
Evidence that is generated automatically and time-stamped: access control records, the training and permissions register, permit history, the presence list and exercise reports.
Sources
Let us talk about evidence for your protection plan
Using your plant as an example, we will show how the audit trail, the presence list and access control for external companies support protection documentation. Book a short call with the InnerWeb team.
Let's talk