incident commander
The person who coordinates an incident response: assigning roles, making decisions and keeping the response moving, rather than debugging.
In more detail
Separating coordination from investigation keeps the response coherent while specialists work in parallel on focused questions. Handoffs of the role are explicit, so nothing is dropped.
Example
chain = ["primary on-call", "incident commander", "CISO"] # sev1 escalationRelated terms
- technical lead — In incident response, the person who runs the hands-on investigation and containment work with the responders.
- scribe — The incident team member who keeps a timestamped written record of what was seen, decided and done.
- communications lead — The incident role that sends regular updates to stakeholders so the investigators are not interrupted.
- incident response — The organised work of detecting, analysing, containing, removing and recovering from a security incident, then learning from it.
- incident declaration — Formally starting coordinated incident response, including naming an incident commander.
- incident — An unplanned event that degrades or interrupts a service for its users, or harms the security of systems or data.
- scribe — The incident role that records observations, decisions and timestamps as the response happens.
Taught in
- Incident Roles, Escalation & Crisis Comm — Cybersecurity Fundamentals, GRC & Cryptography
- On-Call And Incident Response — DevOps & Site Reliability Engineering
- The Incident Lifecycle — DevOps & Site Reliability Engineering
- On Call And Incident Command — Full-Stack Observability: Metrics, Tracing & Logging