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.

standards for incident handling methodologies or processes that are widely adopted, although<br />

<strong>the</strong>re are many projects currently in progress that are attempting to gain acceptance<br />

and establish some standard mechanisms.<br />

• Because <strong>of</strong> <strong>the</strong> newness <strong>of</strong> this field <strong>the</strong>re is also no consistent structure or set <strong>of</strong> services<br />

for a CSIRT. The nature <strong>of</strong> incident response makes it imperative that a team match <strong>the</strong><br />

goals and objectives <strong>of</strong> its constituency or parent organization. This means <strong>the</strong> services<br />

<strong>of</strong>fered and <strong>the</strong> structure <strong>of</strong> <strong>the</strong> CSIRT must be set up to support those being served. The<br />

majority <strong>of</strong> teams do, however, <strong>of</strong>fer some form <strong>of</strong> incident handling, development <strong>of</strong> security<br />

policies, and development <strong>of</strong> alerts and advisories.<br />

• There is no commonly used taxonomy for incident response and computer security terminology.<br />

This can cause confusion when teams share data that has <strong>the</strong> same classification<br />

name, but which may represent different things.<br />

• Employees who are trained and experienced in incident response techniques and practices<br />

are difficult to find.<br />

• No established education path for CSIRT pr<strong>of</strong>essionals exists as <strong>of</strong> today. Many incident<br />

handling activities have evolved out <strong>of</strong> traditional system, network, and security administration.<br />

Various training courses, as well as mentoring by experienced CSIRT members,<br />

is what is currently available today to help educate incident handling staff. There are also<br />

certification programs, but none has been adopted as a standard.<br />

• There is a lack <strong>of</strong> publicly available sample templates for policies and procedures for use<br />

in <strong>the</strong> day-to-day operations <strong>of</strong> a CSIRT.<br />

• Few tools such as tailored help desks or trouble ticket solutions addressing <strong>the</strong> specific<br />

needs <strong>of</strong> CSIRTs—au<strong>the</strong>nticity and confidentiality, as well as workflows—are readily<br />

available.<br />

It has also been observed that CSIRT best practices do not currently exist in <strong>the</strong> following<br />

areas:<br />

• standards for interfaces—a team’s location within <strong>the</strong> organization, with whom <strong>the</strong>y interact<br />

(internally and externally), what is reported, how that occurs, etc.<br />

• data management—how teams manage, access, archive, and share <strong>the</strong>ir CSIRT data<br />

• pr<strong>of</strong>essional standards—<strong>the</strong> formal or <strong>of</strong>ficial specification for what a CSIRT comprises<br />

and <strong>the</strong> staff who perform <strong>the</strong> work<br />

134 CMU/SEI-2003-TR-001

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

Saved successfully!

Ooh no, something went wrong!