Commentary

George Hulme
 

Hacking Nukes

It's rare that I read something in a press release that I agree with, let alone find frightening, but this release from Lumeta scared the heebe geebees out of me.

It's rare that I read something in a press release that I agree with, let alone find frightening, but this release from Lumeta scared the heebe geebees out of me.Security firm Lumeta makes the case that increased connectivity with Supervisory Control and Data Acquisition (SCADA) systems and TCP/IP networks will increase the risk of IT network-style security incidents.

In that, I have no doubt.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Here's the real-life incident the release is based on:

For example, in March, the Hatch Nuclear Power Plant in Georgia went through an emergency shutdown as a result of a software update that was made on the plant's business network. The business network was in two-way communication with the plant's SCADA network and the update synchronized information on both systems. Reset after a reboot, the SCADA safety systems detected a lack of data and signaled that the water level in the cooling systems for the nuclear fuel rods had dropped, which caused an automatic shutdown. Engineers were aware of the two-way communication link, but they did not know that the update would synchronize data between the two networks.

There was no danger to the public, but any time an electric generation plant shuts down, the power company loses millions of dollars in revenue and has to incur the substantial expense of getting the plant back online -- no small task for a nuclear facility. And the Hatch incident was only the latest in a string of accidents and unnecessary shutdowns whose cause was due to some problem on the network. The Browns Ferry nuclear plant in Alabama, for example, shut down in 2006 when a network traffic overload locked up pump controls.

In the case of Hatch Nuclear Power Plant, engineers chose to sever all physical connections between the SCADA and business networks.

If you don't want to take the accounting of the incident from a press release (and who could blame you), read this account "Cyber Incident Blamed for Nuclear Power Plant Shutdown", from The Washington Post.

Lumeta advises facilities to regularly check that their SCADA networks are not connected to their business networks. I agree, and that goes without saying. But when it comes to security, like doing regular backups, many organizations Talk The Talk, but don't Walk the Walk. And all it takes is some nitwit, somewhere, to purposely, or more likely inadvertently, connect SCADA systems to the general LAN and risk to the utility goes up exponentially.

It's only a matter of time before we witness a nasty close call (hopefully that's all it is.)

Have a look at this now famous CNN/DHS video on YouTube:

Makes you wonder when, not if, there's ever going to be an incident.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links