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.

3.5 Staffing<br />

The majority <strong>of</strong> documents we reviewed stress <strong>the</strong> importance <strong>of</strong> identifying staff (or a team)<br />

that is responsible for handling computer security incidents. This staff may be full time and<br />

devoted to incident handling tasks, or it may be ad hoc and pulled toge<strong>the</strong>r only when an incident<br />

occurs.<br />

3.5.1 Staff Size<br />

A question we frequently hear is “How big should my team be?” This is not an easy question<br />

to answer, because it depends on a lot <strong>of</strong> factors. Most people involved in incident handling<br />

agree that one person is not enough, but <strong>the</strong>re is no standard number concerning how many<br />

staff members are needed. This depends on <strong>the</strong> expertise <strong>of</strong> <strong>the</strong> staff, <strong>the</strong> incident workload,<br />

and <strong>the</strong> type <strong>of</strong> services <strong>of</strong>fered. It also depends on what work related to incident handling<br />

and computer security is provided by o<strong>the</strong>r parts <strong>of</strong> <strong>the</strong> parent or host organization.<br />

Depending on <strong>the</strong> level <strong>of</strong> service provided, <strong>the</strong> size <strong>of</strong> <strong>the</strong> team may need to have a minimum<br />

number <strong>of</strong> staff. For example, for a 24x7 service like <strong>the</strong> hotline, you can begin to estimate<br />

how many staff you might need to provide this service. If you have three shifts, you will<br />

need at least four to six people to provide a basic hotline service: three to cover <strong>the</strong> shifts and<br />

a backup for each to cover sick time and vacations. Depending on <strong>the</strong> number <strong>of</strong> calls that<br />

come in, one person for each shift may not be enough. So you may need ano<strong>the</strong>r three staff<br />

members. However, if <strong>the</strong> hotline staff also performs o<strong>the</strong>r tasks, such as technical monitoring,<br />

triage, or incident analysis, <strong>the</strong>n even that number <strong>of</strong> staff may not be enough.<br />

There was one European CSIRT that was staffed with just one person who spent just 20% <strong>of</strong><br />

his time handling incident reports—for a whole country. While by today’s standards this<br />

would seem an unlikely model, at that time this “team <strong>of</strong> one” provided a valuable service to<br />

o<strong>the</strong>r CSIRTs in <strong>the</strong> community by acting as a facilitator to distribute incident reports to <strong>the</strong><br />

appropriate entities.<br />

In looking at <strong>the</strong> data ga<strong>the</strong>red in <strong>the</strong> CSIRT Organizational Survey and through our literature<br />

review, no specific staffing trends or best practice staffing levels were seen. The survey data<br />

showed that<br />

• 31% <strong>of</strong> participating CSIRTs stated that <strong>the</strong>y had 1–5 full-time staff.<br />

• 31% stated that <strong>the</strong>y had 6–10 dedicated full-time CSIRT staff.<br />

• 21% stated that <strong>the</strong>y had over 10 staff.<br />

• Only one stated that <strong>the</strong>y had over 100 staff and that was a combined military team.<br />

• Even some ad hoc and distributed part-time teams stated that <strong>the</strong>y had some staff devoted<br />

to incident handling on a full-time basis.<br />

CMU/SEI-2003-TR-001 71

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

Saved successfully!

Ooh no, something went wrong!