Map the systems that keep trading moving
Identify the software, cloud services, email, payment systems and data that operations depend on. Consider what would happen if a critical system became unavailable.
Test the basics before an incident
Backups, access controls, patching, multi-factor authentication and response responsibilities can affect both resilience and the information relevant to an underwriting discussion.
Understand the first hours after an event
A practical incident plan should identify who escalates, who preserves evidence, which specialists may be needed and how communications are managed. Specific notification duties depend on the policy and event.
A sensible next step
If you are reviewing a quote or existing cover, prepare the schedule and questions for an authorised adviser. Do not submit sensitive information through this first-contact website form.
Request an insurance review