Penetration Testing/ICS & OT Penetration Testing
ICS, SCADA & OT Penetration Testing

ICS and SCADA penetration testing that respects the process you run

Carefully scoped testing of your industrial control systems, OT networks and IIoT devices, planned around safety and uptime. Every finding comes with evidence of how it was reached and a fix your engineers can apply.

  • IT-to-OT segmentation, zones and conduits
  • Remote access, jump hosts and vendor connections
  • PLCs, HMIs, engineering workstations and historians
  • Mapped to IEC 62443 and MITRE ATT&CK for ICS
The credentials behind every engagement
CREST-accredited for penetration testingISO/IEC 27001 certifiedSOC 2 Type 2 attested
2026 CyberSecurity Breakthrough Awards winnerG2 High Performer, Fall 2026
Penetration Testing Solution of the Year2026 CyberSecurity Breakthrough Awards

Reviewed by Omair Manzoor, Founder & CEO, ioSENTRIX · Updated

Key terms: What is SCADA security?

Trusted by security teams at
See it in action

Can your office network reach your controllers?

We trace the path from one office laptop to the plant floor. We observe before we touch, and prove writes only on a lab unit.

Swipe to see the full exhibit →

Most OT paths start in IT

Firewall rules, shared servers and shared passwords connect the office to the plant.

Safety comes first

Passive capture on live networks, active steps in agreed windows, writes on a lab unit.

Every path closed

Each finding maps to IEC 62443 with a fix, and we retest the conduit once it is filtered.

Read this exhibit as text
  1. The test starts from one office laptop on the enterprise IT network (Purdue levels 4 and 5).
  2. A firewall rule lets the IT network reach a patch server in the IT/OT DMZ.
  3. A shared password opens the engineering workstation at the supervisory level.
  4. The controller accepts Modbus/TCP writes with no login.
  5. On a lab PLC, not the live process, we write a setpoint of 98% to prove the impact. The live tank is never touched.
  6. After the fix, the IT/OT conduit is filtered to named flows only, and a retest confirms the path is closed. Findings map to IEC 62443-3-3, MITRE ATT&CK for ICS and NIST SP 800-82.

Source: ioSENTRIX OT testing methodology; IEC 62443-3-3; MITRE ATT&CK for ICS. Illustrative path at a fictional site, not client data.

The short answer

What is ICS penetration testing?

ICS penetration testing is a controlled security test of industrial control systems and the operational technology (OT) networks they run on, such as SCADA servers, PLCs, HMIs and historians. Testers check whether an attacker could reach and influence the process from IT, remote access or the plant floor, without disrupting operations.

OT penetration testing differs from IT testing because safety and availability come first. Active techniques are agreed in advance, fragile devices are tested in a lab or a maintenance window, and passive methods are used on live networks. Findings map to IEC 62443 system requirements and MITRE ATT&CK for ICS, so engineering and security teams share one view.

At ioSENTRIX, ICS and OT penetration testing is carried out by certified testers at a CREST-accredited firm, with test methods agreed with your engineers in advance and a free retest of every fix.

You need an OT pentest if

  • Your IT and OT networks are connected, directly or through a DMZ
  • Vendors or staff reach OT systems remotely
  • An insurer, customer or regulator asked for OT security evidence
  • You are working toward IEC 62443 security levels for a site or product
What we test

Four layers, tested with care

Scope follows your sites and zones. Most ICS penetration tests cover these four areas.

Layer 1

IT/OT boundary

Whether an attacker on the corporate network can reach the plant.

  • Segmentation & firewall rules
  • DMZ, historians & shared services
  • Shared accounts & directory trust
  • Zone & conduit enforcement
Layer 2

Remote access

The routes vendors and staff use to reach OT systems.

  • VPN & jump host configuration
  • Vendor remote support paths
  • Multi-factor authentication
  • Session approval & recording
Layer 3

Control network

What an attacker could do once inside the OT network.

  • Engineering workstation security
  • HMI & SCADA server hardening
  • Unauthenticated industrial protocols
  • PLC access & logic change controls
Layer 4

IIoT & field devices

Connected sensors, gateways and the services behind them.

  • IIoT gateway firmware & services
  • Device-to-cloud authentication
  • Wireless field networks
  • Default & shared credentials
