A Year of GuidePoint Security Running Labshock

GuidePoint Security has been running Labshock for a year, and their logo now sits on our site.

It started on their booth.

It Began With a Button

At HOU.SEC.CON last year, Kevin Kumpf pressed an E-Stop and a stack light went dark.

Not a simulation. Not a video on a slide. A real button wired to real hardware, in front of people.

That was the first time Labshock drove a physical system in public, and it happened on the GuidePoint booth rather than ours.

Why Their Booth Was a Test

GuidePoint do OT security for a living — assessments, critical infrastructure, real plants and real controllers, every week.

So putting our environment on their stand was not a favour. It was an audit conducted in public, by people who would recognise immediately if the process underneath were fake.

Why a Year Is the Number That Matters

Tools get bought all the time. Tools get dropped faster.

A year means somebody there keeps opening the platform and keeps choosing it over the alternative, long after the decision stopped being novel. Nobody renews a habit out of politeness.

That is the only review that counts, and it is not one we can write ourselves.

Nothing Changes On Our Side

We keep building. We keep testing. We keep shipping.

Thanks to Patrick Gillespie and the GuidePoint team.

OT security must be testable.

Not documented.

Try It Yourself

• Start free: github.com/zakharb/labshock — runs locally with Docker, no cloud.
• The full account of the HOU.SEC.CON hardware demonstration: labshocksecurity.com/press/hou-sec-con-2025-real-hardware
• Run an assessment workflow you already use against a plant you are allowed to break.
• Ask how other teams are using it: discord.gg/bpmaQFfW76