Incident Response

By Michael Desrosiers
m3ip, Inc.
mdesrosiers@m3ipinc.com
http://www.m3ipinc.com

This month's topic is incident response in regards to a security or privacy breach or compromise.

The first thing that an organization needs to understand is exactly what constitutes an incident, what incidents are reportable and what actions you need to take when an incident occurs. The purpose of an incident response plan is to respond, investigate and report any abnormal activities that deviate from approved or expected practices on your organization's information system resources. A solid business plan should include a description of a security violation, a security incident and an example of when a technical vulnerability causes or could cause one or the other.

There are two types of security violations:

Compliance laws and regulations(HIPAA, SOX, GLBA);
Organizational policies and procedures.

Security incidents may reveal the need for increased computer security efforts, possibly including a security training and awareness program. Technical vulnerabilities can be found in hardware, firmware or software and can be caused by design or implementation characteristics or flaws that leave an information system open to potential exploitation and escalation of risk to a business. Should you shut down the systems, alerting the potential hacker or should you try to gain more information about the attacker for prosecution or study? Your decision will depend on what sort of activity has already been discovered and what the likelihood is of loss of life or market edge. Timely reporting is paramount and should be consistent with the incident's severity. Efficient incident handling also will minimize the potential for negative public relations exposure. When an attack is in progress, spontaneous decisions can thwart efforts to determine the source of the incident, collect evidence or prepare for recovering the system and protect system data. Be aware that if you report a potential crime, authorities may seize all of your equipment and remove it from your premises for an unknown amount of time.

Planning & preparation:

• Notification or point of contact in the case of an incident;
• Local managers and personnel;
• Law enforcement and investigative agencies;
• Computer security incidents handling teams;
• Affected and involved sites;
• Internal communications;
• Public relations.

Classification & identification:

Handling the incident;

• Protection of evidence and activity logs;
• Containment;
• Eradication;
• Recovery;
• Follow-up.

Administrative actions:

• Report type, description and impact of the incident;
• Date and time the incident occurred;
• Name and classification of the information system;
• Man-hours involved in recovery and cleanup;

There you have it. The premise behind developing a sound and workable incident response mechanism, is to think it through before it is needed. This is one aspect of information security that cannot be reactive.

To respond to this or previous newsletters or to inquire about an on-site presentation, please feel free to call us at 508-995-4933 or email us at mdesrosiers@m3ipinc.com.

Regards,

Michael Desrosiers
Founder
m3ip, Inc.
We Manage Risk So You Can Manage Business
(O)508-995-4933
(C)774-644-0599
mdesrosiers@m3ipinc.com
http://www.m3ipinc.com

More Articles by Michael Desrosiers

Take Control of Maintaining Your Mac

Take Control of Syncing Data in Leopard

Take Control of Upgrading to Snow Leopard

Macworld Total Snow Leopard Superguide

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.