Guide
NIS2 software for SMEs: Implement with a small team and IT partner
Implement NIS2 with a limited team: choose software using ownership, external providers and a small, dependable initial scope.


Your IT provider operates the systems. One internal person coordinates security alongside other duties. Management needs to decide but does not know which evidence is missing. This is a typical organisational bottleneck for a small team: work is distributed, but its context is not.
NIS2 software must work with your existing team. Using a recovery test, this guide shows how to involve management, an internal owner and an IT partner without loading every task onto the coordinator.
“Small” does not automatically mean exempt or in scope
Germany’s classification depends on activity, size criteria and special rules under section 28 BSIG. Establish this before buying a package. Related companies can also matter when assessing size.
Once the obligation is established, do not start implementation with every available function. Choose an important service, its internal owner and the supporting IT partner.
Three roles rather than a new department
| Role | Responsibility in the first workflow |
|---|---|
| Management | Decide priorities, resources and residual risks |
| Internal service owner | Assess impact and accept implementation from a business perspective |
| External IT partner | Perform and evidence agreed technical work |
Outsourcing a service does not remove internal responsibility. Conversely, an internal coordinator need not perform every technical check personally. What matters is who supplies each statement and who assesses it. Our guide to an ISMS without an internal IT department explores this allocation.
Use this template in these measures
Implementation measure
Handle and review security incidents
Mapped requirements (3)
- A.5.26 · Reaktion auf Informationssicherheitsvorfälle (DE)
Supporting contribution
The guidance connects coordinated response, records, communication, handover and reasoned closure in the existing case. The organisation provides suitable competence, technical interventions and actual results.
- A.5.27 · Erkenntnisse aus Informationssicherheitsvorfällen (DE)
Supporting contribution
Review connects causes, types, frequency and costs to changes in risks, safeguards, procedures and briefings and their effect. An archived review alone is insufficient.
- A.5.28 · Sammlung von Beweismaterial (DE)
Supporting contribution
The work connects authority, preservation suitable for the medium and state, origin, integrity checks, protected storage and traceable transfers. Competent acquisition and case-specific legal admissibility still require checking.
Further framework mappings of this measure
TISAX · 1.6.2
VDA ISA 6.0.3 · Partial contribution
Coordinated handling, reasoned prioritisation, communication and learning contribute to managing reported events. Other applicable categories, protection-need additions, partner responses and organisational requirements remain to be addressed.
Read the source ↗
Implementation measure
Maintain security contacts and use threat intelligence
Mapped requirements (3)
- A.5.5 · Kontakt mit Behörden (DE)
Supporting contribution
The workflow establishes relevant authorities, triggers, ownership and official usable routes, maintains them and uses authority information to understand expectations. Actual contact and reporting follow the circumstances.
- A.5.6 · Kontakt mit speziellen Interessengruppen (DE)
Supporting contribution
Maintained specialist contacts enable relevant information flow, exchange and support. Significant findings reach the responsible roles; no mandatory membership catalogue is required.
- A.5.7 · Bedrohungsintelligenz (DE)
Supporting contribution
Information needs, suitable internal and external sources, preparation and contextual analysis produce understandable actionable intelligence. Strategic, tactical and operational perspectives and use in risks, safeguards and testing are included.
Implementation measure
Prepare and exercise incident readiness
Mapped requirements (3)
- A.5.24 · Planung und Vorbereitung des Informationssicherheitsvorfallmanagements (DE)
Supporting contribution
The work establishes and exercises known reporting, coordination and response routes with actual roles, authority and available resources. Organisational introduction, competence and execution remain to be demonstrated.
- A.5.25 · Beurteilung und Entscheidung über Informationssicherheitsereignisse (DE)
Supporting contribution
Preparation defines criteria, priorities and decision ownership and exercises assessment. Actual incoming events still require assessment and a reasoned decision based on the known facts.
- A.6.8 · Meldung von Informationssicherheitsereignissen (DE)
Supporting contribution
The workflow communicates an easy reporting channel and fallback, explains prompt reporting of suspected events and the necessary facts without attempts to exploit vulnerabilities. The existing employee rule and exercise support actual use.
Further framework mappings of this measure
TISAX · 1.6.1
VDA ISA 6.0.3 · Partial contribution
Reachable staffed reporting and feedback routes are prepared and exercised with actual roles. Awareness, usable internal and external channels and applicable protection-need additions still require checking.
Read the source ↗TISAX · 1.6.2
VDA ISA 6.0.3 · Partial contribution
The work prepares classification, responsibilities, suitable response objectives, escalation and communication and exercises the decision route. It does not demonstrate actual handling, specific reporting obligations or all applicable protection-need and testing requirements.
Read the source ↗
Implementation measure
Prepare IT emergency response and recovery
Mapped requirements (3)
- A.5.30 · IKT-Bereitschaft für Business Continuity (DE)
Supporting contribution
Prepared service cards connect BIA objectives with responsibilities, dependencies, recovery and planned exercises. Suitable infrastructure, competence and actual testing must still be implemented in operation.
- A.5.29 · Informationssicherheit bei Störungen (DE)
Supporting contribution
The plan defines safeguards, approved alternative controls and security checks during emergency operation. Their suitability and actual application must still be verified.
- A.8.13 · Sicherung von Informationen (DE)
Supporting contribution
The existing service workflow connects required backups, protected copies, monitored execution and safe regular restore tests to business requirements.
Further framework mappings of this measure
TISAX · 5.2.8
VDA ISA 6.0.3 · Partial contribution
Activation, alternative communications, accessible recovery procedures and planned testing support continuity planning. Applicable protection-need additions, technical implementation, partner coordination and actual test results must still be addressed separately.
Read the source ↗
First workflow: Does recovery work?
Take the provider’s backup report. Establish whether it demonstrates successful backup alone or tested recovery too. Which application was involved? Which data was restored? Is the result sufficient for your operation?
In Kopexa, this evidence belongs to the associated measure. Information assets, other assets and risks provide context. A process-level BIA helps justify the necessary recovery time using business consequences, instead of copying it from the provider’s offer.
An identified gap receives an owner and specific treatment. Completion then requires suitable evidence. “Our IT partner handles it” becomes a traceable working state.
Employees do not need to become the GRC team
Employees often need only a few relevant rules and understandable reporting routes. Kopexa’s Workforce Hub brings approved content to the appropriate audience and documents participation. The central GRC system remains the basis for security owners.
Test two interfaces: can the coordinator arrange approval of a new policy version? Does an occasional user understand what to read or complete? Our policy guide explains the connection.
A small pilot with clear acceptance
Choose the recovery case for the two-week guided trial. At the end, management, the internal owner and IT partner must be able to explain the same status: what was checked, what is missing and who acts?
Calculate setup, internal maintenance and required external support separately. Ask about partner and employee access and eventual export. Accept the software when it eases coordination and all three roles recognise their open tasks.
Quick answers
Frequently Asked Questions
Still have a question? Find the answers here.
Should an SME import all security data immediately?
No. Start with a clear scope and a few meaningful data sources. Extend only once ownership and maintenance work.
Sources
- BSIG section 28: Scope — Bundesministerium der Justiz [Accessed ]