Logging and monitoring
Planning and operating continuous monitoring and logging of security-relevant events — with defined retention.
Ready for
NIS2?
15 questions, five minutes, instant result — no registration, no email required.
NIS2 in four action areas
NIS2 does not ask for paperwork, it asks for security that demonstrably works. In practice, implementation falls into four action areas: governance and reporting, logging and detection, vulnerability and patch management, and incident response. The self-check scores exactly those four.
Your answers stay in your browser. We store nothing and set no cookie for it.
NIS2 self-assessment in 5 minutes
Your result
0/ 100 · NIS2 readiness score
Critical gaps — Core NIS2 requirements are open. Priority is logging, detection and a workable reporting process.
In preparation — First building blocks exist, but continuous operations, evidence and exercised processes are missing.
Largely solid — Most requirements are met — coverage, evidence and exercises remain open.
Well positioned — High level of implementation. The leverage is in evidence, automation and continuous validation.
Result per action area
The score is passed into the contact form as text — you can edit or delete it before sending.
Requirements and matching building blocks
What NIS2 requires — and which building block covers it.
SIEM platform
Detection, analysis, response and documentation of security incidents across the corporate network on one platform.
Threat intelligence
Integrating TI feeds to continuously use current data on cyber threats, vulnerabilities and attack techniques.
Endpoint detection and response
EDR for fast detection and response on endpoints — including operations, containment and audit trails.
Regular vulnerability scans
Recurring scans to identify potential security gaps across systems and networks.
Assessment and prioritisation
Processes to assess and prioritise vulnerabilities and to meet the agreed remediation window per criticality.
Penetration testing
Testing system security and uncovering weaknesses that regular scans do not surface.
Patch management
Effective patch management to remediate known vulnerabilities quickly and verifiably.
Cyber security analysis
Continuous analysis and handling of security incidents within an appropriate timeframe by a skilled analyst team.
Incident response
Building an incident response plan plus setting up and training a response team (internal, external or as a service).
SOAR automation
Automation for detection and response — automation supports, the human analyst decides.
Reporting obligations
A clear process to detect and report incidents within 24 to 72 hours.
Recommended next steps
Governance & reporting
Clarify applicability, assign accountability at management level, define the 24h / 72h / 1 month reporting process and assess your supply chain.
Strengthen evidence: exercise the reporting process, tighten supplier contracts and plan recurring training.
Logging & detection
Build central logging and an operated SIEM, put EDR into operations and connect threat intelligence.
Measure detection coverage against MITRE ATT&CK, cut false positives and extend use cases.
Vulnerabilities & patching
Establish regular scans, define criticality and remediation deadlines and operate patch management verifiably.
Sharpen remediation SLAs and reporting, schedule penetration tests with retesting.
Incident response
Write an incident response plan, name a response team and secure forensic capacity with response times.
Exercise response: tabletop drills, containment automation and regular compromise assessments.
NIS2 questions and answers
Scope, obligations and reporting deadlines.
Who does NIS2 apply to?
NIS2 applies to essential and important entities across 18 sectors, depending on sector, company size and turnover. Suppliers are often pulled in through their customers' supply chain requirements.
What obligations does NIS2 introduce?
Risk management, logging and detection, incident response processes, vulnerability and patch management, supply chain security, training and reporting within 24 hours, 72 hours and one month.
How quickly must incidents be reported?
An early warning within 24 hours, an incident notification within 72 hours and a final report within one month.
Does a managed SOC make us NIS2 compliant?
A managed SOC covers the technical core requirements for detection, analysis, response and evidence. Governance topics such as applicability and supply chain are covered by our consulting.
What does the NIS2 self-check cost?
Nothing. The 15 questions run entirely in your browser — no registration, no email required and no answers stored.