SCADA

You Were Warned: Cybersecurity Expert Edition — Now with Space Stations

Over the last handful of days breathless reports may have crossed your media streams about Stuxnet infecting the International Space Station.

The reports were conflations or misinterpretations of cybersecurity expert Eugene Kaspersky’s recent comments before the Australian Press Club in Canberra. Here’s an excerpt from his remarks, which you can enjoy in full in the video embedded above:

[26:03] “…[government] departments which are responsible for the national security for national defense, they’re scared to death. They don’t know what to do. They do understand the scenarios. They do understand it is possible to shut down power plants, power grids, space stations. They don’t know what to do. Uh, departments which are responsible for offense, they see it as an opportunity. They don’t understand that in cyberspace, everything you do is [a] boomerang. It will get back to you.

[26:39] Stuxnet, which was, I don’t know, if you believe American media, it was written, it was developed by American and Israel secret services, Stuxnet, against Iran to damage Iranian nuclear program. How many computers, how many enterprises were hit by Stuxnet in the United States, do you know? I don’t know, but many.

Last year for example, Chevron, they agreed that they were badly infected by Stuxnet. A friend of mine, work in Russian nuclear power plant, once during this Stuxnet time, sent a message that their nuclear plant network, which is disconnected from the internet, in Russia there’s all that this [cutting gestures, garbled], so the man sent the message that their internal network is badly infected with Stuxnet.

[27:50] Unfortunately these people who are responsible for offensive technologies, they recognize cyber weapons as an opportunity. And a third category of the politicians of the government, they don’t care. So there are three types of people: scared to death, opportunity, don’t care.”

He didn’t actually say the ISS was infected with Stuxnet; he only suggested it’s possible Stuxnet could infect devices on board. Malware infection has happened before when a Russian astronaut brought an infected device used on WinXP machines with her to the station.

But the Chevron example is accurate, and we’ll have to take the anecdote about a Russian nuclear power plant as fact. We don’t know how many facilities here in the U.S. or abroad have been infected and negatively impacted as only Chevron to date has openly admitted exposure. It’s not a stretch to assume Stuxnet could exist in every manner of facility using SCADA equipment combined with Windows PCs; even the air-gapped Russian nuclear plant, cut off from the internet as Kaspersky indicates, was infected.

The only thing that may have kept Stuxnet from inflicting damage upon infection is the specificity of the encrypted payload contained in the versions released in order to take out Iran’s Natanz nuclear facility. Were the payload(s) injected with modified code to adapt to their host environs, there surely would have been more obvious enterprise disruptions.

In other words, Stuxnet remains a ticking time bomb threatening energy and manufacturing production at a minimum, and other systems like those of the ISS at worst case. Continue reading

Blowback: Stuxnet and the Ongoing Risk to Manufacturing Worldwide

Dear Chevron: Thanks for letting us know you’ve been infected with Stuxnet. It’s difficult to muster sympathy for your management or shareholders, because you were warned.This guy quite clearly warned your industry, as did other firms specializing in technology security.

Every single manufacturer around the world using supervisory control and data acquisition (SCADA) driven equipment in their processes was warned. Businesses at particular risk are those relying on certain ubiquitous applications in a networked environment.

Perhaps you heeded the warning months ago but didn’t disclose widely that your business was working on eliminating the exposures. If your business has been hardening your systems, great. However, the public does have a right to know know if your plant located in their backyard might blow up or release toxic chemicals because your firm was exposed to cyber warfare elements our country sponsored in some fashion.

This goes for any other firms out there that are dealing with the same exposure. Perhaps you believe it’s a business intelligence risk to let your competitors know you’ve got a problem– frankly, we’re way past that. The potential risks to the public outweigh your short-term profitability, and if your plant blows up/dumps chemicals/produces unsafe or faulty products because of Stuxnet, our public problem becomes your public relations/long-term shareholder value problem anyhow.

By the way: perhaps it might be worthwhile to actively recruit American citizens who qualify for security clearance when hiring SCADA application analysts to fix your Stuxnet problems. Why compound your problem for lack of foresight with regard to national security risks? We can see you’re hiring. Ahem. Continue reading

Emptywheel Twitterverse
emptywheel RT @joshgerstein: DC Circuit issues rare mandamus order nixing deposition for Vilsack in Sherrod v. Breitbart lawsuit http://t.co/Pz1RjXFcw6
43sreplyretweetfavorite
emptywheel @attackerman Don't forget surveill everyoneinthewideworldistan. In case they become Whereverthefuckistan.
5mreplyretweetfavorite
emptywheel @onekade A really bad cover? Schindler, is that you?
21mreplyretweetfavorite
emptywheel "Debate abt capital punishment in US has now devolved into debating how many mins of wheezing & coughing = too many," http://t.co/edSoJShmIJ
36mreplyretweetfavorite
emptywheel Greg Miller is better at the tie-less look than Bob Litt. #ImportantNatSecNews
52mreplyretweetfavorite
emptywheel @JulieATate They lost ability to wiretap on parts of AQAP bc of Daily Beast story, then blamed it on Snowden. Maybe that? @KenDilanianAP
53mreplyretweetfavorite
emptywheel Apparently Raj De did not prep by reading @bartongellman's analysis showing that you don't have to be communicating w/target to be collected
55mreplyretweetfavorite
emptywheel John Rizzo says 12333 has been on the books for years. Doesn't say Bush "amended" 12333 in 2001 but did not change text of EO until 2008.
1hreplyretweetfavorite
emptywheel @MiekeEoyang He proposes to start doing that sometime after another 5 years of tenure?
1hreplyretweetfavorite
emptywheel @MiekeEoyang Also, law requires purging info not related to Foreign Intell. Both PCLOB and WaPo analysis agree that almost never happens
1hreplyretweetfavorite
emptywheel RT @SpyTalker: Army intelligence system pulled from key test - U.S. - Stripes http://t.co/ztjcU3esLv
1hreplyretweetfavorite
July 2014
S M T W T F S
« Jun    
 12345
6789101112
13141516171819
20212223242526
2728293031