Energy
|CS.110
IT and OT Device Security Testing
Security testing of SCADA, PLC, smart meter and industrial router devices in 3 sectors - 50+ vulnerabilities reported to vendors.
Client
Industrial device vendors and operators (mining, energy, automation)
Challenge
Industrial device vendors and operators wanted an independent check of whether their products would withstand attack: from SCADA systems and controller firmware to energy devices, PLCs and OT firewalls.
Approach
Penetration testing
White-box and black-box security testing of devices from the mining, energy, and industrial automation sectors.
Firmware and hardware analysis
Device decomposition, embedded software analysis, and non-volatile memory data extraction.
Protocol fuzzing
Systematic testing of the communication protocol stack to identify bugs - including the DLMS/COSEM protocol of smart meters.
Reporting and CVE
Vulnerability documentation with CVSS scoring, reports to manufacturers, and official CVE registration.
Results
We reported more than 50 vulnerabilities to vendors, including one that freezes a meter with a single 22-byte frame.
We reported more than 50 vulnerabilities to device vendors.
We found 5 flaws in the DLMS/COSEM protocol stack of smart meters.
One vulnerability allowed freezing a meter with a single 22-byte data frame.
The critical flaws included remote code execution, memory leaks and command injection with root privileges.
Planning a similar project?
30 minutes with a consultant who runs projects like yours. We agree the scope and tell you what the price depends on.
Related case studies
CS.104
Advanced Red Team Testing in the Energy Sector
The attack simulation exposed critical IT and OT vulnerabilities, which the company removed, as retests confirmed.
CS.105
Identity and Access Management System Testing
Tests of AD, ADFS and PKI found configuration gaps an attacker could exploit and produced a prioritised remediation plan.
CS.107
AMI system security for a distribution system operator
Reverse engineering found critical vulnerabilities in AMI devices, and the operator has security procedures for the system.
We'll discuss scope, methodology, and timeline.