When the Lights Go Out: 4 Cyber Security Risks to Watch for During a Major Technology Outage
When a global technology provider suffers a major outage, the immediate headlines focus on the disruption that could be more visible: disrupted transportation, stalled payments, unreachable email, and teams unable to work. Far less attention goes to the second story unfolding quietly… For attackers, a large-scale outage is not just an inconvenience for their targets. It is an opportunity.
Adversaries are quick to exploit moments of collective confusion. Within hours of a significant incident, phishing campaigns appear that impersonate the affected provider, offering “fixes”, “recovery tools” or urgent account verification links. Fraudsters pose as IT support, suppliers or senior executives, knowing that employees are anxious to restore normal service and more likely to bypass the usual checks. Meanwhile, more sophisticated actors look for gaps created by emergency workarounds, disabled safeguards, and stretched security teams who are fighting fires on multiple fronts. The very conditions that make an outage stressful are the ones that make social engineering and opportunistic intrusion more effective.
The challenge is that most organisations plan for outages as an availability problem, not as a security event. Business continuity plans tend to focus on getting systems back online, while the cyber implications are left as an afterthought. Yet the decisions made in the first hours of an incident, from how staff communicate to which controls are relaxed to keep operations moving, can determine whether an organisation emerges with only a temporary disruption or with a far more serious breach. In this article, we explore four things every business should be aware of from a cyber security perspective when a major provider goes down, and what you can do now to be ready before the next one hits.
Don’t assume that people are who they appear to be
Our first point is also the simplest: trust no one you can’t verify. During a major outage, normal channels such as email, Teams and sometimes even phone become unreliable, and attackers know it. Expect a wave of calls, texts and messages from people claiming to be IT support, a supplier, or a colleague who has been locked out. They will sound urgent and plausible, and they will usually have a reason why the usual checks can’t happen. “I’ve lost access to my phone”, “I’m on my personal number because the systems are down” and “I need you to reset this for me now” are all classic pretexts. In a calm moment, most people would spot the warning signs. In the middle of a crisis, when everyone is eager to help and get things moving again, they are far easier to miss.
The rule we should follow is straightforward: don’t engage unless you already have a history with that person. If you don’t recognise the caller or sender, or you can’t confirm they are who they say they are, don’t act on their request, however convincing or pressing it seems. This applies even if the person claims to be one of your own colleagues. A genuine employee who has lost their phone or access still has ways to prove who they are, such as through their manager, a known contact, or a pre-agreed verification process. “I don’t have my phone” is not a reason to skip verification. It is exactly what an attacker would say. You have to know, not assume, that you are dealing with the right person.
This discipline matters across every channel, whether it’s email, Teams or a phone call. Compromised or spoofed accounts, voice cloning and convincing impersonation make it easy for an attacker to appear familiar, so a name on the screen is not proof of identity. Organisations should make sure staff know in advance that it is always acceptable, and indeed expected, to pause, say no, and verify through a separate trusted route before acting. During an outage, a few minutes of healthy suspicion is a small price to pay compared with the cost of handing over credentials, approving a payment or granting access to the wrong person.
Outage Opportunism: Spot it. Stop it. Report it.
Our second point builds on the first: expect scams, and expect a lot of them. Phishing is when criminals use scam emails, text messages or phone calls to trick their victims, often to get them to visit a website that downloads malware or steals bank details and other personal information. A major outage hands them the perfect cover story. Messages offering a “fix”, a “recovery tool” or an urgent account check will arrive in volume, and many will look convincing because they match exactly what people are already worried about. Vigilance is always important. During an outage, it matters more, and it matters now.
The good news is that you don’t have to deal with these threats alone, and reporting them makes a real difference. The UK’s National Cyber Security Centre (NCSC) has the power to investigate and take down scam email addresses and websites, and reporting takes only a minute and costs nothing. Each report reduces the amount of scam communication you receive, makes you a harder target, and protects others from becoming victims.
In practice, organisations should make reporting part of their outage response, not an afterthought. Make sure staff know how to report suspicious emails, text messages, calls, websites and adverts, and that they know what to do if they think they have already clicked or shared information. The NCSC publishes clear guidance on each of these, including how to spot a scam and how to respond if you have been caught out. Encourage people to report first and worry later, and make it clear that nobody will be blamed for raising the alarm. The faster a scam is flagged, the sooner it can be shut down and the fewer colleagues, customers and partners it can reach.
Your suppliers are affected too, so look beyond the headline provider
Our third point is about the ripple effect. When a global technology firm goes down, the organisations that depend on it are not limited to the ones you can see. Your own suppliers, vendors and service partners are very likely built on the same platform, which means an outage you assumed was “someone else’s problem” can reach your business through the back door. Payment processors, HR and payroll platforms, customer support tools, logistics partners and managed service providers may all be degraded, offline or operating in a reduced and less secure state without you being aware of it.
This matters from a security perspective because it widens both your exposure and your blind spots. Don’t just check the status of the affected provider. Check in with the vendors that hold your data, process your transactions or have access to your systems, and find out how they have been impacted and what workarounds they are using. A supplier scrambling to restore service may relax controls, switch to unapproved channels or share data in ways they normally wouldn’t. Attackers also know that suppliers are a useful route in, and will impersonate them with convincing messages about changed bank details, urgent invoices or “temporary” access arrangements.
The practical response is to treat supplier communications with the same caution you apply to everyone else. Confirm any unexpected request, particularly anything involving payments, credentials or access, through a contact you already know and trust. Make sure you have an up-to-date picture of which suppliers depend on the affected provider, ideally before an incident happens, so you know who to call and what to look out for. An outage may begin with one company, but its consequences travel through the whole supply chain, and your security response needs to do the same.
Beware the quick fix: workarounds create risks of their own
Our fourth and final point is about what happens inside your own organisation. When critical services go down, people are resourceful, and that is both a strength and a risk. Teams that can’t access email, collaboration tools or shared files will look for alternatives, whether that means personal email accounts, consumer messaging apps, unapproved file-sharing services or free tools downloaded in a hurry. This is shadow IT, and it thrives in exactly this kind of environment. The intent is almost always good, because people simply want to keep working, but every unsanctioned workaround moves company data outside the controls designed to protect it.
The danger is that these stopgaps rarely get switched off. Data shared through a personal account or an unvetted tool may be unmonitored, unencrypted and impossible to recover or delete once the crisis has passed. Security teams under pressure may also be tempted to disable safeguards, loosen access rules or approve exceptions to get systems moving again. Attackers know this, and some will even offer a convincing “quick fix” of their own, such as a patch, a workaround guide or a replacement tool that is really malware. A workaround that solves today’s problem can quietly become tomorrow’s breach.
The answer is to keep the goal clear: restore services to how they were before, as swiftly and safely as possible, rather than building a new and less secure normal. Agree in advance which alternative channels are approved for use during an outage, and make sure staff know what they are. Where temporary measures are unavoidable, record them, time-limit them and assign someone to review and unwind them once service returns. Encourage people to ask before they improvise. A swift return to normality is the right objective, but it only counts if it is a secure one.