4 ms·
Put this crap all on a segregated network. It's how we did it 20 years ago, are people still making the same mistakes? Were firewalls not common even 30 years a
by bluedino 9y ago
Put this crap all on a segregated network. It's how we did it 20 years ago, are people still making the same mistakes? Were firewalls not common even 30 years ago?
- pjc50 9y agoSegregated networks are hard, and usually end up punctured very quickly when someone wants remote access to the segregated system. Or builds a bridge using a system connected to both networks.
- snerbles 9y agoI'm an engineer for an industrial integrator. No matter how often we tell our customers to keep the industrial control networks separated, they'll still find ways to lazily screw their networks up. A couple years ago at a Fortune 100 company, I dealt with a WinCE panel that began randomly spewing millions of broadcast UPnP packets - enough to make Wireshark lag badly. Took us about fifteen minutes to find and unplug the offending item, and the recommended mitigation from Rockwell Automation was to just disable UPnP. No patch was available for a problem that's been known since about 2006 or so, on an HMI product that is still being sold today. Due to some terrible switch configurations on the part of the customer, the traffic made it out to the campus network and DoS'd most of their intranet servers. About 3,000 employees were sent home early for the day because none of them could read their email.
- snowwindwaves 9y agoHow do the computers running the HMIs get security patches then? Only the most critical equipment would have a budget large enough to pay someone to put windows or linux updates on a USB and get all of the computers updated. I don't allow the HMI computers to access the internet, but then they remain unpatched. As an OEM I'm out of the picture once the plant is working.