Final document
A report that can be handed to management
Each requirement in the agreed scope gets one of four statements and a trace of what that statement rests on. Next to it is an action plan. The plan is for your team. We do not sign that a gap is closed until we re-audit it, or you show the evidence in another agreed way.
Four statements, and nothing else in the heading
| Statement | When we write it |
|---|---|
| Met | There is a trace that the requirement works, not only that a policy names it. |
| Partial | An element exists, but scope, an update or evidence of performance is missing. |
| Gap | The requirement applies, and the trace is missing or contradicts the description. |
| Not applicable | The provision does not cover this entity or this service. The reason is in the report. |
What the action plan contains
- A reference to the requirement and to the finding, not to a general “raise security”.
- The proposed result: what evidence must exist so that a re-audit can change the statement.
- A role on your side that should own it. We do not invent names we were not given.
- A dependency: whether closing it needs a separate technical commission or management training.
The report is not an authority’s decision, it does not replace the copy of a report submitted under Article 15(1a), and it is not a statement of conformity. An essential entity that has the statutory audit duty submits a copy of that report to the authority within three working days of receiving it. Our document does not perform that step.
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.