Service
Telemetry integrity review
Control applications make decisions on numbers. This review asks whether those numbers are still the process, or a cached, scaled, or spoofable substitute.
We pick a small set of control-relevant tags — tank level, motor current, room pressure, conveyor speed — and follow each from the field device through gateways, historians, and the IoT application until a rule, script, or operator sees it.
Along the path we look for unit conversions done twice, default values substituted on timeout, and smoothing that hides a stuck sensor. We check whether an attacker or a faulty integrator can publish a plausible value on the same topic the controller trusts.
Where the application closes a loop in software (PID in the cloud, interlocks in a Node-RED flow, “if temperature then open valve” in a rules engine), we treat that logic as part of the control system, not as IT decoration.
You receive a tag-path dossier for the sampled points, a note on which loops are unsafe to leave in software, and tests the site can repeat after the next integrator visit.