Monitoring and response
A 24/7 SOC where the audit finds an empty path
A requirements audit often ends with the sentence that a significant incident has nowhere to go. This line is the same company’s operational answer: monitoring named 24/7, built on SIEM, EDR and XDR, plus incident response. We do not publish a response time or a service credit.
What you commission when the notification path is missing
- Event collection in a SIEM and correlation that can be shown at the next reading of Article 11.
- Endpoints under EDR or XDR, where the workstation or server is inside the information system in scope.
- Incident response: who raises the case, who classifies a significant incident, who prepares the early warning and the CSIRT notification. The statutory clocks (24 hours, 72 hours, one month) remain the entity’s duty. We do not turn them into our SLA.
- A trace after the case that a compliance audit can later read as evidence, not as a slide.
The name “24/7” means the monitoring is run continuously. It does not mean a guaranteed minute of contact or a percentage of availability. Those figures are absent because they are not agreed in a commission.
A longer account of this line, written from the analyst’s console, is on 24cyber.pl. We keep it beside the audit here, because an incident-handling gap with nobody watching remains a gap.
Neighbouring lines on audytnis.pl
Return to the KSC audit if the gap still needs a name. Implementation sets the notification procedures. A pentest checks whether the attack path is visible in the log at all. Systems provide the sources the SOC reads. A re-audit comes back after the change.
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.