Do you need help & advice with Business Continuity or Cybersecurity?
When a cyber incident hits, every second counts. Confusion can cost your business dearly, leading to extended downtime and reputational damage. Dave from GoodChoice IT shared some really important points about what businesses need to think about before disaster strikes. It’s not about if it will happen, but when, and being ready makes a huge difference.
Key Takeaways
- Test your recovery: Can you actually get your data back?
- Identify key people: Know who to call and how to reach them.
- Gather essential contacts: Insurance, PR, and internal communication details.
- Plan your communications: How will you inform staff and customers if email is down?
- Map your network: Understand your systems and their order of importance for restoration.
Before Disaster Strikes: Essential Questions to Ask
It sounds simple, but have you actually tested your backup and recovery process? Can you really restore your data when you need it most? This is a big one. Beyond just having a plan, you need to know it works.
Then there’s the people side of things. Who are the key individuals you need to contact immediately? Do you have their mobile numbers? Are they reachable on platforms like WhatsApp if regular communication channels are down? Knowing this upfront saves precious time.
Insurance, PR, and Communication Plans
What are your insurance details? Who do you need to ring first? Having this information readily available is vital. It’s not just about fixing the technical issue, but also about managing the fallout. What’s your plan for public relations? What message will you put out to customers or the public if they ring up asking what’s happening? Who is in charge of sending out these messages?
Having these details planned out, even briefly, can really help things move along much faster when you’re under pressure. It stops that panicked, "what do we do now?" feeling.
Understanding Your Network and Restoration Order
Things like network diagram maps are surprisingly helpful. Knowing your IP addresses, network ranges, and which servers do what is important. More importantly, in what order do you want to restore them? Some systems are more critical than others, and getting them back online first can minimise disruption.
Consider how long it might take to download data. Where has it been corrupted from? What might data loss actually look like? How will you explain this to your team? And critically, how are you going to communicate with your team if they can’t access email or your usual virtual team platforms? This is especially relevant for hybrid or remote working setups. All of this needs to be thought about beforehand.
