Guide
NIS2 costs: Budget for software, consulting and internal work
Plan NIS2 setup and ongoing costs around your security gaps, internal capacity, software and required expert support.

NIS2 costs depend primarily on the security work that already functions in your organisation and the gaps that remain. A software licence, a consulting project and an internal security role cover different responsibilities. Comparing their prices alone produces an incomplete budget.
This guide explains how to plan NIS2 setup and ongoing operating costs for implementation in Germany. Updated: 12 November 2026. Fill the calculation structure with your actual quotes and internal effort; generic market prices would say little about your needs.
Establish your starting point before the budget
Determine which entity is affected and which services need assessment. The applicability check provides a starting point. Even without direct NIS2 applicability, customer requirements, other obligations and operational risks can require security investment.
Then review existing work. An ISMS, current policies and tested emergency procedures may be useful. Check that their scope and implementation can be evidenced. “We have a backup solution” differs from “We have successfully tested recovery of our core service”.
The NIS2 requirements guide helps structure this review. Under section 30 BSIG, implementation costs inform proportionality. They replace neither risk assessment nor the duty to implement appropriate and effective measures.
The five NIS2 cost drivers
| Area | Initial effort | Recurring effort |
|---|---|---|
| Classification and gap analysis | Assess scope, applicability and existing implementation | Assess changes in activities and company structure |
| Security organisation and ISMS | Establish roles, procedures, inventory and risk assessment | Keep risks, requirements and responsibilities current |
| Technical security measures | Close identified technical gaps and introduce solutions | Operate, maintain, test and renew where necessary |
| Evidence and reviews | Assemble evidence and define review procedures | Check results, address deviations and renew evidence |
| Training and support | Enable teams and supplement missing expertise | Account for new staff, management training and changing responsibilities |
Not every organisation needs the same products. Required technology follows from risks, the state of the art and applicable requirements. A fixed shopping list of SIEM, EDR and other product categories would not provide a sound calculation for every organisation.
Consulting, internal roles or software: what are you paying for?
External consulting and implementation support
Specialists can assess applicability, review gaps, build procedures with your team and support implementation. Specify expected results in the engagement: a documented gap assessment, a rehearsed reporting process or a professionally reviewed policy, for example.
Clarify which tasks your staff will handle and what support continues after the project. A consulting engagement does not transfer management's legal responsibility. It also does not automatically include technical implementation, training or ongoing maintenance.
Internal security responsibility
An internal role brings organisational knowledge and continuity. Whether it requires a new position, an existing function or a team depends on scope and risk. A generic employee threshold at which a CISO supposedly “pays off” does not answer that question.
Plan available working time, cover for absence and access to specialist expertise. Information security and data protection roles can cooperate but are not interchangeable. A data protection officer is not automatically responsible for all NIS2 work.
GRC software and templates
Software helps keep implementation status, tasks and evidence together. Templates can support the start; they must fit actual procedures and be reviewed. Professional decisions and technical work remain part of the budget.
Kopexa can combine the platform with individually agreed support. Compare the scope you need using current pricing and a specific quote. Also allow time for onboarding, data transfer and regular use.
Build a sound first-year calculation
Use the same basis for each item: scope, unit price, responsibility and result. Separate additional expenditure from internal capacity so both remain visible.
| Budget item | Calculation | What to clarify before approval |
|---|---|---|
| Platform | Contract costs for the period | Required functionality and usage scope |
| Setup and data transfer | Agreed project scope or hours × rate | Included data, procedures and teams |
| External expertise | Agreed services or hours × rate | Concrete deliverables and remaining internal work |
| Technical implementation | Quotes for each prioritised gap | Setup, operation and follow-on costs |
| Internal work | Planned hours per role | Time released from daily work and cover for absence |
| Recurring reviews and training | Frequency × effort per cycle | Owners, participants and expected records |
For a multi-year comparison, calculate setup costs + recurring costs for all years considered + planned changes. Avoid including internal work in one option and excluding it from another. A low licence price says little about total costs on its own.
A simple capacity calculation: if two owners each allocate four hours per week to implementation, that is eight hours per week in total. Whether this is sufficient depends on the outstanding tasks. This is a planning method, not a Kopexa project duration or promise of NIS2 compliance.
Which approach fits which starting point?
- Security knowledge and capacity available: A platform with suitable templates can support independent implementation. Identify where extra expertise is still needed.
- Owners available but experience missing: Combine internal implementation with guidance and clear interim reviews.
- Capacity or specialist knowledge missing: Agree concrete implementation support. Internal decisions, participation and ongoing responsibility remain necessary.
- Several management systems already in place: Assess reuse before starting a separate NIS2 project. The NIS2/ISO 27001 mapping helps.
Common budgeting mistakes
Budgeting only for the first year. Owners change, systems are replaced and evidence becomes outdated. Include maintenance and review from the outset.
Assuming certification is mandatory. Section 30 BSIG does not impose ISO 27001 certification on every affected organisation. Certification may be useful or contractually required for other reasons. If so, budget it as a distinct scope.
Treating software as a substitute for staff time. Someone still needs to make decisions, check information and complete work.
Spending the entire budget on documents. Policies and reports matter. Failed recovery or uncontrolled privileged access, however, require operational improvements.
Start with one outstanding task
Take your most important open NIS2 task and establish the required result, who will work on it, what is missing and how completion will be checked. This provides a better budget basis than a generic price per employee.
The NIS2 roadmap supports sequencing. Kopexa for NIS2 helps organise implementation and discuss the support you need.
Quick answers
Frequently Asked Questions
Still have a question? Find the answers here.
What does NIS2 compliance cost an SME?
A sound budget follows from existing implementation, outstanding risks and available capacity. Include software, external services, technical improvements, internal time and ongoing maintenance. A generic amount per SME is too imprecise.
Is consulting or software cheaper for NIS2?
They cover different tasks and can work together. Compare the complete scope, including internal work, technical implementation and support after setup.
Can I use government average costs as my budget?
An economy-wide impact assessment is not a quote for your organisation. Check the reference year, duties included and methodology. Your budget needs its own gap assessment and defined service scope.
What ongoing NIS2 costs arise?
Recurring work includes risk reviews, system maintenance, supplier assessments, training and evidence renewal, alongside agreed licence and support costs.
Can I implement NIS2 without external help?
It depends on expertise and available time. Internal implementation is possible when the required competence and capacity exist. Plan targeted support for knowledge or resource gaps.
What does a NIS2 audit cost?
First establish purpose, criteria, scope and expected evidence. An internal effectiveness review, a commissioned audit and ISO 27001 certification are different services. Comparable pricing requires the same scope.
How should NIS2 costs be treated for tax purposes?
Tax treatment depends on the expenditure type and the organisation’s circumstances. Ask your tax adviser to assess recurring services, purchases and any capitalisation requirements.
At what size does an internal CISO make sense?
A fixed employee threshold does not answer this. Risk, complexity, available expertise and sustained workload matter. Software and external specialists can supplement an internal role.