OTPentest

OT/ICS penetration testing · Safety first

Find the path to your control systems before an attacker does

Practical OT/ICS penetration testing and security assessments for asset owners, utilities, manufacturers, vendors and integrators. Real attacker techniques, tested without putting your process, your people or your uptime at risk.

  • Never in productionTesting stops before anything can touch the process. Phase 2 attacks happen in a lab.
  • A public methodologyBuilt on the free OT Penetration Testing Framework.
  • Plain-language resultsWritten for the plant floor and the boardroom, aligned to ISA/IEC 62443.

Services

What we test

Every engagement is scoped around your process and what must never be disrupted. Pick one service, or combine them.

OT penetration testing

An assumed-breach test that starts on your IT network and shows how far an attacker could get toward your control systems: through the IT/OT DMZ, onto level 3, and up to the point of interacting with an HMI, SCADA system or PLC. In production, that's where testing stops.

  • IT-to-OT attack paths and the IT/OT boundary
  • Engineering workstations, historians and Windows-based HMIs
  • Credentials, remote access and trust relationships
  • Clear stop points agreed with operations

External exposure assessment

A passive look at what the internet already knows about your facilities, including exposed OT services, remote access portals and leaked details about your control system stack. Nothing is sent to your industrial assets.

  • Internet search engine and OSINT review
  • Exposed OT/ICS protocols and HMIs
  • Vendor and integrator footprint
  • A short, prioritized fix list

Lab & test bed testing

The techniques nobody should run in production, such as writing to PLCs, manipulating logic and attacking safety functions, tested safely on your test bed, spare equipment, FAT/SAT systems or during a planned outage.

  • PLC, HMI and engineering software attack paths
  • Unauthenticated protocol abuse (Modbus, S7, EtherNet/IP, DNP3 and more)
  • Inhibit Response Function and Impair Process Control scenarios
  • Vendor systems before they go live

Segmentation & boundary testing

Do your zones and conduits actually do what the drawings say? A focused test of firewall rules, the DMZ, dual-homed hosts and remote access paths between IT and OT.

  • Firewall and conduit rule validation
  • Jump host and vendor remote access review
  • Paths that bypass the DMZ
  • Findings mapped to the Purdue Model

An honest note

Most OT environments don't need a pentest first

Demand for OT penetration testing is limited, most operations can't afford one, and many "OT pentests" turn out to be IT pentests that stop at the OT boundary. A lot of organizations get more value from a risk assessment or a maturity assessment.

If a pentest isn't the right next step for you, you'll hear that on the first call, along with what would help more.

Good reasons to test

  • You've invested in segmentation and want proof it works
  • A new system, site or vendor connection is going live
  • Leadership or an insurer needs evidence of real-world risk
  • You want your defenders to see an attack chain end to end

Approach

How an engagement runs

Each step follows the OT Penetration Testing Framework and is built around one rule: safety and availability come first.

  1. Understand the environment

    Before anything is touched, we learn the process, the architecture, the critical functions and what must never be disrupted.

  2. Scope it with operations

    Scope, rules of engagement, stop points and written authorization are agreed with the asset owner, engineering and operations, not just IT.

  3. Passive first

    Start with what can be learned without sending a packet: documentation, OSINT and passive traffic analysis.

  4. Controlled testing

    Active testing only where it's agreed safe. Anything that could touch the process moves to a lab, a test bed or a planned outage.

  5. Report in plain language

    An executive summary for leadership and operator-friendly findings for the plant, mapped to the Purdue Model and aligned to ISA/IEC 62443.

  6. Fix, then retest

    A prioritized action plan your team can actually work through, and a retest to confirm the fixes hold.

Who you work with

Mike Holcomb

Mike Holcomb (GRID, CISSP, GPEN, ISA/IEC 62443) is an OT/ICS cybersecurity practitioner and educator, and the creator of the OT Penetration Testing Framework. He's the author of the upcoming A Practical Guide to OT/ICS Penetration Testing, and he has published more than 60 hours of free OT/ICS training on YouTube.

More than 100,000 practitioners follow his work on LinkedIn and YouTube. Testing is delivered through UtilSec, LLC.

More about Mike

What you get

  • An executive summary leadership can act on
  • Findings written in operator-friendly language
  • Findings mapped to the Purdue Model and aligned to ISA/IEC 62443
  • A prioritized action plan
  • Retesting to confirm fixes

FAQ

Common questions

Will you test our production systems?

Not in any way that could affect safety or availability. In production, testing stops once the tester is in a position to interact with control systems. Anything beyond that point is done in a lab, on a test bed or during a planned outage, with engineering and operations involved.

Do we actually need a penetration test?

Maybe not. Most OT environments get more value from a risk assessment or a maturity assessment first. If that's true for you, you'll hear it on the first call.

How long does an engagement take?

It depends on the scope and the number of sites. An external exposure assessment is usually quick. An assumed-breach test or test bed engagement takes longer. You'll get a clear timeline before anything starts.

What do you need from us?

A technical point of contact, someone from operations who can make the call on stop points, network drawings and asset lists if you have them, and written authorization from the asset owner.

What methodology do you use?

The OT Penetration Testing Framework, an 11-phase attack chain from reconnaissance to impact that lines up with MITRE ATT&CK for ICS. It's free and public, so you can see exactly how testing works.

Do you work with vendors and integrators?

Yes. Testing a system before it ships or before it's commissioned is one of the safest and most useful times to find problems.

Let's talk about your environment

Tell Mike about your site, your process and what you're worried about. The first conversation is free and there's no obligation.

Message Mike on LinkedIn