Technical evidence
A scan and a pentest when the document cannot answer how an attacker gets in
A compliance audit reads policies and traces. It does not replace a check of whether a service can be broken. This line is vulnerability scanning and penetration testing for companies and institutions, inside an agreed scope and under a commission. cyberscan24.pl describes the testing at more length. Here we tie it to a gap in the report.
How we set the test next to the audit
- A vulnerability scan: a picture of the hosts and services inside the information system in scope, not the company’s whole internet “while we are here”.
- A penetration test: an attempt along an agreed path, written so it can be repeated in a review, without an attack guide for third parties on this page.
- The link to Article 8: a vulnerability at a direct supplier, and product quality, are supply-chain questions. The test does not replace that question, but it gives the question a fact.
- A written scope before the start. A test with no commission and no boundary is not an offer.
We do not publish prices, counts of vulnerabilities found, or client names. We do not promise that a test “passes” the Act.
A longer account of the methods is on cyberscan24.pl. If you first need to name which requirement applies to the entity at all, start with the KSC audit.
What usually travels with the test
A SOC needs a log source, otherwise the test result stays in a PDF. Systems close what the test showed on the firewall, on access or on backup. Implementation adds a procedure when the gap is organisational. A re-audit checks the closure 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.