Buyer's guide

How to choose a data diode: 10 questions to ask

Updated November 17, 2026 · 7 minute read

Buying a data diode is not like buying a switch. The products look similar on a data sheet and behave very differently in a plant. Use these ten questions with any vendor, including us. A good vendor will answer them plainly and tell you where their product is not the right fit.

1. What does it enforce physically, and what only in software?

This is the most important question. Hardware diodes make the link one-way in physics. Software diodes make the protocol one-way and rely on you to supply a transmit-only link if you need physical enforcement. Neither is wrong, but you should know which one you are buying. Read software versus hardware data diodes for the trade-offs.

2. What exactly needs to cross the boundary?

List the data: files, database tables, historian tags, OPC UA nodes, Modbus registers, syslog, video. A diode must be able to carry each one in a way that makes sense without acknowledgements. Check that your protocols are supported and how each is handled, not just that the product "supports OT".

3. How does it cope with packet loss?

With no return channel, the receiver cannot ask for a resend. Ask how loss is repaired (forward error correction, redundancy) and, just as important, how loss is detected and reported when repair is not possible. Silent data loss is worse than loud failure.

4. How is data integrity proven?

Look for end-to-end checks such as file hashes and per-batch verification, and for a clear rule about what happens to anything that cannot be proven complete. A safe design quarantines it and raises an alarm.

5. What happens to a database replica when something goes missing?

If you replicate databases, ask whether changes are applied in order and exactly once, and how the replica recovers from a gap (for example by sending a fresh snapshot). See one-way database replication for OT networks.

6. What is certified, by whom, and for what scope?

Some buyers need a specific certification, such as Common Criteria, for a regulation or contract. Ask which product version was certified, under which scheme, and what the certificate covers. If the answer is "none yet", that is useful information too. It is better to hear it now than after the purchase.

7. Can you read the threat model and the test results?

A vendor confident in the design will publish what the product claims, what it does not claim, and how it was tested. Marketing language such as "unhackable" is a red flag.

8. How is it managed, and by whom?

Ask about the management interface, user roles, an audit trail, configuration validation and how upgrades are applied. A diode you cannot operate safely is a risk of its own.

9. What does it really cost over five years?

Compare the whole cost: hardware or servers, licenses or subscriptions, support, installation, extra modules for each protocol, and renewal terms. Hardware appliances are usually sold by quote, often in the tens of thousands of dollars for a pair, with annual support on top. Software is typically a subscription on commodity servers. Ask for the price list in writing.

10. What happens when you need help, or the vendor goes away?

Ask about support hours and response times, how security reports are handled, and what happens to your deployment if the vendor stops selling the product. Software you run on your own machines keeps running; check what the license allows.

A simple way to decide

  • If a rule or contract demands a certified product, start with certified appliances.
  • If you need physical enforcement in a sealed box, a hardware diode fits.
  • If you need many flows across many sites quickly and affordably, and you can supply a transmit-only link, software is worth a serious look.
  • You can combine them: software on top of a one-way link or a hardware diode you already own.

Our own answers to these questions are on the Security page and in the comparison table, including what we do not claim.

Test it against your checklist

Start a free 14-day trial of DiodeGuard and see how it handles your files, databases and protocols. No card needed.

Start free trial