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.

2.3.2 The Creation <strong>of</strong> FIRST<br />

In August 1989 an invitational workshop was organized by <strong>the</strong> CERT/CC to discuss not only<br />

what was learned during <strong>the</strong> first year <strong>of</strong> operation but also what <strong>the</strong> next steps were in coordinating<br />

relationships between <strong>the</strong> teams. 14 This became <strong>the</strong> first event drawing practitioners<br />

from <strong>the</strong> field and <strong>the</strong> start <strong>of</strong> <strong>the</strong> annual conferences that are now organized by <strong>the</strong> Forum <strong>of</strong><br />

<strong>Incident</strong> <strong>Response</strong> and <strong>Security</strong> <strong>Teams</strong>. 15<br />

In October 1989 ano<strong>the</strong>r worm attacked <strong>the</strong> Internet, which now consisted <strong>of</strong> approximately<br />

170,000 hosts. This worm, called WANK, exploited vulnerabilities in systems connected to<br />

<strong>the</strong> Digital Equipment Corporation’s proprietary network, DECNET. Three teams coordinated<br />

<strong>the</strong>ir activities to provide <strong>the</strong> response to this worm: <strong>the</strong> Department <strong>of</strong> Energy’s <strong>Computer</strong><br />

<strong>Incident</strong> Advisory Capability (CIAC), <strong>the</strong> NASA Space Physics Analysis Network, and<br />

<strong>the</strong> CERT/CC. Various warnings were released from both CIAC and CERT/CC that were<br />

helpful to <strong>the</strong> Internet community, even though many administrators did not heed <strong>the</strong> warnings<br />

and were infected by a variant <strong>of</strong> <strong>the</strong> WANK worm called OILZ released two weeks<br />

later.<br />

After this example <strong>of</strong> successful collaboration between teams, more discussions ensued on<br />

how to set up a response team network. During a 1990 workshop by NIST and CERT/CC, a<br />

panel session presented and discussed <strong>the</strong> ideas for such a network. The session, titled “Developing<br />

<strong>the</strong> <strong>Response</strong> Team Network,” included <strong>the</strong> following presentations:<br />

• Dennis D. Steinauer (NIST, USA), “The <strong>Response</strong> Center Network : Developing It and<br />

Making It Work”<br />

• Richard D. Pethia (CERT/CC, USA), “Developing <strong>the</strong> <strong>Response</strong> Team Network”<br />

• Ronald H. Hysert (Canadian System <strong>Security</strong> Centre), “Developing <strong>the</strong> <strong>Computer</strong> <strong>Security</strong><br />

<strong>Incident</strong> <strong>Response</strong> Network: A Canadian Perspective”<br />

• Christopher C. Harvey (SPAN, France), “The Development <strong>of</strong> <strong>Response</strong> <strong>Teams</strong> in<br />

Europe”<br />

From <strong>the</strong>se and o<strong>the</strong>r discussions, goals for future collaboration were established. These<br />

goals were to share information among CSIRTs and, if needed, to aid one ano<strong>the</strong>r during incidents<br />

and network-wide attacks. The CSIRT community is still pursuing <strong>the</strong>se goals today.<br />

<strong>Teams</strong> working in various collaborations are looking for <strong>the</strong> most effective way to establish a<br />

coordination network.<br />

14<br />

15<br />

<br />

Today FIRST conferences are international forums for CSIRTs and security teams involved in<br />

incident handling. To read more about <strong>the</strong>m see .<br />

20 CMU/SEI-2003-TR-001

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

Saved successfully!

Ooh no, something went wrong!