Define the work before choosing technology
List the decisions and records the organisation must support, including legal scope, ownership of Article 21 controls, Article 23 incident escalation, supplier reviews and management oversight under Article 20. Identify which existing tools already perform these tasks reliably.
Separating essential functions from desirable convenience features avoids a procurement decision driven by demonstrations rather than concrete operational needs.
Evaluate the build option realistically
An internally developed system can match existing risk models and data structures, connect to proprietary environments and avoid some dependence on a vendor's roadmap. But development also creates obligations for authentication, software maintenance, availability, audit logging and access control.
Budget for maintaining regulatory mappings as national law and guidance change, not merely for the first release. A small development team can create a polished interface without establishing sustainable legal review or content ownership.
Assess purchased software beyond licence price
A vendor may supply managed updates, audit trails, reusable workflows and implementation support. Verify exactly which Member States and entity types it covers, how often requirements are reviewed and whether source references can be inspected.
Total cost includes configuration, migrations, onboarding, third-party integrations, data export, security due diligence and contractual support. Ask how the provider handles a serious incident or prolonged service outage.
Test security, control and exit arrangements
Both choices need proportionate protection for sensitive evidence, vulnerability findings, identities, supplier details and incident records. Specify role-based permissions, retention, logs, backup testing and recovery responsibilities.
For a purchased system, negotiate workable data portability and exit assistance. For a custom system, identify replacement maintainers and document critical integrations. Avoid a design in which evidence can be read only through one proprietary interface.
Make a decision through a representative pilot
Use one regulated service to test scope assessment, a material risk, a control gap, corrective-action verification and board reporting. Measure administrative effort, review quality and ability to trace each conclusion to source evidence.
Choose an approach that can be maintained. NIS2 requires appropriate security management and oversight; it does not require the organisation to buy or build a specialised application.
Questions on the text
Does NIS2 require specialised compliance software?
No. The Directive requires appropriate cybersecurity risk-management measures and associated obligations, not purchase of a specific software product.
Can a readiness score prove compliance?
No. The applicable law, operational control effectiveness and supporting evidence require assessment.
What should be reviewed before software selection?
Assess service scope, national-law mapping, security, workflow quality, evidence portability and ownership of ongoing updates.