SSQ.AISSQ.AI
English
help!

Industrial Control & Hardware Security Validation

Testing control systems, connected devices and their firmware

From settings and configuration down into the firmware of control equipment and connected devices, we find the weaknesses that can really be exploited.

We work in two specialist areas, industrial control security and hardware and firmware security, and also look at where they connect to business networks, apps and the cloud.

Do our control systems and connected devices hold up against attack, down to the equipment and firmware?

From the network boundary and access routes down to the equipment itself: the weaknesses that can really be exploited, and what they would mean for your operations or product.

Expert reviewed

NETWORK Business network Network boundary CONTROL Control network DEVICE Controllers, devices FIRMWARE Firmware, hardware Remote access Flaw in the firmware itself
We follow a route across the network boundary through the control network and the controller down to the firmware itself, and check where the boundary holds.

When it fits

This service is for two kinds of organisation: those that run equipment and those that make connected devices. The first two situations belong to operations, the last two to device makers.

  • Your control network is being connected to other networks

    Remote maintenance, cloud integration or a move to a smart factory is connecting your control network to the outside, so we start by checking that the boundary and access routes are closed as intended.

  • You are bringing in equipment or devices from outside

    Before installing control equipment or connected devices you are buying in, you want to know whether they carry default accounts, management functions nobody needs or known vulnerabilities.

  • You make or launch connected devices

    For a device headed for shops, homes or industrial sites, we check its firmware, hardware interfaces and the communication between device, app and cloud, before or after launch.

  • A customer wants security evidence before delivery

    The customer or partner taking delivery of your devices sets security requirements and asks for a third-party test, so you need the evidence before shipping.

The SAFE SQUARE approach

Firmware, analysed first-hand

We take the firmware of control equipment and connected devices and analyse how it actually behaves.

Live equipment and test rigs, kept apart

Settings and configuration are checked in ways suited to equipment in operation; the equipment and firmware themselves are analysed on spare units or test devices.

For sites that cannot patch straight away

Where equipment cannot be replaced or patched straight away, we also set out what can be done now, such as narrowing the routes in.

What we look at

OT

Industrial control security

The target
Control networks, control equipment such as PLCs (programmable controllers), HMIs (operator screens) and SCADA (supervisory control systems), and where they connect to business networks.
What we can test
  • The boundary and separation between control and business networks
  • Remote access routes
  • HMI, SCADA and engineering workstations
  • Industrial communication protocols
  • Vulnerabilities in PLCs and other control equipment and their firmware (previously unknown ones may also turn up)
  • Equipment management accounts and settings
Where it applies
Factory production lines, plant process control, building automation and facility management
HW·FW

Hardware and firmware security

The target
Connected devices in shops, homes and industrial sites, their firmware, and the apps and cloud that manage them.
What we can test
  • Firmware analysis
  • Hardware interfaces
  • Communication between device, app and cloud
  • Management screens and default accounts
  • Integrity of the update process
  • Vulnerabilities in the device itself
  • The mobile app that manages the device
Where it applies
Shop terminals, smart home devices, and sensors and gateways on industrial sites

The areas are examples.

How it runs

  1. Agree targets and environment

    We agree with you the equipment and devices to test, and where the testing will run.

  2. Map the setup

    We set out with you the network layout and access routes, and the equipment and firmware in place.

  3. Test and validate

    We look from the network boundary down to the equipment and firmware themselves, and confirm whether the weaknesses found can really be exploited.

  4. Explain and re-check

    We explain the findings, real impact, evidence and fixes to the people who run the equipment, look after security or build the product and, if you wish, check the fixes again.

Keeping it safeTests that could affect equipment run only if agreed beforehand, and the equipment and firmware themselves are analysed on spare units or test devices. The principles every engagement follows, safe conduct and stop conditions, facts kept apart from assumptions, and how material is kept and destroyed, are set out under How we work.

What you receive

What was checked, and where

The equipment, devices and firmware versions tested, the environment and conditions, and what is left for next time, stated plainly.

Findings and real impact

Whether each finding can really be exploited and what it would mean for operations, safety or the product.

Reproducible evidence

The conditions and evidence needed to confirm each result again.

What to fix first

What to fix first, with what can be done now set apart from lasting fixes such as patching or replacing equipment.

A sample findingFictional example
Finding 01

The PLC's management function is open from anywhere on the control network with a default account

High
Where it was confirmed
A spare PLC of the same model and firmware version as the production line, on a test control network.
Real impact
Anyone who can reach the control network could change process settings with the default account. We confirmed it on a spare unit; the three production lines with the same setup are affected.
What can be done now
Change the default account's password, allow the PLC's management port to be reached only from the engineering workstation, and raise an alert whenever settings change.
At the next maintenance window
Update the firmware to the manufacturer's latest version, check it on a spare unit first, then roll it out to the production lines and test again under the same conditions.

Functional safety assessments and certification audits follow their own processes; these results can serve as evidence in them.

  1. Tell us what worries you, or what you want checked. A few lines are enough.

  2. We reply with a proposed scope, schedule and cost, and settle them with you.

  3. Once agreed, the work begins. Results and next steps come to you as it runs.