Compliance and re-audit
A compliance audit and a re-audit, without an Article 15 declaration
This line covers a compliance audit against the KSC Act and a second reading of findings after the action plan. We do not present ourselves as auditors who meet Article 15(2), and we do not cite a certificate from a regulation we have not confirmed as published. The separate domain audytornis2.pl goes further into that subject.
Two commissions sold on this page
- A compliance audit: scope, the requirements in Articles 8 and 10, a report and a plan. That is the audytnis.pl specialty, set out on the audit page.
- A re-audit: we return to the identifiers in the previous report and check whether the closing evidence exists. The cycle of “at least once every three years” in Article 15(1) runs from the statutory audit report. Our re-audit does not start that date.
The statutory audit we do not declare
An essential entity undergoes an information-system security audit at least once every three years, at its own cost (Article 15(1)). An important entity does not have this cycle. An authority may order it an external audit after a significant incident or another breach (Article 15(1b)). A copy of the statutory audit report goes to the authority within three working days (Article 15(1a)).
The statutory audit is carried out by an accredited body, by at least two auditors who meet the practice or certificate conditions, or by the competent sectoral CSIRT (Article 15(2)). A regulation is to set the certificate list (Article 15(8)). We have not checked whether it is already in the Journal of Laws, so we cite no certificate.
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.