How to Scope an OT Penetration Testing as a Service Program

How to Scope an OT Penetration Testing as a Service Program
An effective OT penetration testing as a service program starts with a precise scope. Define the operational objectives, critical assets, safety boundaries, required data, attack scenarios, evidence standards, deliverables, and reassessment terms before testing begins.
The goal is not to run as many tests as possible. It is to determine which credible attack paths can reach critical systems, whether existing controls interrupt those paths, and which actions can reduce risk without destabilizing operations.
A generic IT statement of work is rarely sufficient. OT environments include legacy systems, specialized protocols, long equipment lifecycles, and dependencies that may not tolerate conventional testing.
This guide provides a practical framework for defining the scope.
What should OT penetration testing as a service include?
OT penetration testing as a service is a managed assessment that identifies and validates exploitable paths affecting industrial environments. A well-scoped service connects technical findings to operational consequences instead of delivering an isolated vulnerability list.
The program should define:
- Facilities, environments, zones, and asset classes under assessment
- Critical operations and consequences to consider
- Architecture and security data used to model the environment
- Adversary behaviors and attack paths to evaluate
- Production safety constraints governing execution
- Controls whose effectiveness will be validated
- Technical, engineering, and executive deliverables
- The process for remediation validation and reassessment
Asset visibility and vulnerability scanning do not prove that an attacker can reach a critical OT asset. Penetration testing should add context about exploitability, connectivity, controls, and consequences.
1. Define business and operational objectives
Begin with the decisions the assessment must support. A request to “test the OT network” is too broad to guide a safe and useful engagement.
More useful objectives include:
- Determine whether credible paths reach designated critical OT zones
- Validate whether segmentation controls restrict unintended pathways
- Identify exploitable combinations of vulnerabilities and control gaps
- Evaluate whether existing safeguards interrupt modeled adversary activity
- Prioritize remediation according to reachable operational consequences
- Establish a baseline for measuring attack-path reduction over time
Assign an owner and an expected decision to each objective. For example, an engineering leader may need evidence to approve a firewall rule change. A CISO may need a defensible view of risk across multiple sites.
Also define what the engagement will not claim. Document incomplete source data, excluded facilities, and unmodeled asset classes as limitations. Do not treat them as implicit coverage.
2. Identify critical assets and operational consequences
Work backward from what the organization cannot afford to lose. Ask operations, engineering, safety, and security stakeholders to identify systems and functions associated with unacceptable consequences.
Relevant categories may include:
- Safety-related systems
- Controllers and process control equipment
- SCADA servers and operator workstations
- Engineering systems
- Historians and supporting infrastructure
- Boundary security controls
- Systems supporting essential production or service delivery
Do not rank targets by technical severity alone. A moderate weakness on a reachable system may matter more than a critical vulnerability on an isolated asset.
Define the consequences that will guide prioritization. These may include:
- Loss of view
- Loss of control
- Interruption of a critical process
- Equipment stress
- Environmental or safety impact
These criteria give stakeholders a shared language for prioritization. They also prevent the final report from becoming a vulnerability inventory without operational context.
3. Set safe testing boundaries
Document safety constraints before execution begins. Traditional testing techniques can create unacceptable risk when applied directly to fragile or availability-sensitive OT systems.
The scope should state:
- Whether testing will use simulation, controlled live validation, or both
- Which systems and techniques are excluded from live interaction
- Approved assessment windows and coordination requirements
- Conditions that require work to pause
- Stakeholders authorized to approve scope changes
- Evidence handling and reporting requirements
- Assumptions used when direct validation is not appropriate
For many environments, a cyber digital twin provides a safer foundation. Architecture, asset, configuration, vulnerability, and control data can be assembled into a model. Adversary techniques and attack paths can then be evaluated without testing production systems directly.
The provider should explain which data supports the model, where assumptions were required, and how model confidence affects each conclusion. For more context, see how digital twins enable safe OT security testing.
4. Specify the data needed for the assessment model
Perfect visibility should not be a prerequisite, but the data requirements must be clear. A service provider should be able to ingest available OT data and identify material gaps without presenting partial input as full coverage.
Potential sources include:
- Network diagrams and zone definitions
- Asset inventories and asset attributes
- Network flow and communication records
- Firewall configurations and policy exports
- Vulnerability and configuration findings
- Existing assessment results
- Security architecture documentation
- Known criticality and consequence classifications
The statement of work should identify:
- Mandatory and optional data
- Acceptable formats
- Data owners
- Validation steps
- The process for reconciling conflicting sources
The result should be more than an asset list. It should be a high-fidelity model of assets, relationships, trust boundaries, vulnerabilities, and controls that supports attack-path analysis. This is why asset visibility alone is not enough.
5. Define the attack paths and adversary behaviors to test
State which paths and behaviors the provider will evaluate. Without this detail, “comprehensive testing” can mean different things to the provider, security team, and plant stakeholders.
Define scenarios according to:
- Critical destinations and operational consequences
- Known architecture and trust relationships
- Relevant adversary behaviors
- Vulnerabilities with plausible exploit conditions
- Security controls expected to prevent or interrupt progression
- Threat intelligence applicable to the organization and sector
Include end-to-end analysis where the available data supports it. Testing isolated vulnerabilities does not show whether multiple weaknesses can be chained into a consequential path.
MITRE ATT&CK for ICS can provide a useful vocabulary. However, technique coverage should not be the only measure of success. The more important question is whether a realistic sequence could reach a critical objective in the specific environment.
6. Define evidence and prioritization requirements
Do not accept AI-generated conclusions without supporting evidence. Require the provider to explain why an attack path is considered viable and which conditions must be present for it to succeed.
For each prioritized path, request:
- The originating condition and targeted critical asset or zone
- The sequence of assets, vulnerabilities, and control boundaries involved
- Evidence supporting each step
- Exploitability assumptions and confidence levels
- Existing controls expected to interrupt the path
- The potential operational consequence
- Recommended mitigation and compensating control options
Prioritization should consider reachability, exploit conditions, control effectiveness, asset criticality, and potential consequences. CVSS or vulnerability count alone should not determine the remediation queue.
For a deeper treatment of this issue, review exploit conditions in OT vulnerability prioritization.
7. Require deliverables for engineering and leadership
A useful engagement should produce outputs tailored to the people who must act on the results.
Technical and engineering deliverables
- Validated or evidence-supported attack-path diagrams
- A prioritized list of exploitable conditions
- Affected assets, zones, and control boundaries
- Supporting evidence and assumptions
- Engineering-relevant mitigation options
- Retest criteria for each priority finding
Program and executive deliverables
- A summary of material operational risk
- Critical paths and potential consequences
- Control strengths and weaknesses
- Scope coverage and known limitations
- Prioritized investment recommendations
- Baseline metrics for future assessments
Ask the provider to distinguish among facts, modeled conclusions, and assumptions. Transparent reasoning makes AI-supported analysis easier for security and engineering teams to review.
8. Establish measurable acceptance criteria
Evaluate the engagement against agreed outcomes, not report length.
Useful acceptance criteria include:
- Percentage of designated critical zones represented in the model
- Number of critical paths evaluated and supported by evidence
- Percentage of prioritized findings mapped to an owner
- Number of paths interrupted after remediation
- Change in reachable critical assets between assessments
- Time from a validated finding to a mitigation decision
- Percentage of findings successfully reassessed
These measures shift attention from finding volume to proven risk reduction. They also give leadership a consistent way to track improvement across sites and assessment cycles.
9. Plan remediation validation and reassessment
A one-time assessment can establish a baseline, but industrial environments change. New vulnerabilities, architecture changes, configuration drift, and evolving adversary behavior can create new paths or reopen old ones.
Define the follow-up process during initial scoping:
- Assign owners to validated findings.
- Select remediation or compensating controls.
- Update the model with the planned changes.
- Reassess affected attack paths.
- Record whether each path was interrupted or merely altered.
- Schedule broader reassessment based on risk and environmental change.
This approach turns penetration testing as a service into a validation cycle instead of a periodic reporting exercise. It complements existing teams and controls by showing where remediation work can have the greatest effect.
Questions to ask an OT penetration testing provider
Use these questions during provider evaluation and scope review:
- How is your methodology purpose-built for OT rather than adapted from IT testing?
- How do you prevent assessment activity from affecting production systems?
- Which data sources do you require, and how do you handle incomplete data?
- How do you validate complete attack paths instead of listing vulnerabilities?
- How do you account for asset criticality and operational consequences?
- What evidence supports each prioritized finding?
- How are assumptions and confidence levels documented?
- Which deliverables are designed for engineering teams?
- How do you validate that remediation interrupted a path?
- Can the assessment be repeated as architecture, threats, and controls change?
A provider should answer these questions precisely. Broad promises of complete coverage are not a substitute for documented inputs, boundaries, methods, and limitations.
OT penetration testing scope checklist
Before approving the engagement, confirm that the scope includes:
- [ ] Named facilities, zones, and asset classes
- [ ] Defined critical operations and consequences
- [ ] Business and technical objectives
- [ ] Documented data sources and known gaps
- [ ] Safety constraints and excluded activities
- [ ] Specified attack scenarios and critical destinations
- [ ] Evidence and confidence requirements
- [ ] Exploitability-based prioritization criteria
- [ ] Engineering and executive deliverables
- [ ] Acceptance metrics
- [ ] Remediation ownership
- [ ] Reassessment and retesting terms
The broader OT penetration testing checklist can support preparation before, during, and after an engagement.
Scope for proof, not finding volume
The best OT penetration testing as a service scope asks four focused questions:
- Which paths can reach critical systems?
- What evidence shows that those paths are viable?
- Which controls can interrupt them?
- What should the organization fix first?
Frenos uses agnostic data ingestion, cyber digital twins, AI-powered adversary simulation, and evidence-based attack-path validation to assess OT defenses without testing live production systems. The goal is not to replace existing security tools or teams. It is to turn fragmented findings into operational context and defensible remediation priorities.
Request a demo to see attack paths in your OT environment and assess defenses without production impact.
Related links
- Blogs - Critical Infrastructure OT Incident Response: A Practical Playbook for Industrial Environments Build an OT incident response plan for industrial environments with practical steps for preparation, safe containment, evidence collection, recovery, ransomware, and controller changes. Read more
- Blogs - NOV 04, 2026 Critical PHP Vulnerabilities: What They Mean for OT Security Two PHP flaws rated CVSS 9.2 raise urgent questions for OT teams. Learn how to check if you’re affected, if attackers can reach it, and how to respond. Read more
- Blogs - NOV 04, 2026 When to Move From Annual OT Penetration Testing to a Service Model Learn when annual OT testing is no longer enough and how penetration testing as a service enables safe, continuous attack-path validation. Read more


