<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Had a call the other day that properly wound me up, and I think it&#x27;s worth talking about.]]></title><description><![CDATA[<p>Had a call the other day that properly wound me up, and I think it's worth talking about.</p><p>A prospective client asked four times - four - "do you have experience in OT?" Each time we explained: diverse OT environments across multiple industries and vendors, all tested safely. An Electronic Engineering degree (yes, people care about academics...). Team members who've worked in the industry (wrong industry!). Years of refined methodology. None of it landed.</p><p>The preconception was locked in before the call started: pen testers are IT guys who don't understand OT. Nothing we said was going to change that.</p><p>Here's what's mad about that. What we do is understand OT. We walk around plants. We have the dirty PPE to prove it. We sit in control rooms with operators and plant engineers talking about what keeps them up at night. We are the opposite of "IT guys". </p><p>A huge part of what we do is listening. We speak with operators who've seen things go wrong. Plant engineers who know what could cause the most harm without triggering safety systems. So much of OT is safety engineering - random, uncoordinated failures should not cause catastrophic failure. We're the people who work out whether an attacker could trigger those things deliberately and remotely. Something that happened once by accident? We work out if someone could make it happen on purpose.</p><p>Step 1 is understanding the process. A chemical plant is engineered completely differently to an automated warehouse, railway signalling system, or cruise ship. We work with your people to understand the process, work out which bits we can break, then go back and work out if that causes impact. Sometimes other controls stop it. Sometimes we bypass those controls. This needs constant dialogue. It's what we do. It's what we've been doing today.</p><p>We understand the constraints. We know what techniques are safe, which systems you don't touch, and the consequences of getting it wrong. </p><p>But here's the thing that really gets me.</p><p>The people who build and maintain OT systems are not always best positioned to break them. That's not a criticism - it's a different skillset. But the engineers who design, commission and maintain these systems are aiming to keep them operational. They think within what the manufacturer says is possible. They assume implementation matches design. They follow safety engineering, not security engineering. </p><p>We work outside what people think is possible and challenge those assumptions.</p><p>I don't know what would have convinced this person. But the industry has a real problem gatekeeping OT security behind a narrow idea of what "OT experience" looks like. If your only measure is whether someone has spent 20 years configuring PLCs, you're missing the people best placed to find the vulnerabilities in them.</p><p>The best security testing combines operational knowledge from people on site with adversarial thinking from testers who break things. That's not a gap in our capability. That's the whole point.</p>]]></description><link>https://board.circlewithadot.net/topic/7d9da6d7-3548-4c34-b26b-3e8a77943a60/had-a-call-the-other-day-that-properly-wound-me-up-and-i-think-it-s-worth-talking-about.</link><generator>RSS for Node</generator><lastBuildDate>Mon, 06 Apr 2026 20:22:39 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/7d9da6d7-3548-4c34-b26b-3e8a77943a60.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 04 Apr 2026 18:49:11 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Had a call the other day that properly wound me up, and I think it&#x27;s worth talking about. on Sat, 04 Apr 2026 21:05:54 GMT]]></title><description><![CDATA[<p><span><a href="https://infosec.exchange/@cybergibbons">@<span>cybergibbons</span></a></span> as the “network guys” we didn’t understand OT. In some cases that was true but certainly not all.</p>]]></description><link>https://board.circlewithadot.net/post/https://infosec.exchange/users/Wifiwits/statuses/116348469561868322</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://infosec.exchange/users/Wifiwits/statuses/116348469561868322</guid><dc:creator><![CDATA[wifiwits@infosec.exchange]]></dc:creator><pubDate>Sat, 04 Apr 2026 21:05:54 GMT</pubDate></item></channel></rss>