The head of the entity
What the Act asks of the person in charge
Articles 8c to 8e place responsibility for cybersecurity duties, decisions on the management system, resources and oversight on the head of the entity. A compliance audit exists so those decisions rest on findings, not on a supplier’s assurance.
What the Act says directly
- The head remains responsible even when the duties were entrusted to another person with that person’s consent (Article 8c).
- The head decides on preparing and overseeing the management system, plans the resources, assigns tasks and is to ensure that staff know the internal rules (Article 8d).
- The head, and a person entrusted with the head’s duties in this area, takes training once each calendar year. Attendance must be documented (Article 8e). The training is commissioned on the NIS2 implementation line. A longer account of the programme is on audytnis2.pl.
- A person carrying out tasks under Article 8 or Article 11 presents a National Criminal Register statement of no conviction for offences against the protection of information, with the exception the Act states for a security clearance (Article 8f). We do not perform those checks as a service.
Fines that can reach the person in charge
Article 73a allows a fine on the head of the entity when the time, scope or nature of the breach justifies it. The ceiling is 300% of remuneration calculated as holiday pay equivalent, and 100% of that remuneration for the head of a public entity. A separate fine on the entity itself still exists under Article 73.
For an essential entity, Article 73(3) caps the fine at the higher of EUR 10,000,000 or 2% of turnover from economic activity, and not less than PLN 20,000. For an important entity, Article 73(4) states EUR 7,000,000 or 1.4% of turnover, and not less than PLN 15,000. In the cases in Article 73(5) the authority imposes a fine of up to PLN 100,000,000. Euro amounts are converted at the National Bank of Poland rate of 31 December of the year before the decision.
Six lines, one company
Each line has its own page here. The KSC audit comes first because it is this domain’s specialty. The rest is in the offer, not in a referral away.
KSC audit
Gap, risk, report and plan against the KSC Act. The deepest part of this domain.
24/7 SOC
Monitoring named 24/7: SIEM, EDR, XDR and incident response, with no response-time promise.
NIS2 implementation
Policies, procedures, an ISMS, incident reporting and training for the head once a gap is named.
NIS2 auditor
A compliance audit and a re-audit. No declaration of Article 15(2) auditor status.
Pentests
A vulnerability scan and a penetration test as technical evidence, on a written scope.
Systems
NGFW, segmentation, backup, MFA, EDR, monitoring, plus CCTV and access control when the finding calls for them.