NIS2-Readiness

NIS2

Not in scope yourself, but your customer requires NIS2

If your company does not fall under Section 28 of the German BSI Act (BSIG), the act generally places no obligations on you. Your customers, however, must ensure the security of their supply chain and pass requirements on by contract and questionnaire. Answer with reference to your service, honestly about your implementation status and with evidence you can actually show.

Workshop of a supplier in evening light, a clipboard with a form on a workbench in the foreground

Last updated: 2026-11-06

This page is for companies that are not in scope of NIS2 themselves but receive questionnaires, contract clauses or requests for evidence with a NIS2 reference from their customers. The other side, how an in-scope entity assesses its suppliers and which questionnaire it sends, is covered on the page on supply chain security. German law calls in-scope organisations essential entities (in Germany: besonders wichtige Einrichtungen) and important entities (wichtige Einrichtungen).

Are you really out of scope?

Settle this first, before you answer a questionnaire as a “supplier”. An organisation can be in scope if it carries out an activity listed in Annex 1 or 2 of the BSIG and has at least 50 employees or both turnover and balance sheet total above €10 million; figures of linked enterprises count. Suppliers from manufacturing can themselves fall under Annex 2, for example in machinery, electrical equipment or motor vehicle parts. IT service providers that install, manage, operate or maintain their customers’ systems can be managed service providers under Annex 1. The check is set out on the page on NIS2 applicability, the position of IT service providers on the page on IT service providers and MSPs.

If you are in scope, you have obligations of your own under the BSIG, whatever your customers ask for. The rest of this page applies to companies that have checked their applicability and concluded they are out of scope.

Why is your customer asking about NIS2?

Under Section 30(2) sentence 2 no. 4 BSIG, essential and important entities must take measures for “supply chain security, including security-related aspects of the relationships with direct suppliers or service providers” (our translation). The explanatory memorandum quoted by the BSI (Federal Office for Information Security) gives examples: contractual agreements with suppliers and service providers on risk management measures, on handling cyber security incidents and on patch management, as well as observing principles such as security by design and security by default. The entity should take into account the vulnerabilities of its direct suppliers and the quality of their cyber security practices, including the security of their development processes (as also stated in Article 21(3) of the NIS2 Directive).

The BSI makes clear: the BSIG does not oblige all suppliers and service providers. To meet their own obligations, however, entities must commit their suppliers to corresponding security requirements. For your customer, whether to keep working with a supplier that gives no reliable answers can therefore become a business decision.

For some digital entity types, such as cloud providers, data centre operators and managed service providers, it gets more specific: Implementing Regulation (EU) 2024/2690 requires them to have a supply chain security policy and names contract contents, including the provider’s duty to report without undue delay security incidents that pose a risk to the customer’s systems. If you supply such companies, questions about incident notification are particularly likely.

How NIS2 requirements reach a supplier. Left, the BSIG: Section 30(2) no. 4 obliges the essential or important entity to ensure supply chain security. Middle, the entity: supplier assessment, contract, questionnaire. Right, the supplier that is not in scope: generally no obligation under the BSIG, but contractual requirements; answer with reference to the service, with implementation status and evidence. Arrow back: answers and evidence feed into the entity’s supplier assessment.
Tap the graphic to open it at full size.How requirements travel from the law via the customer to the supplier. Source: BSIG as amended on 22 October 2026, Section 30(2) no. 4; BSI info package on supply chain security; own illustration.

What can your customer require by contract?

What you owe follows from your contract, not from the BSIG. In negotiations, your customer can ask for almost anything; you decide what you commit to. The table separates where a requirement comes from:

RequirementOriginAssessment for you as a supplier
Appropriate security measures for the servicecustomer’s obligation under Section 30(2) no. 4; example in the explanatory memorandumrelate the scope to the systems and data your service touches for the customer
Information about security incidentsBSI recommendation; contract content under the Implementing Regulation for the digital entities named thereimportant for the customer because it has reporting obligations of its own; agree trigger and deadline precisely
Patch managementBSI recommendation; example in the explanatory memorandummainly for software, devices with software and IT services
Security by design and by default, taking BSI recommendations into accountBSI recommendation; example in the explanatory memorandummainly for manufacturers of software and connected products; we handle SBOM questions as a service under SBOM service
Evidence, information, auditsnot prescribed by law; details openagree type, frequency and confidentiality; the BSI explicitly asks for verifiable properties
A specific certificate (such as ISO 27001)not prescribed by law; according to the BSI there is no general certificate for the supply chain requirementthe customer can ask for it, but a certificate does not replace the customer’s own assessment

