What changed?
Note when the issue was noticed, the symptoms, and the devices, accounts, or services involved.
Encrypted files. A compromised mailbox. A critical system offline. Let’s discuss the incident, confirm availability, and agree on the next steps.
You do not need a perfect diagnosis. Start with what your team can observe.
Note when the issue was noticed, the symptoms, and the devices, accounts, or services involved.
Identify your internal contact, relevant vendors, and any insurer or incident adviser already engaged.
Explain the business impact and which operations or information need attention first.
The order and scope depend on the incident, the affected systems, and the people already involved.
Understand the symptoms, access, timeline, and immediate business impact.
Coordinate appropriate isolation, access changes, and escalation with the responsible team.
Plan remediation and recovery around available evidence, backups, and operating priorities.
Document findings and the practical controls that need attention afterward.
Explore your cybersecurity position, continuity plan, or the topics worth reviewing with your team.