escalation policy
A written rule for who is told about a problem, in what order and how quickly, when the person first responsible cannot or does not act.
In more detail
Escalation hands a problem to someone with more authority or more expertise. Writing the policy before an incident means nobody negotiates it under pressure: it lists who is paged, in order, and how long each person has to acknowledge before the next one is called. In risk management, an indicator turning red or a risk moving outside tolerance is escalated to the risk owner or risk committee.
Examples
chain = ["primary on-call", "incident commander", "CISO"]
escalate_after_min = 5red is what triggers escalation to the risk ownerRelated terms
- functional escalation — Passing an incident to people with more specialised skill, such as a database expert or an outside forensics firm.
- hierarchical escalation — Passing an incident up the management chain to someone with the authority to make bigger decisions.
- paging — Sending an urgent alert to the phone of the person on call so they respond to a problem right away.
- incident severity — A rating of how bad an incident or case is, such as P1 for the most serious, which sets how fast it must be handled.
Taught in
- Risk Assessment: Qualitative vs Quantitative — Cybersecurity Fundamentals, GRC & Cryptography
- Security Frameworks: NIST CSF 2.0, ISO 27001 & CIS — Cybersecurity Fundamentals, GRC & Cryptography
- Incident Roles, Escalation & Crisis Comm — Cybersecurity Fundamentals, GRC & Cryptography