The Heartbleed Security Bug Breeds Insecurity for Industrial Networks

The Hack's Purpose Was to Replace Hyperlinks, and Direct Users to Other Websites in Europe and Other Locales, But the Results Could Be More Significant

Share Print Related RSS

The Heartbleed security bug is a programming error in an open-source encryption protocol layer of OpenSSL. The gist of the bug is that it allows entry into cached memory that would normally be "malloc’ed" (allocated memory by an application) and protected by that application. So if a hacker can get access to that memory space, which now appears to be unencrypted, then the data that's in that space is easily read.

Believe or not, the Canada Revenue Agency uses this open-source layer to connect to official users, such as accountants, and the general public for e-filing.

I subscribe to an investment service whose site was hacked for reasons unknown. The resulting report from the owner of the site was that the version of WordPress was an older version that had known vulnerabilities, and it hadn't been updated.

By whom? Well, it seems that the creator of the website was using a web-hosting service in California that provided the secure platform and the WordPress application and database as part of its service. So the trust was placed with the service along with the developer.

Misplaced trust can be deadly. The result of the hack was simply to replace hyperlinks and direct users to other websites in Europe and other locales, but the results could have been much more significant.

We do trust in the capabilities of those services that we use—banking, downloads, free apps, etc. Free apps? You have to wonder when a flashlight application for your Blackberry wants to have access to your personal info and turns on your location services. But it is free!

Also Read: Seven Steps to Network Security

The NSA has brought to light the backdoor theory of almost all systems be they hardware or software. We have relied on the powers that be (read IT department) to keep us safe at work. We rely on our ISPs to keep us safe at home. Maybe we should rely on ourselves a bit more to protect ourselves.

The Apple IOS 7 had a bug that sent out unencrypted data over the network. Anyone that does banking with a portable device is nuts. How can you trust that a flashlight application isn’t monitoring and sending info to the mother ship?

You have to wonder when a flashlight application for your Blackberry wants to have access to your personal info and turns on your location services. But it is free!

Trust with verification is needed, which brings me to the removal of support of Windows XP—a new chapter in the life of automation. If we believe in Murphy's Law, things will hit the fan.

I'm guessing here, but the number of SCADA nodes, HMI boxes and programming laptops still running XP must be monstrous. Everyone wants remote access to everything, and if you use XP as an endpoint, there is now a built-in security risk, since no more patches will be forthcoming. The longer you use XP, the more vulnerable you are. It would almost be best to go back to Windows 2000.

It has been estimated that hardware cycles vary from 3 to 6 years. Windows 7 has been with us for five years; XP for 13. Because of the chaos with Vista, not many moved to Windows 7, thus the plethora of computers out there with XP.

The U.S. Navy canceled an order for 1,400 iPads because a portion of the BIOS was written in Russia, by Russians. No disrespect to the Russian programming community meant, but there wasn't any love given to them by the Navy.

Cloud-based technologies are safe and cost-effective we are told. Really? Great idea, but maybe not the best implementation.

While not all issues are security issues, now more than ever we must be vigilant with our industrial systems. Probably even more so in the future. No one knows what the future holds, but one thing is for sure: The evil doers always will be there and they'll be knocking on our door. We must be as informed and knowledgeable as we can. Being our own advocate is paramount.

In God we trust, yes. But in firmware, software and protocols we can't, or at least we shouldn't.

Off-topic final note: ISA's Automation week in North America, which I pronounced dead two years ago, is now officially gone. No longer will the paths of professionals of varying technical disciplines cross in the technical session hall of learning. I'm saddened, but also looking forward to what's next. I just don't know what it looks like yet. Condolences to the ISA and congratulations to the organization for providing so much opportunity for so many over the years. Thank you.  

Share Print Reprints Permissions

What are your comments?

Join the discussion today. Login Here.

Comments

No one has commented on this page yet.

RSS feed for comments on this page | RSS feed for all comments