Skip to main content
Labshock
LoginStart Free
← All Updates
PRODUCTSeptember 17, 2026

Ultrametrix Validated Its Discovery Module on Labshock

A discovery product needs something real to observe. Axel Franc and his team built the environment, generated the traffic, then pointed their own tool at it and checked what it found.

Labshock is not only a place to learn OT security. It is a place to validate a product.

Ultrametrix used it that way.

What They Did

Axel Franc and his team used Labshock during their research to generate OT traffic and validate UMX Explorer, their discovery module.

Ultrametrix ships two modules — UMX Explorer and UMX Risk Manager — for mapping OT environments, visualising cyber risk and working towards IEC 62443 compliance.

Products like that need something real to observe:

  • assets
  • communication flows
  • network structure
  • industrial traffic

So they connected to a Labshock environment. Not for training. For validation.

Their site is at ultrametrix.fr

Why This Is a Direction, Not a Side Effect

You can run PLCs, HMIs, SCADA, engineering stations and network components, and generate genuine OT communication between them. You can build zones and conduits.

Then you connect your own product and watch what it discovers.

Does it find the assets? Does it understand the flows? Does its picture match the environment you already know is there?

That last question is the valuable one, and it is the thing production cannot give you. In a plant you are comparing your tool's output against an asset list that is also a guess. Here you built the environment, so you know the answer before you ask.

Ground truth is the product.

Learn Is One Direction. Test and Validate Are Another

Asset discovery, IDS, network monitoring, risk platforms, SIEM, security controls — all of them need industrial environments to prove they work.

You should not need a production plant every time you want to validate an OT product.

Build the environment. Generate the traffic. Connect the product. Check the result.

OT security must be testable.

Not only documented.

Try It Yourself

  • Build an environment whose contents you know exactly, then point your tool at it.
  • Compare what it reports against what you built. The gap is the finding.
  • Start free: github.com/zakharb/labshock — runs locally with Docker, no cloud.
  • Validating a product and want the setup walked through? discord.gg/bpmaQFfW76
LABSHOCK SECURITY — OT SECURITY MUST BE TESTABLE, NOT DOCUMENTED