1 posted on
09/05/2003 9:01:34 PM PDT by
Hal1950
To: Hal1950
To: Hal1950
When the box goes unpatched for six months, the IT shop needs a collective b****-slap.
5 posted on
09/05/2003 9:16:54 PM PDT by
Poohbah
(Crush your enemies, see them driven before you, and hear the lamentations of their women.)
To: Hal1950
The NRC also said that plant IT staff were not aware that there was a vulnerability in SQL Server, or that there was an exploit on the loose, despite the fact that Microsoft and the CERT Coordination Center had issued advisories on both. If my IT staff said that to me, they'd be out of jobs. SQL Slammer was a nearly 100% preventable attack through Microsoft alone. 100% preventable if you had the proper software in place as a safeguard. Being vulnerable to SQL Slammer was almost inexcuseable as admins had over 6 months to patch. MS Blaster was a different story due to the exploit being released only 4 weeks after the vulnerability was released.
6 posted on
09/05/2003 9:17:49 PM PDT by
xrp
To: Hal1950
8 posted on
09/05/2003 9:19:13 PM PDT by
sigSEGV
To: Hal1950
Why nuclear power plant controls are connected to any network escapes me. The only thing I saw in the article was for corporate bureaucracy. The actual controls don't need to be connected. The plant should be a stand alone system. Another (network) system could be put in place to display/transmit information.
11 posted on
09/05/2003 10:15:40 PM PDT by
ampat
To: belmont_mark
PING!
13 posted on
09/05/2003 11:35:09 PM PDT by
Orion78
(I WILL NEVER FORGET!!! FREE IRAN!!! BUSH 2004!!!)
To: joanie-f; snopercod
Bump.
To: Hal1950
A firewall is NOT good enough. I am on my third computer because the other ones crashed due to infectious intrusions. Nuclear power plant computer systems should be totally isolated from ANY outside interference.
16 posted on
09/06/2003 6:46:33 AM PDT by
DianaN
(Eternal Freedom)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson