 |
 |
|
By Mike Theriault on 2010-06-17
Mike Theriault, CEO of B2B Computer Products LLC, offers these tips. The goal is a quick, but considered response. Gather the facts as quickly as you can and act as soon as you have enough information to respond correctly.
Don’t take any action until you can accurately define the problem (not necessarily the cause) and know its scope.
|
|
|
- of
1. Review Compliance DocumentsBe ready to demonstrate compliance to avoid fines and regulatory action.
2. Call Your Incident Response TeamBeyond IT, members may include: attorneys, senior execs, PR, HR, and representatives from each affected business line.
3. Assess the DamageDetermine who and what is or may be affected and the potential effect on your business.
4. Notify StakeholdersConsultants, regulators, and law enforcement should know ASAP; in most states, you have 30 days to disclose to customers.
5. Identify the Cause and Minimize the DamageUnless a breach is actively hurting business, delay fixes until cause and potential impact are understood.
6. Emergency SituationsUnplug susceptible servers and storage systems, disconnect media devices if malicious code is suspected.
7. Document the IncidentRecord everything, from detection through response, to speed rebuilds and aid prosecution of the perps.
|
| FEATURED SPONSORED VIDEOS | |
|
|
|
|
|
|
|
|
Make 8 Popular Performance Tools Work for You
Ten Enemies of Innovation
IT Workers More Confident in Jobs, Economy
The Secret of Apple's Success
Money Woes Take a Toll on Worker Performance
10 Ways to Build Lean, Agile Teams
