01
Scoping conversation
A call or a visit to name the applications, the processes they can touch, and whether we may perform supervised write tests.
Kuala Lumpur · IoT control applications
Sit with the command until it reaches the machine.
Data Endpoint Grid audits the software that can start, stop, or set a process — mobile HMIs, brokers, edge rule engines, and the cloud functions that grew write paths after go-live.
Primary work
Command-path audit
Most sites ask us here first. We take the application operators actually touch and trace every start, stop, setpoint, override, and remote reset until it lands on a pump, valve, drive, or damper.
You get a command inventory, a privilege matrix, and a remediation order that can be scheduled into a shutdown — not a generic control-system pamphlet.
Also booked
Related reviews
These sit beside the command-path work when the application is wider than a single write topic.
- Embedded control software review Read the firmware and on-device application that sits between the network and the I/O.
- Operator interface assessment Examine the HMI, tablet, and browser apps that people actually press during a shift.
- Privilege and identity mapping Name every account that can change a process, including vendors and forgotten service users.
- Telemetry integrity review Test whether the values the control app acts on still match what the sensors produced.
- Change-control and rollback audit Inspect how control-app versions, rules, and device images are approved, shipped, and undone.
From sites we have sat with
What operations said afterwards
They followed a “monitoring” app until it started a pump we thought was local-only. The report was specific enough for our integrator to fix in one shutdown.
Hafiz Rahman, Facilities lead, cold-store operator, Port Klang
We expected a generic security checklist. We got a tag-by-tag walk of the CIP loop and a privilege matrix our night shift could actually use.
S. Venkatesh, Engineering manager, food processing, Shah Alam
The closed session with operations and IT stopped an argument we had been having for a year: the cloud functions were writes, not dashboards.
Lina Chew, IT operations, warehouse automation, Selangor
How an engagement runs
Five steps, then a written pack
The sequence is the same whether we are in a cold store in Port Klang or reading a gateway image in Segambut. Details live on the methodology page.
02
Evidence intake
Network sketch, role lists, broker or API notes, and a named operations contact. We will work from a whiteboard photo if that is what exists.
03
Path walk
On site or on a staged system, we follow commands, identities, and a sample of tags until they meet the field device or the software loop.
04
Closed findings session
Operations and IT hear the same record. We separate what can wait for a planned window from what should be constrained before the next vendor login.
05
Written pack
Command inventory, privilege matrix, evidence notes, and a remediation order. No dashboard login is required to read it.