NIS2 doesn't just want you to secure your own systems. It wants you to secure your supply chain — the vendors, suppliers, and service providers who have access to your data, systems, or infrastructure. The problem is that most companies handle this by collecting ISO 27001 certificates from suppliers. That's not what NIS2 wants. It wants evidence, not certificates.
Article 21(2)(d) of NIS2 requires measures to secure the supply chain. Specifically, you must:
Here's what happens: a company asks suppliers for their ISO 27001 certificate. The supplier sends a PDF. The company files it. Supply chain security done.
But the certificate proves the supplier has a security management system. It doesn't prove the supplier's security actually works. The supplier could be fully certified and still have a misconfigured S3 bucket, unpatched critical vulnerabilities, or an open admin panel — none of which the auditor checked.
An ISO 27001 certificate from a supplier is evidence of intent, not evidence of effectiveness. NIS2 wants the latter.
Instead of collecting certificates, ask suppliers for:
NIS2 expects security practices to be in supplier contracts. That means specific, measurable requirements, not vague "supplier shall maintain appropriate security." Useful contract terms:
If a supplier is compromised and the compromise reaches your systems or data, that's a NIS2 incident for you. You must report it within 24h/72h. The supplier's certificate doesn't protect you. Your verification of their security might have.
This is why supply chain security under NIS2 isn't about collecting PDFs. It's about knowing whether your suppliers can actually withstand the threats that would reach you through them.
Aethel Guard is a Netherlands-based security architecture firm serving EU companies of all sizes. Your architect, not your vendor.