HNS MAIN FEED
Sunday, 21:23 EDT
- Scammers using IM to deliver "IQ Test" spam
- Automated vs. manual security
- Facebook boosts security by adding remote logout feature
- Trojan attacks remain widespread
- Spammers attack Apple's Ping social network
- Labor Day phishing warning
- User's opinions on malware infections revealed
- Google Code hosting malware-spreading project
- Fake browser warnings lure victims to rogue AV solution
- Rescue of Chilean miners used as lure by banker Trojan
- Phishing campaign targets McDonald's fans
- Cyber crooks steal nearly $1 million from University of Virginia
Writing an Incident Handling and Recovery Plan
by William Lynch - Senior Consultant for CTG's Information Security Services Practice - Wednesday, 16 March 2005.
Introduction
While many websites and papers discuss incident handling and incident response plans, aside from RFC 2350 very few of these lay out exactly what an actual plan might look like. The following is an outline of a typical generalized incident handling and response plan for a small to mid-sized organization that doesn't have a dedicated incident response staff. Using this outline as a starting point, the reader will need to adapt sections to his or her organization or industry as necessary and flesh out the plan in detail in order to create an adequate customized plan.
Incident Handling and Recovery Plan Outline
1 | 2 | 3 | Next page >>
- Malware detection with Neptune
- Corporate espionage for dummies: HP scanners
- A closer look at GFI Backup 2010 Business Edition
- Network security challenges faced by universities
- Building secure software using fuzzing and static code analysis
