Start by detecting signals, collecting time-aligned logs and status, then investigating causes. Consider GIIP for operational information and FDE Box for technical support.
| Required task | Importance |
|---|---|
| Detection | 20% |
| Collection | 20% |
| Analysis | 30% |
| Recovery | 20% |
| Prevention | 10% |
Coverage describes functional scope. It is not a success probability or cost-saving rate.
Numerical assessments have not been published for these items. Use the tasks and conditions below to discuss your environment.
Inspect infrastructure status and collected information.
Confirm collector permissions, target environments and collection scope. Actions depend on granted access and the agreed service scope.
Agree on investigation and follow-up technical support.
Agree on goals, access, approval steps and the scope of support before choosing a deployment approach.
Multiply task importance by coverage (full 1, partial 0.5, none 0). For a combination, use the highest level for each task so overlapping work is counted once.
Coverage describes functional scope. It is not a success probability or cost-saving rate.
Change task importance to explore the calculation.
| Required task | Importance | Coverage level |
|---|---|---|
| Detection | Full | |
| Collection | Full | |
| Analysis | Partial | |
| Recovery | Partial | |
| Prevention | Partial |
Overlapping tasks are counted once using the highest coverage level. A numerical result is shown only when all selected items have reviewed assessments.
Your mail app opens with the selected challenge and services. Review before sending.
Discuss this selection ↗