
Knowing which devices exist is only the beginning.
Galvanick Opinion.
October 28th, 2026
On September 30, 2026, the Government Accountability Office (GAO) released Internet of Things: OMB Action Needed to Ensure Agencies Secure Their Networked Devices, which examined how 22 civilian agencies track networked IoT and OT devices in their environments. The Department of Housing and Urban Development (HUD) offered a telling example: its new asset management system identified more than 160 IoT devices its legacy system had never reported. What the agency knew about its environment depended on which tool it used.
Of the 22 civilian agencies reviewed, 15 had established inventories, 11 maintained them, and 10 included all required device information. Only seven met all three OMB requirements, two years after the initial inventory deadline.
Equipment whose compromise can disrupt physical operations are in these inventories. GAO cites attacks reported by CISA in July 2026 where threat actors changed passwords on internet-exposed water-sector devices, including PLCs, locking out operators and forcing manual operations.
GAO recommends updated OMB guidance with clear priorities, timelines, and oversight. That’s needed. But completing an inventory is not the same as being able to defend what it lists.
The Problem Outlasts the Deadline
Operational equipment often outlives the people and systems that track it. Maintenance providers change, records migrate, and experienced staff leave, while the equipment stays in service. Agencies reported similar pressures, citing staff turnover and competing priorities. NASA officials noted it's difficult to distinguish IT from IoT and OT, and they worry that active discovery scans could disrupt sensitive systems.
A static inventory falls behind as soon as devices are added or replaced. Keeping it useful takes an ongoing process that tracks changes in both the equipment and its operational role.
From Records to Context
Discovering a previously unrecorded controller is a starting point. Defenders need to establish its operational role, identify the responsible owner, and examine its communications with other systems. That context helps them assess exposure and distinguish routine activity from changes that warrant investigation.
Those answers usually live in different systems and are owned by different teams. Galvanick pulls that evidence together, pairing asset inventory and communication mapping with behavioral threat detection across endpoint, network, infrastructure, and application data. The Galvanick Platform does this natively and can also ingest data from tools agencies already run, which makes it a central hub for contextual threat detection across the industrial environment.
Beyond the Audit
Completing these inventories is a meaningful step. The next step is to ensure that effort pays off when it matters most. When an unfamiliar connection appears at 2 a.m., an operator needs more than a list of devices. They need to know what that device normally talks to, who last touched it, and whether the activity was expected.
As agencies address GAO’s findings, the inventory should become something security and operations teams use regularly. It should help them identify who is responsible for a device, understand its connections, and investigate unexpected activity. It should remain useful beyond the next reporting deadline.
Request a demo at Galvanick.com