Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Security testing in industrial environments is bounded by the risk of disrupting production or safety, so assessments rely on passive analysis, replica systems, and tightly agreed rules of engagement.

What Are Testing Limits in OT Environments?
The first thing an experienced industrial tester does on arriving at a plant is explain what they are not going to do. In a corporate network, a vulnerability scan is routine background noise. On a control network, the same scan has a documented history of faulting controllers, tripping protection relays, and stopping production lines. Testing limits in OT are the agreed boundaries that let a meaningful assessment happen without becoming the incident it was commissioned to prevent.
None of this is theoretical. CISA and vendor advisories have repeatedly warned that active scanning of control networks can cause loss of availability, and most asset owners can tell you about the time somebody found out.
The document that makes OT testing safe is not the methodology, it is the rules of engagement, and it should be signed by the plant manager as well as by the security sponsor. Workable rules name the IP ranges and devices that are in scope and, explicitly, those that are out; list the techniques permitted at each Purdue level; require an engineer with plant knowledge to be present or reachable for every active step; define a stop condition and a single person who may invoke it; set the window, usually a planned outage or low-demand period; and record the agreed rollback for each action.
Two further conventions matter. Never test safety-instrumented systems actively on a live plant — ever. And treat any unexpected process behaviour, however unrelated it seems, as a stop event until the engineering team says otherwise. Coverage is always negotiable; the plant is not.
A good industrial assessment is explicit about its own gaps. If the control layer was examined passively only, say so, state what that technique can and cannot reveal, and recommend how the gap could be closed — typically through bench testing at the next equipment refresh or during a factory acceptance test. Regulators assessing operators of essential services against the NCSC’s Cyber Assessment Framework are looking for evidence that risk is understood, and a report that distinguishes verified findings from reasoned inference is far more credible than one that implies full coverage.
At Privia Security, our OT-SCADA Penetration Test is built around these constraints rather than apologising for them, with every active step agreed in writing with your engineers before it happens.
On the Windows and server layer above the controllers, yes, with agreed timing. On a control network containing PLCs, relays, or field devices, treat it as prohibited unless the specific devices have been bench tested and engineering has approved it in writing. Even a slow scan can exhaust connection tables on older equipment.
Combine passive analysis, configuration review, and bench testing on identical hardware. Passive capture reveals what is really on the network; configuration review finds the gaps in segmentation and access control; the bench proves whether a device is exploitable. Together they produce a stronger picture than a scan of a live plant ever would.
During factory acceptance testing, before anything is live, which is when active techniques are free of consequence. After that, planned outages and turnarounds offer the next best window. Testing a running plant should be reserved for passive and review-based work plus whatever the layers above the control network will tolerate.
The person accountable for the process, usually the shift or plant manager, and they should be able to stop it instantly without discussion. Name them and their deputy in the rules of engagement, agree how they will be contacted, and make clear that invoking the stop carries no need to justify it at the time.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.