Start with scope and legal mapping
Require a record of the legal entity, regulated services, sector category, size analysis, national law and reviewer. Check that the platform can distinguish essential and important entities and retain the basis for classifications.
Evaluate how updates to national legislation are tracked and reviewed. Draft EU amendments must not silently overwrite requirements already in force.
Check controls and evidence workflow
Look for Article 21 measure mapping, assigned owners, risk decisions, control status, periodic review dates and evidence references. A meaningful tool differentiates planned, implemented, tested and ineffective controls.
Test whether audit trails capture who changed a status and why. Ask how missing evidence, rejected findings and overdue corrective actions appear in reports.
Evaluate incident and supplier capabilities
Review escalation workflows for significant-incident assessment, timestamp records, notification preparation and authority-specific routing. Assess third-party registers, service dependencies, questionnaire reviews and follow-up tasks.
Check whether automated reminders work in realistic scenarios, including out-of-hours events. The platform should not assert that a reporting deadline has been met merely because an internal ticket was created.
Demand security and data portability
Evaluate role-based access, encryption, logs, backup and recovery, hosting arrangements, supplier assurances and export formats. The software may hold sensitive internal architecture and vulnerability evidence.
Ask for a practical demonstration of exporting a full evidence index and associated metadata. Avoid dependence on proprietary representations that cannot be independently inspected.
Run a service-based pilot before purchasing
Pilot the platform with one material service, several control types, a supplier assessment and an unresolved incident or evidence finding. Observe whether managers can understand risk and reviewers can trace a result to its source.
Compare total administration effort, implementation cost and the quality of assurance, not only the number of dashboard widgets. If a smaller toolset provides the required controls reliably, extra features may add complexity without value.
Questions on the text
Does a completed software assessment prove NIS2 compliance?
No. Actual obligations and operating controls must be evaluated against applicable laws and evidence.
Can the platform replace management oversight?
No. Management remains responsible for oversight under the applicable legal framework.