Cambridge: 01223 209920        London: 020 3519 0124        Ireland: +353 1697 2287        Sheffield: 0114 349 8054        Suffolk: 0144 059 2163         Email: Lucy@breathetechnology.com
Business Cyber Resilience Guide for UK Teams

Business Cyber Resilience Guide for UK Teams

A finance director cannot wait for a ransomware incident to find out whether payroll can still run. A school business manager cannot accept that teaching stops because a cyber attack has locked staff out of systems. This business cyber resilience guide explains how to keep essential work moving when technology is under pressure – and how to recover without panic, guesswork or unnecessary downtime.

Cyber security aims to prevent an incident. Cyber resilience goes further. It accepts that phishing emails, compromised passwords, supplier failures and technical faults can happen, then plans for how your organisation will continue operating and return to normal safely.

What cyber resilience means in practice

For most organisations, cyber resilience is not a separate product or a once-a-year policy review. It is the combination of sensible protection, clear responsibilities, tested recovery arrangements and responsive people who know what to do when something goes wrong.

A well-protected Microsoft 365 tenant matters, but so does knowing who can make decisions if accounts are compromised. Backups matter, but only if they are isolated from the affected environment and can be restored within the time your organisation can tolerate. Staff awareness matters, but it should support people rather than make them afraid of reporting a mistake.

The right level of resilience depends on your operations. A professional services firm may need rapid access to client records and communications. A school or academy trust may need safeguarding, teaching platforms, MIS data and connectivity available for the start of the school day. A manufacturer may be most concerned about production systems, stock data or site access. The common question is simple: what must continue, what can pause, and for how long?

Start your business cyber resilience guide with priorities

The strongest plans begin with the organisation, not the technology. Identify the services that would cause the greatest operational, financial or safeguarding impact if unavailable. Include the systems behind those services, the information they rely on, the people who operate them and the suppliers involved.

This is often where hidden risks emerge. For example, a cloud application may be available, but staff may be unable to access it if identity services fail. A file backup may exist, but recovering it may take several days because the server, permissions and applications have not been considered together. A mobile phone system may be unaffected, yet nobody has an agreed contact list outside email.

Set realistic recovery targets for each priority service. Recovery time objective defines how quickly a service needs to be restored. Recovery point objective defines how much data you can afford to lose. A finance system might require a short recovery point to avoid rekeying transactions, while an archive may tolerate a longer one. There is a cost to tighter targets, so decisions should reflect actual business risk rather than aiming for perfection everywhere.

Build layers that reduce the chance of disruption

No single security control is enough. Resilient organisations use several layers, so one mistake or technical failure does not become a full operational crisis.

Identity should be high on the list. Multifactor authentication, strong conditional access policies, least-privilege administration and regular checks for unused accounts make it harder for an attacker to turn one stolen password into a wider compromise. For Microsoft 365 environments, this may also include reviewing mailbox forwarding, risky sign-ins, legacy authentication and permissions granted to third-party applications.

Endpoints need management too. Devices should receive security updates, use modern endpoint protection and have clear ownership. Staff working from home, shared devices in schools and personally owned mobiles all introduce different practical considerations. The aim is not to make work difficult; it is to make sure access remains controlled wherever it happens.

Email protection and user education remain essential because phishing is still a common route into an organisation. Training works best when it is regular, relevant and free of blame. Give staff a clear way to report suspicious messages, then make sure reports receive a quick human response. A five-minute check can prevent a much longer outage.

Network security, secure Wi-Fi, segmented systems and suitable filtering also play a part. Segmentation is particularly valuable where a compromise on an office device must not spread to servers, backups, specialist equipment or teaching systems. The exact design will depend on the age of your infrastructure, remote-working needs and budget, but the principle is consistent: limit the blast radius.

Make backups recoverable, not merely present

Many organisations discover too late that a backup dashboard showing green is not proof of recovery. Backups can fail silently, be incomplete, sit on an accessible network share, or restore far more slowly than expected.

