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?"
"Amagasaki, Japan 26 April 2005 A seven-car train with 580 passengers derailed and slammed into an apartment building of nine floors. 73 people were killed and nearly 450 injured"
Trains, in my buildings?
It's more likely than you think.
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...
...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.