communications lead
The incident role that sends regular updates to stakeholders so the investigators are not interrupted.
In more detail
Separating communication from investigation lets technical responders work undisturbed. Updates go out on a predictable cadence to customers, support and leadership. A good update says what is known, what is unknown and when the next update will come, tailored to the audience while one internal timeline stays the source of truth.
Example
comms = "exec and status page update every 30 min" # sev1 update rhythmRelated terms
- crisis communication — How an organisation informs staff, customers, regulators and the public during a serious incident.
- holding statement — A short, pre-approved message that says an incident is being dealt with before all the facts are known.
- spokesperson — The one person authorised to speak publicly for an organisation during an incident.
- incident commander — The person who coordinates an incident response: assigning roles, making decisions and keeping the response moving, rather than debugging.
- status update — A regular message to users and stakeholders about the state of an incident, what is known and what comes next.
- scribe — The incident role that records observations, decisions and timestamps as the response happens.
- incident — An unplanned event that degrades or interrupts a service for its users, or harms the security of systems or data.
Taught in
- Incident Roles, Escalation & Crisis Comm — Cybersecurity Fundamentals, GRC & Cryptography
- On-Call And Incident Response — DevOps & Site Reliability Engineering
- On Call And Incident Command — Full-Stack Observability: Metrics, Tracing & Logging