Let’s talk
Wondering how this plays out in your organisation? Get in touch — I answer personally.
Short answer
The deadline depends on the day the organization met the conditions for being treated as an essential or an important entity. Entities that met them on 3 April 2026 had until 3 October 2026 to file the application under the schedule set by the Minister of Digital Affairs. Everyone else has six months from the day the conditions were met. An application filed after 3 October 2026 still leads to an entry (Article 7d(1)). Entities entered in the register ex officio do not file an application for entry, but supplement the data within six months of service of the request (Article 7b(2) and (4)). The application is filed by the head of the entity, or by a person they authorise, electronically and through the ICT system that maintains the register.
Why this question comes up at all
Entry in the register is often read as the moment an organization “enters” the scope of the Act on the National Cybersecurity System. That reading is the reverse of the legal position. The act applies once the conditions in Article 5 are met, and entry in the register is an administrative-technical act that is declaratory in nature (Article 7d(5)). The register discloses a status it does not itself create.
The practical consequence is uncomfortable.
Remember
An organization that has not filed the application is not outside the act because of it — every deadline for implementing its obligations is already running.
The reverse holds too. An entry does not establish that the classification was made correctly, because the data comes from the entity itself.
The second source of doubt is the pair of parallel deadline regimes. The act sets a standing rule of six months from the day the conditions are met (Article 7c(1)). Alongside it runs a transitional rule for entities that existed and met the conditions on the day the amendment entered into force. The second rule is not written into the KSC act itself, but into the amending act and a ministerial communication. Reading the consolidated text alone, it is easy to miss.
The third source is organisational. The application looks like a registration formality that can be handed to an administrative team. In reality it contains a declaration of the size of the entity, a sectoral classification and technical data. None of these can be completed without first determining what the organization is for the purposes of the act.
What has to be established before the decision
Which deadline binds the organization
The starting point is the date the conditions were met, not the date the obligation was discovered. Which side of 3 April 2026 that date falls on determines the whole schedule that follows.
| Situation of the entity | Deadline for filing the application | Legal basis |
|---|---|---|
| Met the conditions on 3 April 2026 | by 3 October 2026 (the deadline has passed; an application filed later still leads to an entry — Article 7d(1)) | Article 33(3) of the amending act and the communication of the Minister of Digital Affairs |
| Met the conditions after 3 April 2026 | 6 months from the day the conditions were met | Article 7c(1) of the KSC act |
| Entered ex officio | no application for entry is filed, the data is completed within 6 months of service of the request | Article 7b(2) and (4) |
| Designated by a decision of the authority | the data is completed within 6 months of service of the decision | Article 7l(3)(2) |
The ministry’s schedule opened filing on 7 May 2026. For entities that met the conditions on 3 April 2026, the deadline expired on 3 October 2026. The same deadline applied to essential entities and to important entities — the ministry did not split them into separate stages. The communication may be changed only where technical or organisational reasons make it impossible to make entries and start using the S46 system within the scheduled timeframe (Article 34(5) of the amending act). An application filed after 3 October 2026 still leads to an entry (Article 7d(1)). According to the Minister of Digital Affairs, an entity which ceased the activity covered by the act before its deadline expired does not have to file an application (Q&A 1.42).
The deadlines for implementing the substantive obligations run independently of the registration deadline. Entities that met the conditions on 3 April 2026 implement the obligations of Chapter 3 by 3 April 2027, and essential entities carry out their first audit by 3 April 2028. For entities that met the conditions later, the same periods are 12 and 24 months from the day the conditions were met (Article 16). According to the Minister of Digital Affairs, a former operator of essential services that carried out an audit before the amendment keeps its existing cycle (Article 25 of the amending act and Q&A 9.5). It carries out the next audit within three years of signing the report on its last audit.
Whether the entity has already been entered ex officio
This check comes first, because it settles which document the organization should be looking for at all. The minister responsible for computerisation enters four groups of entities ex officio. These are telecommunications undertakings, trust service providers, public entities and critical entities (Article 7a(2)). Former operators of essential services were placed in the register ex officio as a separate group. According to the Minister of Digital Affairs, an ex officio entry of critical entities first requires their status to be formally established under the Crisis Management Act (Q&A 2.37). Until then, according to the Minister of Digital Affairs, an entity meeting the future criteria itself assesses its status under the KSC Act and files an application if it meets the criteria (Q&A 2.38).
An entry made ex officio covers only the data listed in Article 7(2)(1)–(8) and (19)–(26), established on the basis of public registers, the electronic address database or data provided by the competent supervisory authorities (Article 7a(2)). The authority does not know the rest, so it issues a request to supplement it, and the addressee has six months from service. The gap is filled by an application to change the entry, not by an application for entry (Article 7b(4)). The distinction matters in practice, because an application for entry concerning an entity that is already registered does not lead to an entry (Article 7d(3)(2)). According to the Minister of Digital Affairs, such an application goes to the register operator for verification and the entity does not have to withdraw anything (Q&A 2.48 and 2.54). According to the Minister, an entity that should have been entered ex officio and has not received a notification reports the fact to s46-admin@nask.pl (Q&A 2.11).
A separate situation arises where an entity carries on several types of activity. An entry made ex officio may cover one of them and omit the others. The act then requires the register to be supplemented with the activity not covered by that entry.
What data has to be gathered before the form is opened
The scope of the application is set by Article 7(2)(1)–(18). The register is maintained in the KSC ICT system, and the self-registration form is available at wykaz-ksc.gov.pl. Some items are registry data the organization has to hand. The rest calls for work across several teams at once, and it is that part which decides how long preparation takes.
Apart from registry data, six groups of data call for the most work.
- the sectoral classification, meaning the sector, subsector and type of activity under Annex 1 or 2, separately for each type of activity carried on;
- the declaration of the size of the entity against the micro, small and medium-sized enterprise criteria, and for a healthcare provider that is not an entrepreneur and for a municipal office — the number of persons employed as at the date the financial statements were drawn up;
- the ranges of public IP addresses and the domains used on a continuous basis;
- the details of contact persons — at least two, or at least one in a micro or small enterprise and in an important entity that is a public entity (Article 9(1)–(3)), with the account administrator in the system additionally providing a PESEL number or an electronic identification means identifier;
- information on the member states in which the entity carries on activity, together with the type of that activity;
- information on any contract with a managed cybersecurity services provider, where one has been concluded, together with that provider’s details.
Two items on this list cause the most trouble. The ranges of IP addresses and domains have to be agreed between the network team and the owners of the services, and in organizations with distributed infrastructure nobody maintains such a list on a current basis. The PESEL number (or electronic identification means identifier) of the account administrator is in turn often read as excessive, although it follows directly from the provision and serves to authenticate that person in the system.
It is worth knowing that data held in the register is not subject to the act on access to public information or to the provisions on the re-use of public sector information (Article 7(3)). What is publicly available is only the number of entities broken down by sector, subsector and type of activity (Article 7i). It is updated at least once a quarter.
Who signs the application and what they are answerable for
The application is signed by the head of the entity or by a person they authorise. A qualified electronic signature, a trusted signature and a personal signature are all admissible, as is a qualified electronic seal identifying the person (Article 7c(6)). Where an attorney acts, a power of attorney in electronic form is attached. No power of attorney is attached by a commercial proxy disclosed in the National Court Register or by an attorney disclosed in CEIDG. According to the Minister of Digital Affairs, the power of attorney must be drawn up in Polish and granting it is subject to stamp duty (Q&A 2.18 and 2.63). According to the Minister, the attorney may also make the declaration that the data is true, while the head of the entity remains responsible for the application being properly filed (Q&A 2.66).
More important than the signing technique is the content of the declaration. The application contains a declaration by the head of the entity that the data is true, made under pain of criminal liability under Article 233 § 6 of the Criminal Code. The legislator excluded from that liability the reporting of IP address ranges and domain names. Those are precisely the data whose complete currency cannot be guaranteed in a large organization.
A sequencing recommendation follows. The sectoral classification and the declaration of the size of the entity should be settled and documented before the application is signed. Signing the application is the last step of the classification process, not its beginning. According to the Minister of Digital Affairs, the application is completed and signed by the same person, and an application completed by an employee cannot be passed to the head of the entity for signature (Q&A 2.55).
What happens after the application is filed
The entry is made at the moment the application is filed in the system (Article 7d(1)). The act provides for no proceeding and no decision. According to the Minister of Digital Affairs, an application whose data conflicts with an existing entry nevertheless receives the status “Oczekuje na weryfikację” (awaiting verification) and the register operator approves or rejects it (Q&A 2.54). The act does, however, list four situations in which no entry is made (Article 7d(3)).
- the application does not contain the data subject to entry;
- the application concerns an entity already in the register;
- the application does not contain the declaration of the head of the entity;
- the application has not been signed.
The Act does not provide that such an application stops the filing deadline from running. It is therefore worth filing early enough to submit a corrected application in time.
The entry opens access to the ICT system. The act frames this as an obligation, because the entity begins using the system once it has obtained its entry in the register (Article 9(1)(4)). This is the practical reason not to leave registration until last — the same channel is later used to report significant incidents. According to the Minister of Digital Affairs, entities that met the conditions on 3 April 2026 are to connect to the S46 system by 3 April 2027 (Article 46(4), Article 34(3)(2) of the amending act and Q&A 3.1). By the same date they implement the obligations of Chapter 3, including incident reporting (Article 33(1) of the amending act). Former operators of essential services report significant incidents under the new provisions from 3 October 2026 at the latest (Article 33(4) of the amending act). Where a notification cannot be submitted through the system, the method of submitting it is set by the competent CSIRT (Article 31(1)). The reporting obligation does not depend on the entry.
The obligation does not end with the entry. A change in the data covered by the application is reported within 14 days of the day it occurs (Article 7c(3)). This applies equally to a change of contact persons and to changes in IP address ranges and domains. If the organization ceases to meet the conditions, it files an application for removal together with a statement of reasons, and the authority has one month to examine it (Article 7f(3) and (4)).
Finally, the question that comes up most often in board meetings. Failure to file the application on time is a ground for a discretionary financial penalty — the authority may impose one where the gravity and significance of the provisions infringed justify it (Article 73(1a)(1)). A separate financial penalty may be imposed on the head of the entity personally, where the duration, scope or nature of the infringement justifies it (Article 73a(1)(1)). Financial penalties under Article 73(1)–(4) and Articles 73a–73c and 76b may in any event be imposed for the first time only two years after the amendment entered into force (Article 35 of the amending act). Both penalties for failing to file the application on time fall within that deferral, unlike the penalty of up to PLN 100 million under Article 73(5). The deferral concerns when a penalty may be imposed, not the obligation to file. The first real consequence of delay is therefore not a penalty. It may be an entry made by the competent cybersecurity authority on the basis of public registers and data available to the authority (Article 7j(1) and (2)). Such an entry does not close the matter, because the authority then calls on the entity to supply the missing data within six months of receiving the notification, under pain of a penalty (Article 7j(3)).
Most common mistakes
- Counting the deadline from the day the obligation was learned about. The deadline runs from the day the conditions were met, or follows from the transitional schedule. The date on which the organization found out about the matter has no legal significance.
- Treating the entry as the moment the obligations arise. The entry is declaratory. The periods for implementing an information security management system and for the first audit run regardless of whether the application has been filed.
- Assuming an entry made ex officio closes the matter. Such an entry covers only part of the data. The remaining items are supplied by the entity itself on request, within six months. Failure to supply them carries a penalty. According to the Minister of Digital Affairs, the obligation lapses if the entity ceases to meet the conditions before those six months expire (Q&A 2.42).
- Reporting one type of activity instead of all of them. An entity carrying on several types of activity reports them separately. Omitting one means an incomplete entry. The omitted activity does not fall outside the act as a result, because the entry is declaratory (Article 7d(5)). The gap has to be filled with an application to change the entry.
- Leaving the entry without updates. The 14-day deadline for reporting a change of data applies at all times. A change of contact person or a rebuild of network addressing are registration events, even though nobody calls them that.
Conclusions and next steps
The application for entry is a technical act. What precedes it is not technical, namely establishing whether and in what character the organization falls under the act. The register reflects that decision, it does not take it. The quality of the entry therefore depends on the quality of the earlier classification, not on how smoothly the form is handled.
How to apply for entry step by step
The following sequence works in organizations with a complex structure.
- Establish whether the entity has been entered ex officio and whether a request to supplement the data is pending.
- Settle the classification for each type of activity separately and record the reasoning.
- Gather the technical and contact data, starting with the IP address ranges and domains.
- Put the complete set, together with the wording of the declaration, before the head of the entity and decide who will complete and sign the application. According to the Minister of Digital Affairs, it must be the same person (Q&A 2.55).
- Once the entry has been made and the full set of data supplied, check that the account administrator has received the access details for the ICT system (Q&A 2.15). According to the Minister of Digital Affairs, a public entity entered in the register ex officio registers in the S46 system itself once it receives information about the entry, even before it has supplied all the data covered by the request to supplement (Q&A 7.6). Appoint the person responsible for reporting changes.
The fifth point tends to be skipped, and it is the one that decides whether the register stays consistent with the facts. The authority may carry out verification activities and call for a correction within seven days (Article 7k). The deadline is short, because the data in the register is meant to be current at all times.
Frequently asked questions about the KSC register
What is the deadline for applying for entry in the KSC register?
Entities that met the criteria on 3 April 2026 had until 3 October 2026 to apply under the schedule set by the Minister of Digital Affairs. All others have six months from the day they met the criteria (Article 7c(1) of the KSC Act). An application filed after 3 October 2026 still leads to an entry (Article 7d(1)). Entities entered in the register ex officio do not apply for entry, but supplement the data on request (Article 7b(2) and (4)).
Where and how is the application submitted?
Electronically, in the ICT system that keeps the register — the self-registration form is available at wykaz-ksc.gov.pl. The application is signed by the head of the entity or a person they authorise, with a qualified electronic signature, a trusted signature, a personal signature or a qualified electronic seal indicating the person (Article 7c(6)).
Does the absence of an entry mean the organisation is outside the KSC Act?
No. The entry is declaratory (Article 7d(5)). Obligations follow from meeting the criteria in Article 5, and the deadlines for implementing them run regardless of whether the application has been filed.
What if the entity has been entered in the register ex officio?
Do not file an application for entry — one concerning an entity already listed does not lead to an entry (Article 7d(3)(2)). Missing data is supplied through an application to amend the entry within six months of receiving the request (Article 7b(4)). According to the Minister of Digital Affairs, an application filed nonetheless does not have to be withdrawn, and two entries for the same entity are reported to s46-admin@nask.pl (Q&A 2.48).
What data must be prepared before opening the form?
Apart from registry data, six groups call for the most work. The first three are the sector classification for each type of activity, the declaration of the entity’s size and the ranges of public IP addresses and domains. The fourth is the details of contact persons — at least two, or at least one in a micro or small enterprise and in an important entity that is a public entity (Article 9(1)–(3)). However, Article 73a(1)(6) does not exempt the head of an important entity that is a public entity from the penalty, so it is safer for such an entity to designate two persons. The account administrator additionally provides a PESEL number or an electronic identification means identifier. The last two are the Member States in which the entity operates and information on any contract with a managed cybersecurity service provider. The full scope of the application is set by Article 7(2)(1)–(18).
What happens after the application is filed?
The entry is made the moment the application is submitted in the system (Article 7d(1)) — there is no procedure and no decision. According to the Minister of Digital Affairs, once the full set of data has been supplied the account administrator receives the access details for the ICT system (Q&A 2.15). The entity later uses that channel to report significant incidents, and reports any change in the data covered by the application within 14 days (Article 7c(3)).
Related materials
- Does every organization fall under NIS2? — the classification of the entity as the step that has to precede the application for entry.
- Where should the board begin preparing for NIS2? — the order of board decisions once the status has been established.
- What should a NIS2 gap analysis contain? — assessing readiness for the obligations of Chapter 3.
- What to do after 3 October 2026, once the deadline for entry in the KSC register has passed? — late applications, ex officio entries, entries made by the authority and keeping the entry up to date
Sources
- Act of July 5, 2018 on the National Cybersecurity System, consolidated text (as at August 18, 2026), Articles 5, 7–7m, 9, 16, 31, 46, 73–73c and 76b — ISAP, Chancellery of the Sejm: isap.sejm.gov.pl (in Polish)
- Act of January 23, 2026 amending the Act on the National Cybersecurity System and certain other acts (Journal of Laws 2026, item 252), Articles 25 and 33–35 — Journal of Laws: dziennikustaw.gov.pl (in Polish)
- Act of June 6, 1997 — Criminal Code, consolidated text (as at July 28, 2026), Article 233 § 6 — ISAP, Chancellery of the Sejm: isap.sejm.gov.pl (in Polish)
- Communication of the Minister of Digital Affairs of April 8, 2026 on the schedule for filing applications for entry in the register of essential and important entities and for the start of use of the ICT system by essential or important entities (Official Journal of the Minister of Digital Affairs, item 7) — Ministry of Digital Affairs: gov.pl (in Polish)
- Minister of Digital Affairs, National cybersecurity system — questions and answers on the amendment of the KSC Act, update of October 2026 — Q&A 1.42, 2.11, 2.15, 2.18, 2.37, 2.38, 2.42, 2.48, 2.54, 2.55, 2.63, 2.66, 3.1, 7.6 and 9.5 — cyber.gov.pl (in Polish)
- Ministry of Digital Affairs, “Amendment of the Act on the National Cybersecurity System (KSC) — self-registration in the register of essential and important entities” — gov.pl (in Polish)
- S46 System, “Self-registration (entry in the KSC Register)” — NASK, Ministry of Digital Affairs: gov.pl (in Polish)
Establish the status before you fill in the application
If the classification of the organization has still not been settled in writing, the application for entry will reflect uncertainty rather than a decision. NIS2 and KSC readiness support covers establishing the status for each type of activity and preparing the data required in the application.
This material is general and educational in nature. It is not an individual legal opinion or a recommendation for any specific organisation. The scope of the obligations should be assessed against the situation of the organisation concerned.
Legal status: November 2026.