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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Effective teams will have a plan in place for how such coordination and interaction occurs so<br />

that when an event happens, <strong>the</strong> team is positioned to quickly and efficiently orchestrate such<br />

activities. This could include having pre-determined contacts set up (names, phone numbers,<br />

email addresses, encryption keys) and/or tools to support disseminating information (tools to<br />

extract relevant log information, mailing lists and mail merge tools to automate contacting<br />

sites, automated tools to look up contact information from whois servers, etc.). There may be<br />

pre-arranged non-disclosure agreements that are signed between <strong>the</strong> CSIRT and o<strong>the</strong>r external<br />

contacts (for example, trusted experts who might assist in incident or vulnerability analysis).<br />

Identifying <strong>the</strong> appropriate level <strong>of</strong> detail for what data is shared with o<strong>the</strong>rs might be worked<br />

out or negotiated prior to an event, but it has also been <strong>the</strong> case that such arrangements may<br />

need to be made as an incident is unfolding and <strong>the</strong> incident is being analyzed. To <strong>the</strong> extent<br />

that it is possible to determine beforehand who <strong>the</strong> team will share information with, how to<br />

contact <strong>the</strong>m, at what level <strong>of</strong> detail data is provided, and <strong>the</strong> method for dissemination or<br />

access to that data, <strong>the</strong> more <strong>the</strong> CSIRT will be able to undertake such information sharing<br />

efficiently and effectively. Some level <strong>of</strong> trust will also have to be discussed and agreed to.<br />

This will involve what will be done with shared information, how confidential information<br />

will be exchanged, and also with whom this information will be shared.<br />

Van Wyk discusses pulling toge<strong>the</strong>r <strong>the</strong> key players and having a Crisis Action Meeting to<br />

determine appropriate actions for coordination and communication with o<strong>the</strong>rs [van Wyk 01].<br />

Part <strong>of</strong> such activity will determine what needs to be done allowing <strong>the</strong> team to <strong>the</strong>n prioritize<br />

those actions. Schultz also provides suggestions for establishing relationships with external<br />

entities similar to those mentioned above [Schultz 02].<br />

Depending on <strong>the</strong> CSIRT constituency and parent or host organization, who <strong>the</strong> CSIRT shares<br />

information and data with and who a CSIRT coordinates response with can vary. We asked<br />

<strong>the</strong> CSIRTs who participated in <strong>the</strong> survey with whom <strong>the</strong>y coordinated <strong>the</strong>ir response and<br />

with whom <strong>the</strong>y shared data. Their responses are discussed in <strong>the</strong> following two sections.<br />

3.7.14.1 With Whom Does <strong>the</strong> CSIRT Coordinate Activities?<br />

CSIRTs coordinate response activities with internal departments and externally with o<strong>the</strong>r<br />

CSIRTs, law enforcement agencies, and security experts. Of <strong>the</strong> CSIRTs that participated in<br />

<strong>the</strong> survey,<br />

• 66% coordinate <strong>the</strong>ir response activities with <strong>the</strong>ir CIO, IT and telecommunications departments,<br />

or law enforcement<br />

• 58% coordinate with o<strong>the</strong>r CSIRTs<br />

• 41% coordinate with <strong>the</strong>ir legal department<br />

106 CMU/SEI-2003-TR-001

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

Saved successfully!

Ooh no, something went wrong!