The right-hand column is our own professional assessment. We do not assess liability, contractual penalties, termination rights or indemnities; have such clauses reviewed by a lawyer.

How do you answer a supplier questionnaire?

A questionnaire is answered well when every answer fits the service provided, describes the actual status and is backed by evidence. This is how we approach it:

  1. Define the scope: which service do you provide for this customer, and which of your systems, data and people does it touch? A parts manufacturer exchanging drawings answers different questions than a service provider with remote access.
  2. State your own classification first: say that you have checked your applicability under Section 28 BSIG and with what result. That saves follow-up questions.
  3. Choose a yardstick: the BSI recommends that suppliers who are not in scope check their own compliance with the measures in Section 30(2) BSIG for agreements with their customers. The ten areas of Section 30(2) therefore work well as the structure of your standard answers; an overview is on the page on Section 30 BSIG.
  4. Be honest about the status: implemented, partly implemented or planned with a date. An answer “planned by March 2027” is more useful to the customer than a “yes” that does not hold up when asked.
  5. Assign evidence: for every answer, a document, report or log that you can present on request or make available for inspection.
  6. Approve and maintain: management approves the answers. Keep one master version and adapt it per customer instead of writing every questionnaire from scratch.

There is no standard question catalogue. The BSI welcomes efforts by industry to develop one and, for orientation, refers to the UP KRITIS best-practice recommendations on requirements for suppliers. A questionnaire from the entity’s side to download is on the page on supply chain security.

Which evidence is appropriate?

There is no “NIS2 certificate”, even if the term appears in requests. The BSI states explicitly that there is no general certificate for the supply chain requirement. Appropriate evidence fits the service and the risk for the customer. Suitable evidence examples, from lean to extensive:

EvidenceWhat it showsLimits
Self-declaration with named supporting documentsimplementation status per area, backed by policies, logs and reportsnot independently audited; its value depends on honesty and on the supporting documents
CyberRisikoCheck under DIN SPEC 27076baseline assessment for small and medium-sized enterprisesaccording to the BSI only an initial assessment; NIS‑2 compliance cannot be achieved with it
ISO 27001 certificateaudited management system; according to the BSI covers a large part of the measures under Section 30 if implemented comprehensivelycheck the scope: does it cover the service for the customer? It does not automatically meet all BSIG requirements
Audit report or on-site inspection at the supplierreview by the customer or an appointed auditoreffort for both sides; agree scope and confidentiality

Our recommendation: offer inspection of confidential documents instead of sending them, for example in a video call or at a meeting. Network diagrams, vulnerability reports and contingency plans do not belong in a questionnaire attachment.

Excessive requirements and how to answer them

Some requirements go beyond what a small supplier can deliver or should commit to at all. The suggested answers below are our professional assessment, not legal advice:

RequirementProblemSuggested answer
“Provide your NIS2 certificate.”No such certificate exists.offer a self-declaration along the ten areas of Section 30(2) and any existing certificates or audit reports
“Confirm that you meet all NIS2 requirements.”You are not an addressee of the BSIG; a blanket commitment can neither be verified nor limited.limit the commitment to specifically described measures for the agreed service
“Report every security incident within 24 hours.”“Every incident” includes events with no link to the customer; the 24 hours come from the customer’s own reporting duty to the BSI.commit to informing without undue delay, limit the trigger to incidents that may affect data, systems or delivery capability for the customer, distinguish initial information and follow-up report
“Unrestricted on-site audit rights, at any time.”effort and confidentiality towards other customers not addressedpropose audit rights with advance notice, scope, frequency and priority for document review or remote audit
“Bind all your subcontractors in the same way.”also hits subcontractors with no link to the customerlimit flow-down to subcontractors that have access to the customer’s data or systems or contribute to the service

Example: a parts manufacturer answers a supplier questionnaire

Fictitious example, not a client. A contract manufacturer of milled parts has 34 employees, €4.8 million turnover and belongs to no group. A machinery manufacturer that has classified itself as an important entity sends it a supplier questionnaire. The contract manufacturer receives drawings via the customer’s supplier portal, sends questions by email and has no access to the customer’s network. An external provider manages its IT. Its answer looks like this (all values fictitious):

