When most people think about cyber security, they probably conjure up thoughts of someone locked away in a dark room, wearing the same grey hoodie for months. Staring at a screen for days at a time looking for just the right network packet to tell them where and how to attack. But that's not always how hacking is done.
For automation networks or IT computer networks, a few essential cables and adapters should be in your kit.
That way you've got them handy, whether you're troubleshooting network problems or just keeping your equipment and line up and running.
Note that the information below applies not only to PCs, PACs, and PLCs, but to pretty much any industry-standard compliant network device.
There are a ton of great network analysis tools out there today that you can pay huge sums of money for. But a go-to industry standard, and my tool of choice for everyday network troubleshooting, is a free piece of software called Wireshark.
In a recent developer survey conducted by the Eclipse IoT Working Group, IEEE IoT, and Agile IoT, 40.8% of respondents indicated the Internet of Things (IoT) solutions they were either currently building or planning to build were IoT platforms or IoT middleware.
Almost every large IT or OT company today has some form of IoT platform or middleware, with the current number of self-described IoT platforms exceeding 150.
Ethernet networks have taken over as the prominent bus architecture for industrial automation networks. And for good reason.
Ethernet simplifies and homogenizes connectivity between industrial devices. We don’t have to worry about male or female DB9 and DB25 serial connectors, no concern for DTE or DCE devices, and forget about straight-through vs. null-modem cables. In general, the world is a much happier place.
However, even with the added simplicity Ethernet offers, troubleshooting Ethernet networks can be a bit more involved than serial networks.
Let’s assume you’re trying to establish communication with an industrial Ethernet device that for whatever reason has dropped off the network. Here are a few tips I always use when starting to troubleshoot an industrial Ethernet network.
Attention industrial engineers: If you're not thinking about how secure that new wiz-bang-flashy PLC or PAC is before you purchase it, you're setting yourself up for a world of pain down the road.
Industrial control systems are used across a wide range of industries, from manufacturing and fabrication, to electricity generation and transmission, to oil refining and water treatment—all industries where a network security compromise could mean huge losses of capital for the business.
Recently we’re seeing many of these traditionally proprietary control systems—distributed control systems, PLCs, and SCADA applications—adding new, more open technologies like Ethernet and TCP/IP. And with organizations' increasing interest in the business advantages of obtaining system data, industrial control systems are now being connected to information technology (IT) networks.
If you're looking to connect real-world signals and industrial "things" to Information Technology (IT) systems, cloud software, and mobile devices, you already know Opto 22 products will serve you well.
And It’s Going to Happen Again.
Last week the Internet experienced the largest cyber attack in history. Many popular websites went offline for the better part of a day as three waves of cyber attacks hit the DNS infrastructure company DynDNS.
But how could an attack on a single infrastructure company wreak such havoc across the entire Internet?
In my last blog post I talked about the TCP/IP model and why you should care about it. In a phrase: the Internet of Things (IoT).
With all the recent attention around the IoT, the Industrial Internet of Things (IIoT), and Industry 4.0, I’m sure you’re starting to realize that networking, Internet communication, and network security are going to be important in your job as an automation professional.
When you're troubleshooting a network communications problem, it's often best to start from the bottom and work up.
Opto 22 engineer Matt Newton shows you how in his recent blog post about the TCP/IP Model: Troubleshooting the Link Layer.