This is where I think Blaster may have been involved. The report gives a specific timeline for the failures. At 14:14 EDT, the "alarm and logging software" at FirstEnergy’s control room failed. This alarm software "provided audible and visual indications when a significant piece of equipment changed from an acceptable to problematic condition." Of course, no one knew that it failed.
Six minutes later, "several" remote control consoles failed. At 14:41, the primary server computer that hosted the alarm function failed. Its functions were passed to a backup computer, which failed at 14:54.
Doesn’t this sound like a computer worm wending its way through FirstEnergy’s operational computers?
According to the report, "…for over an hour no one in FE’s control room grasped that their computer systems were not operating properly, even though FE’s Information Technology support staff knew of the problems and were working to solve them…"
Doesn’t this sound like IT working to clean a worm out of its network?
This massive computer failure was critical to the cascading power failure. The report continues: "Power system operators rely heavily on audible and on-screen alarms, plus alarm logs, to reveal any significant changes in their system’s conditions. After 14:14 EDT on August 14, FE’s operators were working under a significant handicap without these tools. However, they were in further jeopardy because they did not know that they were operating without alarms, so that they did not realize that system conditions were changing."
The Blaster Virus and the August 14th Blackout
In Blaster and the August 14th Blackout, security expert Bruce Schneier makes the case that the Blaster virus played a more significant role in the huge power outage than the official reports are acknowledging.