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.