02.07.2014 Views

State of the Practice of Computer Security Incident Response Teams ...

State of the Practice of Computer Security Incident Response Teams ...

State of the Practice of Computer Security Incident Response Teams ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

priority), yellow (cautionary alert, has potential to escalate), green (everything normal). 104<br />

These alert banners would be strategically located in <strong>the</strong> CSIRT <strong>of</strong>fices as visual reminders <strong>of</strong><br />

current activity levels. The yellow alert was also used to let part-time members <strong>of</strong> <strong>the</strong> CSIRT<br />

know that <strong>the</strong>y may get called in if <strong>the</strong> priority went higher.<br />

Because <strong>the</strong>re are not consistent severity scales across CSIRTs, one <strong>of</strong> <strong>the</strong> more unfortunate<br />

problems that can occur is that scales can be contradictory. In some cases <strong>the</strong> priority scales<br />

used have just <strong>the</strong> exact opposite level <strong>of</strong> severity compared to some <strong>of</strong> <strong>the</strong> o<strong>the</strong>rs. While a<br />

selected priority setting works very well within an organizational constituency, it could lead<br />

to confusion in those cases where incidents affect multiple sites beyond a single constituency<br />

base. If a clear understanding <strong>of</strong> <strong>the</strong> relative priorities or criticality is not understood by all,<br />

<strong>the</strong> response actions taken may seriously (and detrimentally) affect <strong>the</strong> ultimate resolution <strong>of</strong><br />

<strong>the</strong> activity.<br />

In looking at <strong>the</strong> lifetime <strong>of</strong> an incident, it must be recognized that <strong>the</strong> priority <strong>of</strong> <strong>the</strong> incident<br />

may change as new information comes to light. The priority <strong>of</strong> a specific type <strong>of</strong> incident<br />

might also change over time as changes in mission and services occur.<br />

3.7.7 <strong>Incident</strong> <strong>Response</strong> Processes<br />

CSIRT response strategies vary as much as CSIRTs <strong>the</strong>mselves do. The response that a<br />

CSIRT provides is based on its mission, services, and service levels. <strong>Response</strong> options can<br />

include<br />

• providing guidance and solutions via phone or email<br />

• going to <strong>the</strong> site or affected machine and helping repair and recover <strong>the</strong> systems<br />

• analysis <strong>of</strong> logs, files, or o<strong>the</strong>r artifacts<br />

• assistance in legal investigations and prosecution<br />

• capturing and documenting evidence from affected computers<br />

• development and dissemination <strong>of</strong> patches, fixes, workarounds, advisories, alerts, or<br />

technical documentation<br />

• notification to sites involved in <strong>the</strong> activity (both victim and source sites)<br />

• none (forward to o<strong>the</strong>rs to handle)<br />

Once an incident report has been received and reviewed, <strong>the</strong> response provided will depend<br />

on <strong>the</strong> CSIRT’s mission, purpose, expertise, and policies and procedures. For example, a state<br />

law enforcement CSIRT’s mission may be to pursue legal investigations; when <strong>the</strong>y receive a<br />

104<br />

CERT CSIRT Development Team personal communication, 2002.<br />

98 CMU/SEI-2003-TR-001

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!