Escalation
Routing an incident to higher tiers or authority as it grows.
What it is
Escalation is the process of moving an incident to more senior responders, specialized teams, or decision-makers when its severity, scope, or complexity exceeds the current handler's level. It defines who gets pulled in and when.
Why it matters
Clear escalation paths ensure that serious incidents reach the right expertise and authority quickly. Without them, a major breach can languish in a frontline queue or stall for lack of a decision.
In practice
A tier-one analyst escalating to the incident response team the moment triage confirms domain-wide compromise.
What to look for
- Clear criteria for when an alert becomes an incident.
- Named people for each tier with backup contacts.
- Escalations that stall waiting on approvals.
Common mistake
Escalating too late to look careful. Early escalation is cheaper than late containment.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Collection Plan
Build a host collection command list, ordered by volatility.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
Read next
- Triage: Quickly assessing alerts to decide what's real and what's urgent.
- Incident Severity: A classification of an incident's seriousness that drives response.
- Incident Commander: The single person who directs and owns an incident response.