Try to stop access immediately, preserve the message and establish what the attachment contained. Use your mail administrator to revoke a shared link or recall the message where possible, then ask the unintended recipient to stop using or forwarding it and to confirm deletion. A recall notification is not proof that every copy has disappeared.
Give one incident owner responsibility for the timeline, containment and reporting assessment. Do not wait for a complete forensic answer before deciding whether a current reporting duty applies. Equally, do not tell every customer that their information was stolen when you have only established one mistaken email.
What can we do to contain the email?
Check whether the email carried a file or a link. A controlled link may allow access to be disabled centrally. An attached workbook can remain available after its sender deletes the original message. Ask the administrator whether the recipient opened or downloaded it, whether forwarding occurred and what the available logs can actually show.
Contact the unintended recipient through a verified channel. Identify the mistaken message without sending the spreadsheet again. Request deletion from inbox, downloads and any onward copies, and ask whether it was accessed or shared. Keep their reply. A cooperative recipient reduces uncertainty, but their assurance should be recorded as an assurance rather than presented as technical proof of erasure.
Removing an external sharing permission can stop further access. Keep the original message, headers, attachment and access logs in a restricted incident file first. Do not ask staff to wipe the evidence in the name of cleaning up.
Which facts decide how serious this is?
Inspect a protected copy of the actual attachment. Count the affected records and identify their fields. A list of business switchboard numbers is different from a workbook containing personal addresses, account details, passwords or health information. Hidden sheets, comments and older tabs may contain information that was not visible in the first screen.
Record the recipient's relationship to the business, any confidentiality obligation, whether the email was encrypted and who held the password. Determine whether the password was sent in the same thread. Identify the affected customers from the actual workbook version rather than assuming that every person in the current master database was included.
Does the DPDP Act require notification now?
As checked on 17 November 2026, the ordinary DPDP Data Fiduciary obligations, including its core breach duties, are scheduled for 13 May 2027 under the commencement notification. The consent-manager phase in November 2026 does not activate the whole regime. Do not describe the future Board process as the only reporting question or treat the absence of that current duty as permission to ignore the incident.
The IT Act, the 2011 sensitive personal data rules, CERT-In directions, contracts and any sector-specific requirements need a separate review. The current regime does not treat every personal phone number as sensitive personal data, but the workbook may contain categories that are sensitive. Establish the actual contents and the business's role before reaching a conclusion.
When does CERT-In become relevant?
CERT-In's directions of 28 April 2022 apply to specified entities, including bodies corporate, and require reporting specified cyber incidents within six hours of notice. Data breaches and data leaks appear in the reporting material. Assess whether the mistaken transmission falls within the directions and the FAQs on the facts, rather than assuming an email mistake is automatically outside cybersecurity reporting.
Where a report is required, the FAQs allow the initial information available to be submitted and additional information to follow within a reasonable time. The reporting assessment should therefore begin as soon as the mistake is discovered. Keep the discovery time, advice obtained, report and acknowledgement. A customer's contractual notification clock may run separately.
| Record | What it establishes |
|---|---|
| Original sent email and headers | The destination, dispatch time and attachment version. |
| Mail and link-access logs | The access events the system actually recorded. |
| Recipient's written response | What the recipient says was opened, shared or deleted. |
| CERT-In assessment and customer contract | Separate reporting triggers and notification decisions. |
What should we tell affected customers?
Work out which notifications are legally or contractually required and whether a protective warning is needed because of the actual risk. A useful communication says what information was involved, when the mistake happened, what has been contained, what remains uncertain and what the customer can do. It should not expose other customers' details.
Avoid asking people to change unrelated passwords merely to make the company look responsive. If credentials were included, a targeted reset and monitoring may be appropriate. If the file contained invoice and contact information, a warning about impersonation or changed-payment instructions may be more relevant. Have one verified contact channel for questions.
How do we close the incident properly?
Write a closure note only after the known actions are complete. Record the cause, affected data, containment, reporting decisions and residual uncertainty. Correct the process that allowed the export or address error. Depending on the facts, that may mean external-recipient warnings, restricted exports, a second check for bulk attachments or access-controlled sharing.
The practical judgment is to distinguish evidence of containment from hope. A deleted sent email, a successful recall request and a recipient's assurance are three different records. Each belongs in the file with its actual limits.
Train the team using a synthetic example rather than the leaked workbook. Review whether unnecessary columns can be removed from ordinary working exports. The business compliance guide explains the wider duties and commencement stages. The personal-data answer addresses the customer's side. If the incident leads to impersonation or fraud, use the separate cyber-crime response as well.