T
Hello,
i have grown increasingly nervous about going with modbus TCP in our control systems. I find it scary that modbus TCP is an open protocol, inviting the world to hack. Right now the PLC and HMI speak to each other using this protocol. traditionally, our company does not protect vital registers from modification. The switch is behind a cabinet that is locked. I am curious what sort of protection can be provided, if any, to prevent intrusion or denial of service attack on the system. I also fear of liability issues involved in this sort of scenario. Do most people monitor UI modifications to system registers via a log? Do BMS systems assume the responsibility to stay away from mapped areas that are not theirs? the volume of data to protect is large and the resources for programming protection is too small to justify a change in the future. I am curious if there are switches that can filter based on mac address to only modify specific modbus TCP registers.
i have grown increasingly nervous about going with modbus TCP in our control systems. I find it scary that modbus TCP is an open protocol, inviting the world to hack. Right now the PLC and HMI speak to each other using this protocol. traditionally, our company does not protect vital registers from modification. The switch is behind a cabinet that is locked. I am curious what sort of protection can be provided, if any, to prevent intrusion or denial of service attack on the system. I also fear of liability issues involved in this sort of scenario. Do most people monitor UI modifications to system registers via a log? Do BMS systems assume the responsibility to stay away from mapped areas that are not theirs? the volume of data to protect is large and the resources for programming protection is too small to justify a change in the future. I am curious if there are switches that can filter based on mac address to only modify specific modbus TCP registers.