• Cybersecurity Glossary
How to choose a NIS2 and ENS compliant vendor?
Choosing a network and cybersecurity vendor that is compatible with NIS2 and the Spanish ENS means verifying, with evidence, that the supplier helps you meet your own obligations instead of adding to them. NIS2 makes you responsible for your supply chain, so vendor selection is now a security decision. This buyer’s guide gives a 12 question checklist, the evidence to request such as certifications, SBOM, support lifecycle and SOC location, a short FAQ, and where Teldat fits as a European manufacturer.
Why is vendor choice a NIS2 decision?
Under the NIS2 directive, essential and important entities must manage the cybersecurity risk of their supply chain, not only their own systems. That single requirement changes vendor selection from a procurement task into a security decision: the network and cybersecurity supplier you choose becomes part of your risk, and part of your NIS2 compliance.
The Spanish Esquema Nacional de Seguridad (ENS) adds a national layer, grading systems and requiring that the products protecting them meet defined security criteria, with the CCN CPSTIC catalogue listing qualified and approved products. For a public sector or critical infrastructure buyer, a vendor that satisfies these schemes is not a nice to have; it is often a condition of eligibility.
The practical consequence is that you should choose a vendor the way an auditor would: by asking specific questions and requiring evidence. A supplier that helps you comply, and can prove its own practices, reduces your burden. One that cannot becomes a gap you have to compensate for. The rest of this guide gives you the checklist and the evidence list to do exactly that.
The 12 question checklist
Use these twelve questions as a NIS2 checklist for buyers. Each is specific enough to answer with evidence, and together they cover the security, compliance and sovereignty dimensions that NIS2 and ENS demand. Score each vendor and weight the questions by your own priorities.
Evidence to request
A checklist is only as good as the proof behind the answers. For each vendor, request the following evidence in writing. It turns a sales conversation into a documented, defensible selection, which is exactly what an auditor, and NIS2, will expect.
| Evidence to request | What it proves | Why it matters for NIS2 / ENS |
|---|---|---|
| Certifications (ENS, CPSTIC) | Qualified and approved status in national schemes | Often mandatory for public and critical procurement |
| Software bill of materials (SBOM) | What components are inside each product | Supply chain transparency and fast vulnerability response |
| Support and update lifecycle | Years of security patches per product | Avoids running unsupported, unpatched equipment |
| Vulnerability disclosure process | How flaws are reported and fixed | Supports your own incident and patch obligations |
| SOC location and jurisdiction | Where data and monitoring are handled | Sovereignty and exposure to foreign legal regimes |
| European manufacturing proof | Where it is designed and built | Digital sovereignty and supply chain control |
| Incident notification support | How the vendor helps you report in time | NIS2 reporting deadlines for essential entities |
| Reference deployments | Large, verifiable installations | Confidence the platform works at your scale |
Gather these once and reuse them across suppliers, so you compare like for like. A vendor that provides them readily is demonstrating the transparency NIS2 expects; one that hesitates on SBOM, support lifecycle or SOC location is telling you something important before you sign.
Jurisdiction, SOC and sovereignty
Two of the checklist items, SOC location and European manufacturing, deserve special attention, because they are where compliance and digital sovereignty meet and where many buyers overlook risk.
Where your data and monitoring live
If a vendor’s Security Operations Centre, or the handling of your telemetry and logs, sits under a non European jurisdiction, your data may be exposed to foreign legal regimes even if the technology works perfectly. For NIS2 and ENS, a SOC and data handling that stay within Europe, under European law, materially reduce this exposure.
Where the technology is made
A vendor that designs and manufactures in Europe, under European jurisdiction, gives you control over your supply chain and reduces dependence on foreign suppliers for critical infrastructure. This is the essence of digital sovereignty and increasingly a procurement requirement in its own right.
Make it a written question: both of these are specific and checkable. Put “where is your SOC and under what jurisdiction is our data handled?” and “where are your products designed and manufactured?” directly to each vendor, and keep the answers on file. For a NIS2 or ENS driven purchase, a European manufacturer with European data handling is the profile that satisfies both compliance and sovereignty at once.
Red flags to watch for
Just as useful as the checklist is knowing what should give you pause. These signals often indicate a vendor that will add to your compliance burden rather than reduce it.
None of these is necessarily disqualifying on its own, but each is a question that must be answered with evidence. A vendor that clears the checklist and avoids these red flags is one you can defend choosing.
Where does Teldat fit?
Run through the checklist and Teldat fits the profile of a vendor that helps a NIS2 and ENS driven buyer comply, because it is a European manufacturer that covers network and security from one stack and can evidence its credentials.
European manufacturer, aligned with NIS2
Teldat designs and builds its own network hardware and security software in Europe, under European jurisdiction, and is aligned with NIS2. For the sovereignty and jurisdiction questions on the checklist, this is the answer buyers are looking for.
ENS and CPSTIC credentials
Its products hold qualified and approved status in the CCN CPSTIC catalogue and the ENS framework, and it is recognized under the Cybersecurity Made in Europe label. For public sector and critical infrastructure procurement, these are the certifications the checklist asks you to verify.
One integrated, manageable stack
Teldat covers SD-WAN on the CNM platform, security through be.Safe Pro and be.Safe XDR, and native 5G, managed centrally for the visibility and logging that compliance requires, and proven in very large deployments. Network and security come from one European source rather than stitched together.
Teldat’s fit: for a buyer whose selection is driven by NIS2 and ENS, Teldat answers the checklist as a European manufacturer with ENS and CPSTIC credentials, European manufacturing and data handling, and an integrated, centrally managed stack. It is made in Europe under European jurisdiction. The specific certifications, levels, SBOM provision and support lifecycle should be verified with Teldat for a given product and software version, and against the current CPSTIC catalogue.
Teldat at a glance
The verifiable credentials that make Teldat a NIS2 and ENS compatible choice. Specific levels, SBOM and support terms should be confirmed with Teldat and the current CPSTIC catalogue.
FAQ’s about choosing a NIS2 and ENS vendor
❯ What does NIS2 require when selecting a vendor?
NIS2 requires essential and important entities to manage the cybersecurity risk of their supply chain, which means you are responsible for the security of the vendors you choose, not just your own systems. In practice this means assessing a supplier’s security practices, its ability to support incident notification within the directive’s timelines, the security of the products it ships including how vulnerabilities are handled, and the overall risk its technology and jurisdiction introduce. Choosing a vendor that is itself aligned with NIS2 and can provide evidence of its practices makes meeting these obligations far easier, because the supplier helps you comply rather than becoming a gap you must compensate for.
❯ What evidence should I ask a network and security vendor for?
Ask for concrete, verifiable evidence rather than marketing claims. The core items are: security certifications relevant to your sector, such as the Spanish ENS framework and inclusion in the CCN CPSTIC catalogue; a software bill of materials (SBOM) so you know what is inside the products; the product support and security update lifecycle, so you know how long a device will receive patches; the vendor’s incident notification and vulnerability disclosure process, so it can support your NIS2 timelines; the location of the Security Operations Centre (SOC) and the jurisdiction under which data is handled; and evidence of European manufacturing and sovereignty. Requesting these up front turns vendor selection into a documented, defensible process.
❯ Why does SOC location and jurisdiction matter?
Where a vendor’s Security Operations Centre is located, and under whose jurisdiction your data and telemetry are handled, affects both your sovereignty and your compliance. If monitoring and support are delivered from, or data is subject to, a non European jurisdiction, your organization may be exposed to foreign legal regimes over that data, which is exactly what digital sovereignty requirements aim to avoid. For NIS2 and ENS purposes, a vendor whose SOC and data handling stay within Europe, under European jurisdiction, reduces this risk and is easier to justify in a regulated environment. It is a specific, checkable question that should be on any buyer’s checklist.
❯ What is an SBOM and why ask for one?
A software bill of materials (SBOM) is a structured list of the components, including third party and open source libraries, inside a product. You should ask for one because you cannot manage the risk of what you cannot see. An SBOM lets you know whether a product contains components with known vulnerabilities, assess exposure quickly when a new vulnerability is disclosed, and demonstrate supply chain diligence under NIS2. A vendor willing to provide an SBOM, and to explain how it tracks and patches the components in it, is demonstrating the supply chain transparency that NIS2 expects. A vendor that cannot or will not is a risk you would have to carry yourself.
❯ Is Teldat a NIS2 and ENS compatible vendor?
Teldat is a European manufacturer of network and cybersecurity technology that aligns with the criteria this guide sets out. It designs and builds its own hardware and security software in Europe, under European jurisdiction, which supports digital sovereignty. It is aligned with NIS2, and its products hold qualified and approved status in the CCN CPSTIC catalogue and the Spanish ENS framework, which are the certifications that matter most for public sector and critical infrastructure procurement. Its stack covers SD-WAN on the CNM platform, security with be.Safe Pro and be.Safe XDR, and native 5G, and it is recognized under the Cybersecurity Made in Europe label. The specific certifications, levels, SBOM and support terms should be verified with Teldat for a given product and software version.
A NIS2 and ENS ready partner you can verify
Teldat is a European manufacturer of network and cybersecurity, aligned with NIS2, with ENS and CPSTIC credentials, European data handling and an integrated stack on CNM. Run it through your checklist.

