By Gregory Hale
Whether it is a high-tech silicon manufacturer or an older forge shop, every security profile is different, however, one thing remains true: Having visibility into the network and the proper policies in place will ensure a more secure process.
However, the answer to what you do with that visibility varies with the individual manufacturer. What you do with that visibility can end up being the battle cry for how secure and how resilient your enterprise can become.
“The place we typically try to have people start is with visibility,” said Wes Sylvester, Vice President, Industry Solutions Group – Growth Marketing Segments & Industries at Cisco. “You can’t secure what you can’t see. This is where we can go out and look and see what all is plugged in to your network – even legacy systems – like PLCs and identify them. I have yet for someone to get a list of things on the network and say, ‘yep, that’s all the things I thought were there.’ What often happens is in a big manufacturing plant, there is a dead corner with a poor signal. So, an engineer plugs in his own WiFi router that he bought at the local electronics store and gets great WiFi access for his team in that corner of the plant. But it is not supposed to be plugged in and no one knows it is there, it doesn’t have any security policies. That is why we always start with visibility so you can figure out what’s out there before you can even figure out what you need to do to secure it.”
Identifying devices is one thing, but the human element also comes into play.
Blame Game
“I think the historical tendency has been to start blaming people,” Sylvester said. “When you think there are 400 devices and there are actually 12,000, you look at who is doing something wrong. I think we are trying to change that mindset a little bit because 99 percent of the people who added those devices were doing so to make their jobs or their company more efficient, or solve a problem. The idea of the IT police coming out and punishing everyone who added devices; we’re trying to make that a thing of the past. So, after you get the inventory, the cool thing about some of these tools is those inventories can identify not only that something is connected, but what it is. Then you start to get a list of what can be protected in what way.”
That is where network identity engines and creating policies can come into play.
“If I have 12,000 devices maybe 8,000 of those devices are iPhones and computers where we can make sure they have all the right patches and updates and upgrades and we can put identity polices on them. 8,000 sounds like a lot to individually put identity policies on, so the neat thing is you can do that en masse so you can make sure iPhones never have access to product networks. As an example you have taken 2,000 to 3,000 devices off the list and gotten them secured. Identifying what is out there helps to know what it does and what access does it have. Manufacturers have lots of production equipment like PLCs and other devices that are legacy that may not be patchable and upgradable and so the best thing that we can do with them is put them in a space where they can do the least harm and give them policies where they can do the least harm.
“A good example of that might be if they have a legacy security camera that needs to stay in position. It needs to be there. Maybe it doesn’t have the latest security features and you can’t necessarily put the right polices on it, but using the network you can say ‘security cameras should never be talking to PLCs.’ If that connection gets compromised for some reason, someone who has access to that connection then tries to send a signal to speed up a motor, the network can identify just by knowing what should or shouldn’t talk to each other. It can then shut that message down and not allow it to pass.
Network Knows
“It is not a matter of either of the devices being smart enough to know what to do, or what not to do, because the motor and PLC that drives the motor just receives a message that says speed up or slow down,” Sylvester said. “The camera doesn’t know any different, but the network can know those two devices are not supposed to talk to each other. You can do all of that with identity services engines, so just policy and identity goes a long way. What is a device? What should it be able to do? Who should it be able to talk to?”
With all the legacy systems and devices out on the plant floor, Sylvester said it remains tenable to create these rules or polices on the network to ensure a system remains secure and running by eliminating unplanned downtime.
“I think it is different to do it this way than a traditional bolt on security approach of just put it behind a firewall,” he said. “The historic mindset might have been if it’s a risk, let’s put it behind a firewall and see if we can keep it from causing too much of a problem. This different approach does it within the network and within the policy. You can do that en masse where you can say these are all iPhones and give them this one policy. You can say the same thing with PLCs and give them all the same policy, or you have 400 security cameras on a 50-acre production facility and give them all the same policy.”
Nissan Case in Point
In most cases the policy resides in the network, so you’re not asking anyone to restart a production system or turn a camera off and restart it and turn it back on. It’s making the policy in the network versus making the devices do something specific and have their own policy, all while the process is engaged.
“With a Nissan plant, they are using identity services engine to make sure the right people have the right access at the right time,” Sylvester said. “We quickly rotate devices and did a lot of the production facilities. If I am an engineer and I have a laptop and lose WiFi, or I just want to look up and engineering drawing, I grab a cable and I try to plug into a switch that is on the product floor the network can say this device shouldn’t be speaking and therefore I’m not going to allow the connection. While the production is happening, that engineer could then call up the network manager and say, ‘I need you to allow me to get access temporarily. They can go in and change that policy real time without changing the production line.”
Security profiles may be different, but having network identity engines and policies for enhanced security all begins with greater visibility.

