
If the title and pictures for this blog entry didn't say it loud and clear, than I will say it more plainly. Yes, I am a veteran, and evey once in a while the lingo comes to the surface. Don't mind me! (I linked the pictures to a good millitary non-profit organization that I know too.)
Step 3 in Crisis Management is getting the word out to the techs taking calls and the techs in the field as quickly and effectively as possible. First I would write a brief statement about the problem formatted as follows:
The statement might look like this if virus activity was causing major network issues (see Step 2 for more about that) :![]()
The (_____) virus has caused major network connectivity problems nationwide. / The Security Operations Center is disabling ports that appear to have virus activity. Onsite technicians are being instructed to install the latest security patch before requesting the re-enabling of port security.
An email like this needs to go out to all the technicians, but knowing how most field techs don't sit by their own computers waiting for email, I also find it neccessary to make one more phone call. In the midst of all the incoming calls, I always manage to make some other very critical calls out. One of those calls went to the upper management of all the field technicians. I would make sure that they knew what was going on. They also had a notification chain of their own to follow to get the word out to everyone in their chain of command.





» Storm Worm Virus – Crisis Management Part 2 from HelpDeskNotes
Probably the worst recent virus threat is the Storm Worm Virus. It has grown 10 times larger than any other email attack in the past two years. On average 1 million emails cross the internet in one day, but between... [Read More]
Tracked on: August 15, 2007 10:44 PM | Permalink to Trackback