Hackers Manipulated Railway Computers, TSA Memo Says
An anonymous reader sends this excerpt from Nextgov:
"Hackers, possibly from abroad, executed an attack on a Northwest rail company's computers that disrupted railway signals for two days in December, according to a government memo recapping outreach with the transportation sector during the emergency. ... While government and critical industry sectors have made strides in sharing threat intelligence, less attention has been paid to translating those analyses into usable information for the people in the trenches, who are running the subways, highways and other transit systems, some former federal officials say. The recent TSA outreach was unique in that officials told operators how the breach interrupted the railway's normal activities, said Steve Carver, a retired Federal Aviation Administration information security manager, now an aviation industry consultant, who reviewed the memo."
Is a computer that controls anything like this connected to the exterior instead of it's own private network?
Why?!
Hackers have been involved in railroads since the very beginning!
Now they'll have the excuse they need to do to the rails what they've done to the airlines.
"Tell me doctor, with all of your defenses, are there any provisions for an attack by killer bees?"
To me this sounds like some contractor introduced a bug to the system and is attributing the issues it caused to "hackers". If the system is really open to attacks of this nature, then it is fundamentally flawed.
"Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
...when someone might hijack a train and crash it into a skyscraper.
There's no -1 for "I don't get it."
or else the outsourced IT department overseas has senior staff with, ahhh, alternate loyalties... .
if this is supposed to be a new economy, how come they still want my old fashioned money?
I'm sure that it is coincidence that this sort of story gets publicity now. Nothing to do with countering the bad press the TSA has gotten today. And I'm sure there is no way this sort of thing could be prevented in the future without an all-seeing, all-knowing, all-powerful TSA keeping watch on everyone who decides not to stay in one place all the time. Nothing to see here. Move along. Except for you, and you over there. We'll need you to step over here for a moment...
Because private networks with entry points all over town can not be hacked, right.
Did you notice that quite a few of your sentences .
...the well-publicized "attack" on an Illinois water system by Russian Hackers that, unsurprisingly, never actually happened.
Railroad signalling used to be all special purpose hardware. Not any more. Here's the "VitalNetâ Wayside Message Server". Runs Red Hat Linux. Talks "Interoperable Train Control Messaging" protocol.
It gets worse. Here's a General DataComm unit for railroad signal control. "SC-ADT ports configured for Telnet/ SSH sessions, for bypass transport (port forwarding), and to convert async PPP data to IP for transport over a cellular data network. SC-ADT managed via Telnet, SSH, SNMP, FTP, TFTP and HTTP from the Dispatch Facility. "
TFTP? FTP? Telnet? What's wrong with this picture?
There's even a hobbyist program for listening in on signal control traffic, some of which is passed around on unencrypted radio links.
Make the ethernet cables run through an X-Ray machine, or pat down the IP packets. It'll be as efficient as in airports to prevent future breaches.
When I worked on these, we had dedicated links (X25 serial in those days).
There simply is NO EXCUSE for routing stuff like this over the public internet, VPN or not. Even a DDOS on those communications is unacceptable. If the railway techs sent that data across a public network, their employment should immediately be terminated and the railway company liable.
The article tells us that this event happened to a railroad that (1) is in the Northwest, (2) runs scheduled trains during the workweek (Dec 1 was a Thursday) and (3) has frequent enough service that a 15 minute delay would be noticed.
It appears to me that the railroad described is either Washington State's Sounder Train (en.wikipedia.org/wiki/Sounder_commuter_rail) or Oregon's Westside Express Service (WES) (http://en.wikipedia.org/wiki/Westside_Express_Service).
I should start a service selling "industrial control system security retrofits." Between the Internet and the PLC, I'll set up a simple Linux box, with cryptknock and brute-force protection that only allows SSH logins with passphrased keyfiles. Then I'll give the operators a nice script (in .bat form and shellscripts) that puts them to the login prompt in one click and sets up a tunnel between their localhost and the PLC or whatever. Then they connect to the control client to localhost and work as usual. Because the places that do this shit usually have NO IT STAFF, I'll put together a simple interface for managing the keyfiles (some GUI on the box itself would be safest - really stripped down of course, ncurses-based ideally).
For each installation I will charge $3k, maybe with a support option if they want me to manage their keyfiles remotely, very affordable to them but I am actually taxing them out the ass for stupidity >:)
"When information is power, privacy is freedom" - Jah-Wren Ryel