Dragos Buys Phosphorus to Close the xIoT Visibility Gap
The OT security firm absorbs an extended-IoT specialist, promising customers a unified platform that can actually see—and fix—the devices most asset inventories quietly ignore.
Dragos has acquired Phosphorus, a company focused on what the industry calls xIoT: the sprawling, poorly-inventoried middle ground of enterprise IoT, OT, and network-connected devices that aren't quite IT and aren't quite industrial control systems. No purchase price was disclosed.
The pitch is straightforward. Dragos customers will get expanded asset visibility through Phosphorus's device-intelligence engine, with automated remediation workflows baked in rather than bolted on. A unified platform experience is the stated end goal.
Why does this matter? Because the xIoT problem is genuinely nasty. Legacy OT environments are full of IP-connected sensors, building-management gear, medical devices, and network infrastructure that vendors never designed for modern security tooling. Many of these devices run outdated firmware, use default credentials, or speak protocols that standard vulnerability scanners either misread or simply break. Dragos has spent years building passive-detection capability for exactly this environment — Phosphorus brings active device fingerprinting and remediation to the same table.
Automated remediation in OT is a phrase that makes experienced industrial-security people twitch. Sending an unsolicited config change to a programmable logic controller can stop a production line. Phosphorus's approach has generally emphasized safe, credential-management-focused remediation rather than wholesale patching, which is the sensible starting point. Whether Dragos preserves that restraint at scale is worth watching.
The acquisition fits a pattern visible across the security-platform market: point-product specialists getting absorbed by platform vendors who need to fill coverage gaps without building from scratch. Claroty, Nozomi, and others have made similar moves. The differentiation question — why this combination beats a best-of-breed integration — will depend almost entirely on execution.
For now, Dragos says expanded asset visibility comes first, with the remediation workflows and the unified experience following in subsequent releases. Vague timeline, honest sequencing.