Keep more than one copy of important data, with at least one copy protected from routine administrator access or held separately from the main environment. Consider servers, cloud data, configuration, line-of-business applications and critical files. Microsoft 365 has availability built in, but availability is not the same as having a separate, point-in-time recovery option for your organisation’s data.

Recovery testing should be scheduled, documented and meaningful. Test restoring a sample of files, a mailbox and a priority application where possible. Record how long each step takes and what assumptions were wrong. A test that identifies a gap is useful – it gives you the opportunity to fix it before an incident does.

Prepare an incident response that people can use

An incident plan should not be a dense document that only appears during an audit. It needs to be short enough for senior leaders and operational staff to use under pressure, with technical runbooks available for the people carrying out the work.

Set out who leads the response, who contacts your IT provider, who speaks to staff, and who can authorise major decisions such as isolating systems or moving to manual processes. Include contact details that are available if email and shared drives are down. Keep an offline copy or a secure printed version where appropriate.

Your response should cover four practical stages:

  • Contain the issue by isolating affected devices, accounts or connections without destroying useful evidence.
  • Assess the scope, including which services, data, users and suppliers may be affected.
  • Restore services in a controlled order, prioritising safe operation over speed alone.
  • Learn from the event by reviewing what happened, what worked and what needs to change.

Not every alert is a major incident, and not every incident requires a full shutdown. That judgement is where experienced technical support and clear escalation routes matter. A sole IT manager may need immediate Level 3 assistance; a larger internal IT team may need specialist support with Microsoft 365 investigation, recovery or communications planning.

Test people, suppliers and alternatives

A tabletop exercise is one of the most useful resilience activities available. Bring together leaders, IT, finance, operations and relevant site staff. Present a realistic scenario, such as a compromised senior account or an inaccessible file server, then talk through the first few hours. Who notices? Who decides? How do staff communicate? Can customers, parents or suppliers still be served?

These exercises expose operational issues that technical testing alone will miss. Perhaps the emergency contact list is out of date. Perhaps a key supplier has no defined incident route. Perhaps staff can work from a safe alternative location, but no one knows how to access the required system without single sign-on.

Review third parties as part of the process. Ask what data they hold, how quickly they would notify you of an incident and whether your contracts define responsibilities. You cannot transfer all risk to a supplier, but you can avoid being surprised by an avoidable dependency.

Turn resilience into a regular management habit

Cyber resilience weakens when it is treated as a project with an end date. New starters join, devices are replaced, cloud services are added and attackers change their methods. Regular reviews keep your controls and plans aligned with the way your organisation actually works.

A practical rhythm might include monthly checks on security alerts and vulnerabilities, quarterly access reviews and backup restore tests, and an annual incident exercise. Major changes – such as an office move, merger, new school site, system migration or connectivity upgrade – should trigger a focused resilience review as well.

Good reporting gives leaders confidence without burying them in technical detail. Focus on unresolved risks, progress against agreed actions, test outcomes and decisions that need investment. This creates clear accountability for IT managers while helping non-technical leaders make informed choices about cost, disruption and risk.

The goal is not to promise that nothing will ever go wrong. It is to ensure that, when pressure arrives, your people have a tested plan, the right technical support and a clear route back to safe, effective work. That is the kind of peace of mind that lets your organisation focus on the people it serves.


Download the Outsourced IT Support Checklist

Every Manager responsible for IT (Finance, Office Manager, Ops etc), that's not an IT Manager by profession should review their IT Support experience. How do you know if your expectations are realistic, is the team performing, are you at risk and didn't realise? Do you have doubts? Or are they simply great,

This Check Outsourced IT Support Checklist has been created, after performing hundreds of IT Audits over more than 20 years, revealing the most commonly found problems caused by IT Support Providers.

How does yours compare? Download for free today!

(PS. Your details remain confidential and will never be shared with anyone else)