
www.simplify-data.de
Many small IT firms, agencies and hosting partners are not an "important entity" under the BSIG themselves. NIS2 clauses still end up in their contracts. The reason: affected customers must take supply chain security into account under Section 30(2) BSIG, and they pass questionnaires, audit rights and reporting duties down to their suppliers. This article shows what evidence is typically requested in 2026, what to watch for in contracts, and how a reusable evidence pack lets you answer in a prepared way (as of November 2026).
Please note: this article is general information, not legal advice. Which obligations apply to you depends on size, sector and role. For an overview of direct applicability, see our article "NIS2: Who is affected and which obligations apply".
Why the supply chain reaches you
The law addresses the affected entity, not its suppliers. But the entity must take supply chain security into account, including with regard to direct providers, and be able to document it. Anyone who runs email, backup, remote maintenance, cloud or custom software for an affected company therefore sits in its risk chain. Annex 1 of the BSIG also names managed service providers explicitly as a type of entity.
Typical triggers
- Tenders and supplier audits by large customers
- Annual reviews and contract renewals
- Requests from cyber insurers
- The customer's BSI registration, where public IP ranges and service providers may come up
Without a solid answer you may lose the contract or sign vague liability clauses just to get the questionnaire off your desk.
What customers actually ask for
Requests differ in detail but usually follow the areas in Section 30. The table shows which evidence is often requested and why the customer needs it.
| Evidence | Why the customer needs it |
|---|---|
| Contact and deputy for security incidents | their own report within 24 and 72 hours |
| MFA and access concept for your admins on customer systems | access control |
| Backup and restore description | business continuity |
| List of subcontractors | supply chain at the second level |
| Patch and vulnerability process | security in maintenance |
| Encryption in transit and at rest | cryptography |
| Staff training records | cyber hygiene |
| Contractual reporting deadline to the customer | often shorter than the statutory deadlines |
| Deletion and exit concept | provider change and data processing |
ISO certificates help but rarely replace the product-specific question: how exactly do you protect this particular customer? Answer concretely and refer to your actual systems.
Contract clauses to review
NIS2 annexes are rarely standard contracts. Check every clause before signing, and involve your legal adviser on liability questions.
Reporting deadlines
Customers must be able to submit an early warning within 24 hours themselves. They therefore often demand much shorter deadlines from providers. Only agree to deadlines you can meet at night and at weekends, and define who can be reached and how.
Liability and audit rights
Annexes often contain the passing on of fines, unlimited liability and audit rights without notice. Clarify what you can truly control technically. Audit rights with lead time, a defined scope and confidentiality are reasonable. Technically you can deliver MFA, logging, backup tests and a reporting channel. You do not replace the customer's legal assessment.
Subcontractors and exit
Data centre, monitoring providers and freelancers belong on a maintained list. Agree how changes are announced and describe how data is returned and deleted at the end of the contract.
The reusable evidence pack
Instead of answering every questionnaire from scratch, maintain a pack you extend as needed:
- Two-page summary of security measures
- Network and backup sketch
- Contacts and deputies for incidents
- List of subcontractors
- Record of the last restore test
- Patch rhythm and vulnerability process
- Training record with dates
This shortens questionnaires and prevents contradictory answers from sales and engineering. Name one person responsible for reviewing the pack at least twice a year.
Checklist for IT providers
- Find out which customers are affected by NIS2 or see themselves as such.
- Inventory access to customer systems (VPN, RDP, M365 partner access, ticket systems).
- Enforce MFA and time-limited admin rights.
- Write down the incident process with internal escalation and customer notification.
- List subcontractors and review contracts with them.
- Document one restore test per quarter.
- Check the data processing agreement and the NIS2 annex against the same current state.
- Create the evidence pack and name a permanent owner.
How Simplify Data can help
We help agencies and SMEs produce the technical evidence customers ask for in 2026: zero-trust access, documented backups, MFA and traceable operating processes. Learn more about IT consulting, Managed Services and Zero Trust VPN. For a first conversation, use the contact page.
Sources
- BSI: Questions and answers on NIS-2 (German)
- BSI: NIS-2 obligations (German)
- Federal Law Gazette: BGBl. 2025 I No. 301, including Annex 1 BSIG (German)
- BSIG Section 30: Risk management measures, para. 2 supply chain (German)
- BSIG Section 28: Essential and important entities (German)
This article is for general information only and is not legal advice; for your specific case, please consult a lawyer.