Planning and preparing for the unexpected, especially in response to a security incident, is one of the greatest challenges faced by information technology professionals today. An incident is described as any violation of policy, law, or unacceptable act that involves information assets. Incident Response $($IR$)$ teams should be evaluating themselves on metrics, such as incident detection or dwell time, to determine how quickly they can detect and respond to incidents in the environment. In a recent year, an institute surveyed organizations about internal response capabilities. The frequency distribution that summarizes the average time organizations took to detect incidents is given below.

Click the icon to view the frequency distribution.

a$.$ What percentage of organizations took fewer than $2$ days, on average, to detect incidents?

b$.$ What percentage of organizations took between $2$ and $31$ days, on average, to detect incidents?

c$.$ What percentage of organizations took $31$ or more days, on average, to detect incidents?

d$.$ What conclusions can you reach about average dwell time of incidents?

a$.$ What percentage of organizations took fewer than $2$ days, on average, to detect incidents?

$\%$

$($Round to two decimal places as needed.$)$

b$.$ What percentage of organizations took between $2$ and $31$ days, on average, to detect incidents?

$\%$

$($Round to two decimal places as needed.$)$

What percentage of organizations took $31$ or more days, on average, to detect incidents?

$\%$

$($Round to two decimal places as needed.$)$

d$.$ What conclusions can you reach about average dwell time of incidents? Select all that apply.

A$.$ Most of the incidents are detected after $31$ days.

B$.$ Most of the incidents are detected in less than $31$ days.

C$.$ Less than $25\%$ of the incidents are detected after $31$ days or more.

D$.$ More than $25\%$ of the incidents are detected after $31$ days or more.