Claroty flags IP flaws in building management systems
What happened
Claroty has published research identifying security weaknesses in the CEA-852 standard, which is used to connect building management systems to IP networks. Its Team82 research group identified vulnerabilities and design weaknesses in LonTalk's IP implementation that create remote attack paths into internet-exposed building management system gateway and server devices. This matters for IT, Telecom & Cyber because contracting activity changes leverage, market appetite, and which clauses buyers can credibly trade with 852 as the clearest commercial anchors; Breach response SLAs is now more valuable
Buyer takeaway
For IT, Telecom & Cyber, this is a staffing-shape signal: remote operating models can shift work offsite and change which suppliers, systems, and service levels matter most
Cost / money
The cost angle is directional, not quantified: moving work offsite can cut travel, rotation, and accommodation exposure, but only if the remote setup stays reliable
Supplier / commercial
Expect scope to move toward software support, communications uptime, cyber obligations, and clearer downtime liability instead of only offshore headcount or hardware supply
Safety / operations
Fewer people offshore can reduce exposure and emergency-response load, but the operating model becomes more dependent on connectivity resilience, remote support readiness, and cyber hygiene
What to watch
Watch bandwidth resilience, latency tolerance, cyber obligations, and who carries downtime cost if the remote link drops
Key facts
- Claroty has published research identifying security weaknesses in the CEA-852 standard, which
- Its Team82 research group identified vulnerabilities and design weaknesses in LonTalk's IP im
- CEA-852 links legacy control networks with IP-based communications in building management and
- As LonTalk shifts from serial connectivity to the IP layer, more of that connectivity is occu
