Security

Supply chain security for optics: what NIS2 asks of your transceivers

Supply chain security for transceivers: grey market, coding, per-item test reports and what NIS2 requires. Includes a practical buyer's checklist.

5 Min. LesezeitVon Yvan Watchman

A transceiver is a small thing. It disappears into a port nobody looks at again, which is exactly why it gets forgotten in supply chain discussions. Meanwhile, all your traffic runs through it.

Buying transceivers? This article covers what to check so you don't end up with counterfeit, untested or wrongly coded optics in your network: provenance, coding and test reports, plus an eight-point checklist you can use on your next order. And because it's European Cybersecurity Month, what NIS2 (in the Netherlands: the Cyberbeveiligingswet, in force since 15 August 2026) asks of your suppliers.

What NIS2 actually asks

Article 21(2)(d) of NIS2 lists "supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers".

Article 21(3) gets more specific: you have to take into account the vulnerabilities of each direct supplier and "the overall quality of products" and the cybersecurity practices of those suppliers.

In the Netherlands, the Cbw covers essential and important entities across eighteen sectors. The Dutch NCSC lists securing your supply chain explicitly as one of the ten duty-of-care measures.

What the rules don't do: prescribe how you assess suppliers. You do have to be able to explain your choices. "We bought the cheapest batch on a marketplace" isn't an explanation.

Where optics go wrong

The risk rarely sits in the word "compatible". It sits in three other places.

Grey market and counterfeits. Counterfeit network hardware isn't hypothetical. In 2021, US investigators found 7,260 counterfeit Cisco transceivers in a single New Jersey warehouse. In another case, a seller of counterfeit Cisco networking equipment was sentenced to more than six years in 2024; that gear had ended up in hospitals, schools and military systems, and often failed.

Untested optics. A module that "works" somewhere doesn't necessarily run stable in your switch, on your software release, at your temperatures. Without testing, you find out when the link starts flapping.

Unknown coding. Every transceiver has an EEPROM with fixed fields: vendor name, part number, serial number, date code (SFF-8472 for SFP/SFP+, SFF-8636 for QSFP). DOM/DDM adds live readings: temperature, voltage, bias current, Tx and Rx power. Switches read that EEPROM when you insert a module, and many platforms reject a module whose data doesn't add up.

So coding is just filling those fields correctly for your platform. Nothing wrong with that. The real questions: who did it, with what tooling, and was the module tested afterwards on the platform it's going into?

Compatible is fine, if the chain holds up

Vendors are clear about support: Juniper's JTAC doesn't support third-party optics that aren't qualified, and may ask you to swap in a qualified module while troubleshooting. That's a support question, not a security one. You answer it with a supplier that tests on the actual vendor platforms and can show you a test report.

Our optics come from Solid Optics, a Dutch company and Innovation Harbor's main supplier of optical equipment. They test locally in the Netherlands, with a full test line for all vendors:

  • every item ships with its own test report;
  • batch and individual testing with full traffic, on the equipment the module is intended for;
  • CWDM and DWDM are tested under fluctuating temperatures with an OSA;
  • lifetime warranty on all transceivers, with advance replacement if anything goes wrong.

Coding for your platform (Cisco, Juniper, Arista and more) is optional. Where needed, we test a module ourselves first, or Solid Optics tests it on your own equipment.

Our RMA rate so far is 0.7%. That counts everything: modules that turned out not to be the right choice after all, degradation and checks. We've never had a DOA.

Buyer's checklist

Take this into your next supplier review:

  • Provenance. Who made it, and can your supplier name the chain back to the manufacturer?
  • Test report per item. Tied to the serial number, not just a batch statement.
  • Tested on the target platform. With traffic, on the vendor and type of equipment the module goes into.
  • Coding. Who codes, with what tooling, and is the module retested afterwards?
  • Check EEPROM and DOM. On arrival, read vendor name, part number and serial and compare them with the packing slip and test report. Check that DOM values are plausible.
  • Record it. Log serial numbers in your asset management. During an incident you want to know which modules sit where.
  • Warranty and RMA. How long, how fast, advance replacement or not? And how does the supplier define its RMA figures?
  • Put it in writing. Written agreements with your direct suppliers make your NIS2 story demonstrable.

Want to know what's in your racks?

Our Optics & link test (Link Ready) measures power levels, runs a basic OTDR and hands you documented results. The DC cabling quick scan gives you a clear view of your cabling in one visit.

Check our services or browse optics directly. Rather talk it through first? Call or email us. You'll get an engineer on the line, not a phone menu.

Yvan Watchman

Über den Autor

Yvan Watchman

Gründer von FiberNxt und Xyphen IT

Yvan Watchman ist Gründer von FiberNxt und Xyphen IT. Er baut und betreibt seit Jahren Netzwerke und Rechenzentrumsinfrastruktur in und um Amsterdam.

LinkedIn-Profil

Passende Produkte und Dienstleistungen

Häufig gestellte Fragen

Are compatible transceivers a security risk?

Not by definition. The risk is unknown provenance and missing tests, not the word "compatible". A compatible module from a supplier that tests every item on the platform it's meant for, and can prove it with a test report, is easier to defend than an "original" module from an anonymous marketplace seller.

Does NIS2 require a test report for every transceiver?

No. NIS2 and the Dutch Cyberbeveiligingswet require measures for supply chain security, but they don't prescribe how you assess your suppliers. A per-item test report is simply one of the easiest ways to show you know what you're putting into your network.

Can FiberNxt test a transceiver on my own equipment first?

Yes. We can test a module ourselves first, and our supplier Solid Optics can test on the customer's own equipment. On site, our Optics & link test (Link Ready) measures power levels and runs a basic OTDR, with documented results.

Weiterlesen