Methodology

How we test: example test cases

A sample of the test cases in a typical OT penetration test, labeled by IEC 62443-3-3 system requirement. Your scope and safety plan decide the full list.

SR 5.1

Network segmentation

From a corporate workstation, we map which OT hosts and ports are reachable and compare that with the intended zone design.

SR 5.2

Zone boundary protection

We test firewall and DMZ rules between zones, including paths through historians, file shares and patch servers.

SR 1.1

Remote access authentication

We test VPNs, jump hosts and vendor portals for weak, shared or single-factor logins.

SR 2.1

Authorization on engineering tools

With a standard operator account, we test whether we can change setpoints, download logic or alter HMI screens.

SR 3.4

Software and logic integrity

On a lab unit or in an agreed window, we check whether controller logic and firmware changes are detected, signed or logged.

SR 1.5

Default and shared credentials

We check HMIs, PLCs, switches and IIoT gateways for vendor default and shared passwords.

Sample finding

What a finding looks like in our report

An illustrative example in our report format. Not client data.

Finding 01 · IllustrativeCritical

Shared vendor VPN account reaches the engineering workstation without multi-factor authentication

IEC 62443-3-3 SR 1.1 Human user identification and authentication · SR 5.2 Zone boundary protection

What we found

A vendor support VPN used one shared account with a password and no second factor. Once connected, the session landed in a segment with direct access to the engineering workstation, which held the project files and software used to program the PLCs.

Impact

Anyone with the vendor password could reach the tools used to change controller logic on the production line.

How to fix it

Give each vendor user a named account with multi-factor authentication. Route remote sessions through a jump host in the DMZ with approval and session recording, and block direct routes from remote access into the control zone.

What you get

What you get from every OT pentest

Not an alert feed. Proven attack paths into your process, with fixes your engineers can plan around.

1

Findings with evidence, ranked by risk to the process

Each finding has a severity, evidence of how it was reached and remediation guidance your engineers can apply in a maintenance window.

2

Mapped to IEC 62443 and MITRE ATT&CK for ICS

Findings map to IEC 62443-3-3 system requirements and ATT&CK for ICS tactics, so engineers, security teams and auditors read the same report.

3

Walkthrough, then retesting

The tester who found each issue walks your engineers through it, and retesting is available once fixes land.

ioSENTRIX sample penetration test report cover

See how we write findings before you talk to us

A redacted sample penetration test report (web application): finding write-ups, proof-of-concept evidence and remediation. No form required.

Download the sample report (PDF) →
Systems we test

SCADA, PLC and OT security testing across your plant

From the office network to the controller, tested with safety rules your operations team agrees first.

SCADA

SCADA penetration testing

SCADA servers, historians and operator HMIs, tested for who can see and change what the operators see.

  • Authentication and roles
  • Exposed services and patch level
  • Historian and database access
  • Paths into the control network
Controllers

PLC and RTU security testing

Whether controllers accept unauthenticated reads, writes or logic downloads. Active tests run on lab units or in agreed windows.

  • Modbus/TCP and DNP3
  • S7comm and EtherNet/IP
  • Logic download and change control
  • Firmware and project files
Workstations

HMI and engineering workstation testing

The machines that program and operate the plant, where one weak password can mean control of the process.

  • Shared and default accounts
  • Engineering software and projects
  • Removable media controls
  • Hardening and patching
Segmentation

IT/OT segmentation testing

Whether the corporate network can reach the plant, tested against your IEC 62443 zones and conduits.

  • Firewall and DMZ rules
  • Shared servers and file paths
  • Directory trust
  • Named flows only
Remote access

OT remote access and vendor testing

The VPNs, jump hosts and vendor tools that reach OT systems from outside the site.

  • VPN and jump host setup
  • Vendor accounts
  • Multi-factor authentication
  • Session approval and recording
IIoT

IIoT security testing

Industrial IoT gateways, sensors and the cloud services they report to.

  • Gateway firmware and services
  • Device-to-cloud authentication
  • Default credentials
  • Wireless links
Assessment

OT security assessment

A review of your OT architecture and controls against IEC 62443 and NIST SP 800-82, using passive traffic analysis on live networks.

  • Asset and flow inventory
  • Zone and conduit review
  • Remote access review
  • Prioritized fix plan
