, SecurityFocus 2003-08-19
The Slammer worm penetrated a private computer network at Ohio's Davis-Besse nuclear power plant in January and disabled a safety monitoring system for nearly five hours, despite a belief by plant personnel that the network was protected by a firewall, SecurityFocus has learned.
Expand all |
Post comment
Slammer worm crashed Ohio nuke plant network
2003-08-20
JeiAr (1 replies)
JeiAr (1 replies)
Slammer worm crashed Ohio nuke plant network
2003-08-20
Dmitriy <maniac (at) angrycube (dot) com [email concealed]> (4 replies)
Dmitriy <maniac (at) angrycube (dot) com [email concealed]> (4 replies)
Slammer worm crashed Ohio nuke plant network
2003-08-21
Anonymous (1 replies)
Anonymous (1 replies)
Slammer worm crashed Ohio nuke plant network
2003-08-20
Anonymous (1 replies)
Anonymous (1 replies)
Slammer worm crashed Ohio nuke plant network
2003-08-20
Anonymous (1 replies)
Anonymous (1 replies)
Unbelieveably Irresponsible
2003-08-21
Anonymous (1 replies)
Anonymous (1 replies)
Microsoft Windows in Mission Critical Environments
2003-08-22
Ryan Lambert (8 replies)
Ryan Lambert (8 replies)
Slammer worm crashed Ohio nuke plant network
2007-05-19
mg (at) alienmicro (dot) com [email concealed]
mg (at) alienmicro (dot) com [email concealed]

I work in a large hospital, State run, that has NO knowledgable staff at all running their system. The Dept Head is a political appointee with a degree in STATISTICS. To add insult to injury, he is a MICO manager.
Because he was appointed by a politician, the Hospital Director goes along with him on everything, without question.
When things such as staff needing training in the workings of the network protocols, prior to being given FULL network adminsitrative rights, are pointed out to him, he says that he believes in "sharing the control".
I have worked in several places that have the same attitude, give all of the power and control to the EXECS, whether they know anything about it or not. Then when the crisis hits, they come to me to "get it working ASAP".
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/articles/6767/21785#21785