AreaAnswerEvidenceStatus
NIS2 statusApplicability under Section 28 BSIG checked: not in scope (34 employees, €4.8 million turnover, no linked enterprises). The following describes our implementation status with reference to our service for you. Binding commitments are governed by our contract.classification record of 15 September 2026implemented
Service referencecontract manufacturing to drawing. Customer data: drawings and order data. No access to the customer’s systems.--
Responsibilitymanaging director responsible, contact for information security named, shared mailbox set uporganisation chart, contact detailsimplemented
Handling customer datadrawings in one project folder per customer, accessible only to work preparation and production; deletion twelve months after the order endsaccess list, deletion policyimplemented
Access and MFAMFA for email, remote access and administrator accounts; other accounts to followreport of the sign-in configurationpartly, complete by 31 March 2027
Updatessecurity updates for servers and workstations monthly, critical vulnerabilities out of cycle; machine control computers after manufacturer approvalpatch report of the IT providerimplemented
Backupdaily backup, one copy kept offline, restore test once a yearlog of the last restore test of 12 August 2026implemented
Incidentscustomer informed without undue delay, at the latest 24 hours after becoming aware, if drawings or order data may be affected or delivery capability is at risk; follow-up report once clarifiedsecurity incident procedureimplemented
Trainingannual briefing for all staff with a computer workstation, focus on phishingattendance listimplemented
Service providersIT provider contractually bound to confidentiality, updates and incident notificationcontract extract for inspectionimplemented
Certificatesno ISO 27001 certificate; CyberRisikoCheck under DIN SPEC 27076 carried out in May 2026 as an initial assessmentresult report for inspection-
Evidenceinspection of all documents listed by appointment; confidential documents sent only under a non-disclosure agreement--

It comes with a short cover note that the contract manufacturer uses for all customers:

“We have checked our applicability under Section 28 BSIG and are neither an essential nor an important entity. We know that, as an in-scope entity, you must ensure the security of your supply chain, and we answer your questionnaire with reference to our service for you. Where a measure is not yet fully implemented, we give the date. We are happy to show you the evidence listed in a joint meeting.”

The answer commits only to what the company can prove and makes gaps visible with a date. It deliberately contains no commitments on liability or contractual penalties; those belong in the contract negotiation.

Three typical gaps on the supplier side

GapCauseEffectRemedy
Every questionnaire answered from scratchno standard answers, changing responsibilitycontradictory statements to different customers, high effortone approved master version along the ten areas of Section 30(2), updated annually and after changes
Commitments without evidencequestionnaire answered “yes” under time pressureevidence is missing when asked or audited, the customer’s trust suffersname evidence for every answer; without evidence, state “partly” or “planned”
Incident information not preparedcommitment in the contract, but no procedure and no contact listthe customer learns of an incident too late for its own reporting dutyprocedure with triggers, contacts per customer and a template for the initial information; rehearse once a year

How we help

We help suppliers build a reliable master answer, prepare the matching evidence and assess technical and organisational requirements from customers. Have the contract clauses themselves reviewed by a lawyer. If the check shows that you are in scope yourself, the NIS2 gap analysis shows where you stand.

Frequently asked questions

Do we have to register with the BSI as a supplier?+
No, as long as you are not an essential or important entity yourself. The registration duty under Section 33 BSIG only applies to in-scope entities (and domain name registration service providers). Check your applicability carefully, though, including linked enterprises.
Do we have to answer our customer’s questionnaire?+
Not under the BSIG, which does not oblige suppliers directly. Whether you are contractually obliged to provide information follows from your contract. In practice, your customer needs the information for its own supply chain security; without it, in the BSI’s view, it may not be able to continue the relationship.
Is an ISO 27001 certificate sufficient evidence?+
It can help a lot, but it is not sufficient automatically. According to the BSI, ISO 27001 covers a large part of the measures under Section 30 BSIG if implemented comprehensively, but each entity has to assess it as part of its risk management. What matters most to your customer is whether the scope covers the service provided to it.
How do we deal with several different questionnaires?+
Keep an approved master version structured along the ten areas of Section 30(2) BSIG and transfer the answers into each customer’s questionnaire. Answer questions that do not concern your service for that customer with “not applicable” and a short reason. Also ask whether the customer accepts your master version as an attachment.
Do we have to send the customer our entire security concept?+
That depends on your contract; the law does not prescribe it. In our view, a self-declaration with named evidence that the customer can inspect on request can be sufficient. Confidential documents such as network diagrams should only be handed over under a non-disclosure agreement.

Read more

Sources

This content provides general technical and organisational information and does not constitute legal advice (no legal services within the meaning of the German RDG).