Water and energy

Utility and critical infrastructure testing

Water, power and building systems, tested with the same safety rules as any plant.

  • Passive capture first
  • Agreed test windows
  • Lab-only writes
  • IEC 62443 mapping

SCADA and OT testing questions

What is SCADA penetration testing?

SCADA penetration testing is a controlled test of the supervisory systems that monitor and control an industrial process, such as SCADA servers, HMIs and historians, and the networks and protocols that connect them to PLCs. It shows whether an attacker could view or change the process, using passive methods on live systems and active steps only in agreed windows.

What is the difference between an OT security assessment and an ICS penetration test?

An OT security assessment reviews architecture, segmentation, remote access and controls against a standard such as IEC 62443, often using passive traffic analysis. An ICS penetration test goes further and tries to prove an attack path, for example from the office network to a controller, with evidence for each step. Many teams start with an assessment and follow with a targeted test.

Do you test PLCs directly?

Yes, with care. We test controllers for unauthenticated access and logic changes on a lab unit or spare, or on live equipment only inside an agreed window with stop conditions. We do not write to a controller running the live process unless your operations team has approved it.

Verified reviews

What security leaders say about working with us

★★★★★
“Unlike other providers, Omair and his team truly dive deep into our infrastructure, delivering findings that go well beyond the surface level. Communication is direct and seamless.”
Jesus B.
Cybersecurity Manager, Banking
Verified G2 review ↗
★★★★★
“We were impressed with ioSENTRIX’s ability to independently validate the security of our customer-facing product.”
Zeehasham R.
Data Scientist, Security Operations · Fortune 500 insurer
Verified Clutch review ↗
★★★★★
“The team at ioSENTRIX is professional and highly skilled at their craft.”
Awwab A.
SVP, Chief Information Security Officer
Verified G2 review ↗
How it works

How an ICS penetration test works

Four steps, so you know what happens and what you get.

01

Scope and safety plan

We agree targets, allowed techniques, test windows and stop conditions with your engineering and operations teams.

Start
02

Testing

Testers work from IT, remote access and the plant network, using passive methods on live systems and active tests only where agreed.

Most of the engagement
03

Report

Each finding has a severity, evidence of the attack path and remediation guidance.

At close
04

Remediation support

We walk your engineers through the findings, and retesting is available once fixes land.

After fixes
Reply in under an hour → scoping call → fixed quote in writing → testing, by scope → report, walkthrough and retest
How we compare

Not an IT pentest pointed at a plant. Not a passive inventory tool.

What an ICS penetration test covers compared with the usual alternatives.

ioSENTRIX ICS / OT pentest
OT asset visibility tool
Standard IT network pentest
What is tested
IT/OT boundary, remote access, control network and IIoT
Assets and traffic it can see
IT network; OT out of scope
Safety planning
Techniques, windows and stop conditions agreed in advance
Mostly passive
Not designed for OT
Attack paths
IT-to-OT and vendor paths tested by hand
Inferred from traffic
IT side only
Evidence
Evidence of each path and a fix
Alerts and inventory
Finding list
Standards
IEC 62443, MITRE ATT&CK for ICS
Varies by tool
PTES, NIST SP 800-115
Scope and price

What affects the scope and price of an ICS pentest

OT tests are priced on effort. These are the decisions that move the quote.

What moves the quote

  1. 01How many sites, zones and control systems are in scope
  2. 02Whether testing happens on live systems, a lab or a test bench
  3. 03The industrial protocols and vendors in your environment
  4. 04Remote access paths and third-party connections
  5. 05Whether IIoT devices and cloud services are tested in the same engagement
  6. 06On-site work, test windows and the evidence you need afterwards
Read: Penetration Testing Cost & Pricing in 2026: What a Pentest Really Costs →

What we need from you to start

  • Network diagrams showing zones, conduits and remote access
  • An asset list, even a partial one
  • Agreed test windows and an operations contact who can stop testing
  • Lab or spare equipment for active tests, where available
  • Site access and safety induction requirements for on-site work
Scope my OT test
Track record

Numbers you can check

Ratings you can verify on G2 and Clutch.

