SCADA & Manufacturing Security
Industrial systems are critical infrastructure. We secure OT environments against cyber-physical attacks.
Who this is for
Product, firmware and operations teams shipping physical or connected systems, where a security problem has consequences you cannot patch remotely.
Methodology
What We Test
- SCADA systems, HMIs (Human-Machine Interfaces), and PLCs
- Industrial protocols (Modbus, DNP3, BACnet, OPC UA)
- OT/IT network segmentation and air gaps
- Historian databases and engineering workstations
- Wireless connectivity in plant environments
- Embedded web servers and management interfaces
How We Test
We prioritize safety and operational continuity. We perform passive network analysis to map assets and protocols without disrupting processes. We test non-critical environments or replicas for active exploitation. We validate segmentation controls and assess physical security risks.
What You Receive
- Network topology map and asset inventory
- Identification of insecure protocols and weak auth
- Segmentation verification report
- Hardening guide for OT specific equipment
How an engagement runs
-
Scope, authorisation & safety constraints
We agree the target hardware or environment, the tests permitted on it, and the safety and operational limits before anything is powered on. Nothing starts without written authorisation from someone able to give it.
-
Samples, access & environment
We confirm what you supply — devices or samples, firmware and hardware revisions, bench or lab access, interfaces and credentials — and agree in writing whether work may be invasive or destructive, and how samples are returned or disposed of.
-
Passive analysis first
We start with observation, documentation review and passive analysis so we understand the system before touching anything that could affect it. On operational technology this stage carries the most weight.
-
Controlled active testing
Active testing happens on a bench, a replica or an agreed non-operational window — never against live production or safety-critical operations without explicit written approval and your engineers present.
-
Report & walkthrough
You get an executive summary and technical detail covering what we proved, what held, what could not be tested safely, and why. We walk your team through it.
-
Retest
Fixes are retested against the same samples or environment where that is practical. Retest scope is agreed in your scope document before the engagement begins.
Toolkit
- GrassMarlin
- Claroty
- Nozomi
- Custom Scripts