
A payroll spreadsheet goes to the wrong recipient, a customer database is exposed, or an administrator account is compromised. The business needs technical containment and a legal notification assessment at the same time. Waiting for a final forensic report before identifying the applicable deadlines can leave too little time to act.
Begin with a controlled incident record. Name the person coordinating decisions and involve the relevant IT/security lead, management, legal adviser and data-protection officer if appointed. Use a communication channel that has not itself been compromised.
Capture the facts that determine the response
Record when the incident occurred if known, when it was discovered, when the business became aware of the relevant facts, and what remains uncertain. Preserve these as separate times; the first unusual log entry is not necessarily the moment a manager understood that personal data was affected.
- Which legal entity controls the affected service or records?
- What happened: loss, unauthorised access, disclosure, alteration or loss of availability?
- Which people and data fields may be affected?
- What is confirmed, and what is an estimate pending investigation?
- Who could access the information, and for how long?
- What containment action has been taken, by whom and when?
Keep original logs and relevant files with controlled access. Coordinate password resets, access restrictions and recovery with the technical team so that urgent containment does not unnecessarily erase the evidence needed to explain the incident.
Identify the data-protection regime and your role
A UAE address does not establish one reporting rule for every business. Determine whether the federal personal-data framework, DIFC, ADGM or a sector-specific regime applies to the affected processing. Also determine whether the business is deciding how data is used as a controller or handling it for another organisation as a processor.
| Framework | Question to resolve promptly |
|---|---|
| Federal personal-data law | Check applicability, the controller/processor duties and the current implementing and notification requirements. Do not import another regime’s deadline. |
| DIFC | Use the Commissioner’s Articles 41/42 assessment and reporting guidance. Personal-data and IT/security reports may be separate; any required notice to individuals is also separate. |
| ADGM | For a notifiable breach, official guidance requires controller notification without undue delay and, where feasible, within 72 hours of awareness. |
The ADGM timing is not a universal UAE 72-hour rule. Map customer contracts, processor agreements, insurance terms and sector requirements as well: a contractual notice obligation can require action independently of the regulator assessment.
Assess harm using the actual information exposed
A count of affected records is only one part of the assessment. Consider whether the information includes identity documents, payroll, bank details, medical information, credentials or sensitive correspondence. Identify who received it, whether it was readable, whether access is ongoing, and what practical misuse could follow.
Illustration: an employee emails a payroll file to an unintended external recipient. A deletion confirmation is useful evidence, but the assessment should also consider the fields included, whether the file was opened or forwarded, and whether the confirmation is reliable. Do not equate “recipient asked to delete” with “no breach occurred”.
Document the reasoning for notification or non-notification, the information relied on and the person approving the decision. Revisit it when new facts change the risk. A later discovery of identity documents in an exposed folder may alter an initial assessment based only on contact details.
Prepare accurate notices without waiting for every answer
List the recipients, legal or contractual basis, deadline, owner and status in a notification tracker. For any required initial report, state confirmed facts, identify estimates and explain the investigation or containment steps. Follow the relevant authority’s process for missing information and later updates rather than silently waiting for certainty.
Where individuals need to be told, explain what happened, what information was affected, what the business has done, what practical protective action they should take and how to reach the responsible contact. Avoid unsupported statements that no data was accessed or that there is no risk. Do not include another person’s sensitive information in the notice.
Manage the supplier and recovery work
If a cloud provider or other supplier is involved, request the incident timeline, affected systems, relevant logs, containment measures and outstanding uncertainties. Preserve the agreement and support correspondence. The supplier’s own regulatory report does not automatically complete your business’s separate obligations.
Track restoration, access reviews, corrected permissions and any customer commitments. Keep a decision log rather than relying on scattered messages. Once urgent measures are stable, review the control or contract gap that allowed the incident and assign responsibility for fixing it.
Questions during an incident
There is ransomware but no proof of a download. Is assessment still needed?
Yes. Investigate what happened to access, integrity and availability as well as possible copying. An absence of confirmed download evidence does not complete the personal-data analysis.
Can we use the same notice for the regulator and customers?
Prepare each for its purpose and required content. A regulator needs the report specified by its process; individuals need clear information about their exposure and useful protective steps.
What if the investigation changes the number of people affected?
Preserve the earlier estimate and its basis, record the revised finding and update the relevant recipient through the applicable process. Do not rewrite the historical decision record as if the new facts were known earlier.
Start with a secure incident summary
Read our technology and data-related legal services page and cybercrime evidence guidance. Contact ABC Law Firm with a short incident description and any known deadline; arrange a suitable secure method before sending bulk personal data or technical logs.
