Every office in the UAE has a fire evacuation plan on the wall. Nobody calls that excessive, and nobody waits for smoke before working out where the exits are. Yet plenty of companies run their entire business on email, cloud systems and shared drives with no agreed answer to a simple question: what do we do if all of this stops at 11pm on a Thursday?
That gap is the plain answer to why incident response is important, and why every business needs an incident response plan. A cyberattack is stressful enough without having to invent your process while it's happening.
Two versions of the same Thursday night
Picture a 150-person trading company in Dubai. At 11:40pm, the IT manager gets an alert that files on the main server are being encrypted.
Without a plan, the IT manager tries the CEO, who is on a flight. Someone suggests shutting everything down. Someone else starts wiping a laptop to be safe, and that laptop happened to hold the evidence. By morning, staff are asking questions on WhatsApp, a client has heard a rumour, and nobody knows whether a regulator must be told. Every decision has become an argument.
With a plan, the IT manager opens a two-page document. It names who is in charge when the CEO can't be reached and says to isolate systems without wiping them. It lists the insurer's hotline and the response team's number, and it says who speaks to staff and clients. The attack is still serious, but people are working through a list and not arguing about what comes next.
That's a scenario. The difference between those two nights is one document and an afternoon of practice.
Why this matters even for a small company

You have far less time than you think
A 29-minute average breakout time means an attacker can move beyond the first compromised machine in less time than most companies take to find the right phone number. The fastest case CrowdStrike recorded took 27 seconds.
Downtime is usually the biggest bill
IBM's 2026 figures for the Middle East put the average breach at USD 8 million, with lost business as the largest single cost, at USD 3.57 million. Your numbers will be smaller, but the pattern holds: every extra day of confusion costs more than the technical clean-up.
Recovery is rarely quick either. In Sophos's 2026 study of 48 UAE organisations hit by ransomware, 48% recovered within a week, down from 63% a year earlier, and 23% took between one and six months.
Regulators and clients will ask what you did
Under the UAE PDPL, controllers are expected to notify the regulator when they become aware of a breach affecting personal data. Sector rules can add tighter clocks, such as VARA's 72 hours for material events. Client contracts often add their own deadlines. If nobody has read these before the incident, you may miss them during it.
Mistakes in the first hour are hard to undo
Wiped machines can't be investigated. A rushed rebuild can bring the attacker's foothold straight back. An unplanned email to clients may say something you later have to retract.
It isn't only about ransomware
Ransomware gets the headlines, but your plan should work for the everyday incidents as well:
A finance mailbox is hijacked and a client receives fake bank details.
A laptop with customer data goes missing.
A departing employee downloads the client list.
A software supplier tells you it has been breached.
Your website goes down during your busiest week.
What a good plan answers
| Question | What to write down |
|---|---|
| Who is in charge? | One named lead and one deputy, with authority to act out of hours |
| Who do we call? | Response team, insurer, legal adviser and key suppliers, with personal phone numbers |
| How do we talk if email is down? | A separate channel, agreed in advance |
| What do we do first? | Isolate, preserve evidence and protect backups. Do not wipe or rebuild yet |
| Who must be told, and how fast? | Regulators, police, clients and insurers, with deadlines |
| What keeps the business running? | Which systems come back first, and how to work manually until then |
| Who speaks for us? | One voice for staff, one for clients and media |
A printed copy matters too. A plan stored only on the encrypted server won't help anyone. If you want a formal structure, NIST SP 800-61r3 is a good reference, but a short plan people actually use beats a long one they don't.
Build it in a week
Day 1: name the people. Choose a lead and a deputy, and collect personal numbers.
Day 2: list your crown jewels. Which systems would stop the business, and in what order do they come back?
Day 3: check your obligations. Note regulators, contracts and insurance conditions.
Day 4: test a backup restore. Find out whether it works, and how long it takes.
Day 5: write two pages, and print them.
The next week: run a tabletop exercise. Sit the team down with a scenario and talk it through. You will find gaps within the first ten minutes.
Repeat the exercise at least once a year, and update the contact list whenever someone leaves. Nothing ages faster than a phone tree.
If an attack is already under way, go straight to our guide on the first 24 hours of a ransomware attack.
Intello helps companies write and rehearse incident response plans, and provides digital forensics and incident response, including in Abu Dhabi and Sharjah.
Comparing providers? See the Top 10 Digital Forensics & Incident Response Companies in the UAE.
Talk to our incident response team or contact us.
Frequently asked questions
Why is incident response important?
Attacks move quickly, and early mistakes are hard to undo. A plan means people know who decides, what to do first and who must be told, which limits downtime, cost and regulatory risk.
What is an incident response plan?
It's a short document that sets out who is in charge during a cyber incident, who to call, what to do first, who must be notified and how the business keeps running.
Does a small UAE business need an incident response plan?
Yes, but it can be short. Two pages covering roles, phone numbers, first steps and notification duties will help far more than having nothing.
How often should an incident response plan be tested?
At least once a year, and after major changes in people, systems or suppliers. A tabletop exercise is a simple way to test it without disrupting the business.
Is an incident response plan required in the UAE?
It depends on your sector and contracts. Regulators and standards such as VARA, ADHICS and ISO 27001 expect incident handling, and the UAE PDPL expects breaches to be reported. Even where it isn't mandatory, it's a sensible precaution.