G2
4.9 / 5
on G2 from 12 verified reviews
Clutch
5.0 / 5
on Clutch, Premier Verified
CREST-accredited for penetration testing
2017
founded; CREST-accredited, ISO 27001 certified, SOC 2 Type 2 attested
Independently verified

Credentials held by the firm

Every engagement runs inside a company whose methods and own security are checked by outside bodies.

CREST-accredited for penetration testing

CREST-accredited for penetration testing

CREST assesses the firm's testing methodology, quality assurance and handling of client data.

View our CREST listing →
SOC 2 Type 2 attested

SOC 2 Type 2 attested

An independent auditor tested our own security controls over time.

Request the SOC 2 report →
ISO/IEC 27001 certified

ISO/IEC 27001 certified

Our information security management system is certified to ISO/IEC 27001.

View in our trust center →
2026 CyberSecurity Breakthrough Awards winnerG2 High Performer, Fall 2026

Recognized independently

Penetration Testing Solution of the Year, 2026 CyberSecurity Breakthrough Awards. G2 High Performer, Fall 2026.

Founded in 2017.

Our commitments

What you can count on

Four promises we make on every testing engagement.

  • Free retest of every fixOnce your team fixes a finding, we test it again at no extra cost and update the report.
  • A fixed priceThe quote you sign is what you pay. The price only changes if you change the scope.
  • A report your auditor acceptsIf your auditor has questions about the report, we answer them and update it until it is accepted.
  • A reply in under an hourSend the form and we reply within an hour during US business hours.
For your buying team

Everything your reviewers will ask for

Security, finance and procurement each need something different. Forward this page, or pull what each reviewer needs.

For security

Sample report

See exactly what you get: findings, proof of concept, fixes and retest results.

Download the sample report (PDF) →
For vendor risk

Trust center

Our SOC 2 Type 2 report and security documentation for your vendor review.

Open the trust center →
For procurement

Procurement pack

Master services agreement, sample statement of work, certificate of insurance and W-9.

Request the procurement pack →
For your team

Share this page

Send the link to the people who need to sign off.

Who you work with

Who does the work

Senior security engineers do the hands-on work and write up the results, so the person who found an issue explains it to your team.

Certified engineers

Each engineer holds one or more of OSCP, OSWE, OSCE, CISSP, CISA or AWS security certifications.

Accredited firm

ioSENTRIX is CREST-accredited for penetration testing, ISO/IEC 27001 certified and SOC 2 Type 2 attested.

Since 2017

Founded in 2017, with security work for Fortune 100, financial services, insurance and SaaS companies.

Ready to find out whether IT can reach your plant floor?

We reply in under an hour · no sales pitch

Scope my OT test
Standards

Frameworks we test and map to

◆IEC 62443-3-3◆IEC 62443-3-2◆IEC 62443-4-2◆MITRE ATT&CK for ICS◆NIST SP 800-82 Rev. 3◆NIST SP 800-115
FAQ

Frequently asked questions

Is it safe to penetration test an OT environment?

It can be, when the test is planned for OT. We agree allowed techniques, test windows and stop conditions with your operations team, use passive methods on live control networks, and run active tests against lab equipment or in maintenance windows.

What is IEC 62443?

IEC 62443 is a series of standards for securing industrial automation and control systems. Part 3-2 covers risk assessment and dividing a system into zones and conduits, part 3-3 sets system security requirements and security levels, and part 4-2 sets requirements for components such as devices and software.

Do you test IIoT devices?

Yes. IIoT gateways and sensors are tested for firmware weaknesses, default credentials and insecure connections to the cloud. For deeper hardware and firmware work, see our IoT and embedded device penetration testing.

Do you test remotely or on site?

Many tests start remotely, from the corporate network or through the same remote access vendors use. Some work, such as testing field devices or isolated networks, needs a site visit. We agree the approach during scoping.

How long does an OT penetration test take?

Most OT tests run days to weeks, depending on sites, zones and test windows. Maintenance windows often set the pace. We reply in under an hour during US business hours, and the scope, timeline and fixed quote follow the scoping call.

Ready when you are

Find the path to your process before an attacker does

Tell us about your sites, systems and remote access. We will scope a safe test and send a fixed quote based on effort.

We reply in under an hour · Fixed quote in writing before work starts · Your details are never shared