To the ones who actually read the supplier questionnaire
Quiet work, part 8: a completed questionnaire and a certificate quickly turn into a tick in the supplier register. Someone still reads every answer and finds the "planned", the missing attachment and the scope that is too narrow. Why nobody notices.
The questionnaire came back after three weeks. 112 questions, filled in by the service provider's sales team, "yes" almost everywhere. Attached, an ISO 27001 certificate as a PDF. The supplier register could now show a tick.
Someone still reads every answer. Under multi-factor authentication for administrative access it says "Yes, rollout planned". Under backup it says "see attachment", and the attachment is missing. And the scope of the certificate names the data centre, but not the support team that accesses the systems by remote maintenance. Three follow-up questions go out, and one answer later becomes an obligation in the contract.
What happens when it is missing
A questionnaire that is only filed checks nothing. It proves that someone asked, not what was answered. In the register, "planned" becomes "in place", and a certificate with a narrow scope becomes a confirmation for the whole company.
This only shows when an attack runs through exactly this service provider. Then the question is no longer what the supplier ticked, but who read it.
Where it is required
For entities under NIS2, Section 30(2) no. 4 of the German BSI Act names as a minimum measure supply chain security, including security-related aspects of the relationships with direct suppliers or service providers.
The directive behind that section is more specific. Under Article 21(3) of the NIS2 Directive, entities "take into account the vulnerabilities specific to each direct supplier and service provider and the overall quality of products and cybersecurity practices of their suppliers and service providers, including their secure development procedures".
Vulnerabilities specific to each supplier do not appear in a summary answer. They appear in the one line that says "planned" instead of "implemented". Recital 85 justifies the obligation with the many incidents in which attackers got in "by exploiting vulnerabilities affecting third-party products and services", and encourages entities to include cybersecurity risk-management measures in their contracts with direct suppliers.
Why nobody sees it
Reading leaves no result you can show. Whoever only files the questionnaire is done in five minutes. Whoever reads it needs an afternoon and produces follow-up questions, a delayed contract and a supplier who wants to know whether this is really necessary. In the register, both look the same: a tick.
And what the work prevents never happens. Nobody hears about the remote maintenance access that got a second factor after the follow-up question.
To them
To the ones who read the scope of a certificate first. Who do not count "planned" as "yes", but ask for the date and write it down. And who request a missing attachment, even when the contract was supposed to be signed this week.
Sources
Section 30 BSIG (German BSI Act), risk-management measures of particularly important and important entities, para. 2 no. 4 (German). Directive (EU) 2022/2555 (NIS2 Directive), Article 21(2)(d) and (3), recital 85.
In the next part: to the ones who do not read email with the admin account. The previous part: To the ones who keep the phone numbers in the emergency manual up to date.
Questions about this update?
Talk to us – we are happy to show you this feature in a demo.


