Incident Commander
Also called IC.
The single person who directs and owns an incident response.
What it is
The incident commander is the individual designated to lead an incident response, holding decision authority and coordinating the people and tasks involved. The role is about command and communication, not necessarily deep technical work.
Why it matters
A clear incident commander prevents the confusion and stalled decisions that plague leaderless responses. Someone then owns priorities, communication, and the call on actions like containment or shutdown.
In practice
The incident commander deciding to take a business system offline despite the disruption, after weighing it against the breach risk.
What to look for
- One named person making decisions.
- Regular status updates on a set schedule.
- Clear handoff when the commander changes.
Common mistake
Having the commander do hands-on work. Coordinating the response is a full-time job.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Hunt Query Builder
Build a hunting query in KQL, SPL, LogScale or PowerQuery against documented field names, or start from a prebuilt hunt.
- Rule Range
Write a regex, a Sigma rule, a YARA rule and a query pipeline, each graded live against samples, some of which you never see.
Read next
- Escalation: Routing an incident to higher tiers or authority as it grows.
- Playbook: A documented, repeatable procedure for handling a scenario.
- On-Call: A rotation ensuring someone is always available to respond.