Ask Control Engineering
The Ask Control Engineering blog covers all aspects of automation, including motors, drives, sensors, motion control, machine control and embedded systems. Control Engineering answers questions from readers of Control Engineering's print and online magazines, newsletters and other publications. To comment on any blog posting, click on the post's highlighted question and scroll to the "Post a Comment" box at the bottom. Submit questions as comments to any existing post.
Applying security to PLCs
IT students suggest ways PLCs could be made more secure.
Dear Control Engineering: After watching the video with the DePaul University cyber security students, I was wondering what kind of PLC they used in the class? Is there any more detail on what they found with the security measures?
We normally don’t like to offer advice to would-be hackers, but here is a little more information that did not make it into the video due to the time constraints.
The PLC that the class used was an Allen-Bradley MicroLogix 1100. That particular unit was chosen primarily for its wide deployment, and the fact that it is typical of many of its type. Matt Luallen expects to expand the offering in future sessions, and is already adding a similar unit from Siemens.
A line of questions that ended up on the digital cutting room floor had to do with what the students would suggest to A-B as ways to beef up the security capabilities. Some ideas included:
• Stop using HTTP for the Web GUI, and switch to SSL. They agreed this would be a major step.
• Allow the user to change the administrator name.
• Add requirements for authentication. As it is, one noted that there are big chunks of programming that they can get to without any authentication.
• There’s little protection against sending manipulated data.
Their consensus was that these security features are used in virtually every other field of IT, but not here. Food for thought for the manufacturing community.
Peter Welander, pwelander(at)cfemedia.com