Requirements audit
What we read in the requirements audit
We compare what the entity does, and what it has written down, with Article 8 and the provisions that sit next to it. We do not scan the network and we do not issue a certificate. We look for gaps that can be shown to management as a finding, not as a slogan.
Seven fields that are always on the question list
- Incident risk management: whether the assessment is repeated and whether it leads to a decision, not to a table left on a shelf (Article 8(1)(1)).
- Incident handling: classification of a significant incident, an early warning within 24 hours, a notification within 72 hours and a final report within a month of the notification (Article 11(1)). In the requirements audit we check that the path exists. Running the monitoring and the response is the 24/7 SOC line, described more fully on 24cyber.pl.
- Continuity: continuity plans, contingency plans and recovery plans, with a trace that they were exercised (Article 8(1)(2)(f)).
- The ICT supply chain: supplier vulnerabilities, product quality and whether the direct supplier is named at all (Article 8(1)(2)(e) and (2)).
- Access control, physical access and multi-factor authentication where the provision speaks of appropriate cases (Article 8(1)(2)(c), (l) and (n)).
- Cryptography: policies and procedures, including encryption where it is appropriate (Article 8(1)(2)(k)).
- People: staff education, cyber hygiene and whether the manager has a documented annual training (Article 8(1)(2)(i) and (j), Article 8e). Training for the head is commissioned on the NIS2 implementation line. A longer account of the programme is on audytnis2.pl.
Documentation without which a finding floats
Article 10 requires normative and operational documentation: the management system, infrastructure protection, continuity, technical documentation of the system, and records that the acts in the documents actually happened. We ask about versioning, about who can see a document, and about the retention period. A missing document is described as an evidence gap, even when the team “does it that way”.
What this audit is not, and what the offer still includes
The requirements audit itself is not a network scan, a firewall design or a takeover of incident handling. It reads documents, interviews and traces. When a finding is about monitoring, a test, a programme or a device, you close it with the same company: SOC, NIS2 implementation, auditor, pentests and systems. Those lines are described more fully on 24cyber.pl, audytnis2.pl, audytornis2.pl, cyberscan24.pl and cybersystemy.pl.
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.