The first 72 hours of a breach are decided in advance

Readiness  ·  DataNudge Perspectives

The first 72 hours of a breach are decided in advance

DataNudge Advisory  ·  November 2026  ·  7 min read

When a breach is confirmed, the team has roughly three days to make decisions that took other organizations months to design. The ones that cope are the ones that made those decisions earlier.

Under GDPR, an organization must notify its supervisory authority within 72 hours of becoming aware of a personal data breach, where the breach is likely to put individuals at risk. India’s DPDPA and a range of sector regulators set their own notification duties, and customer contracts often add shorter deadlines of their own. The common thread is that the clock starts when the organization becomes aware, and awareness arrives before the investigation is finished.

That timing shapes everything. The team must decide, with partial facts, whether to notify, whom to tell, and what to say. Organizations that try to make these calls for the first time during a live incident lose hours to questions that have nothing to do with the attack.

Five decisions to settle before an incident

The first is who declares an incident and at what threshold. A named role, with a named deputy, holds the authority to classify an event as a breach and to start the notification clock. Without that role, events sit in a gray zone while people wait for permission.

The second is who can take systems offline. Containment often means switching off something the business depends on. The person with authority to do that must be known in advance, and the criteria for using it should be written down.

The third is who speaks to regulators, customers, and the press. One voice for each audience, with draft templates already approved by legal, prevents contradictory statements that compound reputational damage.

The fourth is which external parties are on retainer. Forensic investigators, outside counsel, and a crisis communications adviser are far easier to engage when the contract already exists. Negotiating terms on day one costs hours the notification clock does not give back.

The fifth is how the team operates if normal channels fail. A breach can take down email and chat. A reachable contact list, an alternate communication channel, and a physical or virtual room where the response team convenes keep the group working when the tools they use every day are unavailable.

Test the decisions with a realistic scenario

A tabletop exercise reveals whether these decisions hold up. Choose a scenario drawn from your own threat profile, such as a ransomware event on a core system or a supplier breach that exposes customer records. Bring in legal, communications, operations, and a senior executive alongside the security team. Inject new information every fifteen minutes and watch where the group hesitates.

The hesitation points are the findings. They typically show up around authority, such as who can approve a shutdown, and around information, such as who has the customer data inventory. Each finding turns into a fix that costs far less than discovering the same gap during a real event.

A simple readiness check for your next leadership meeting

Ask your executive team to write down, separately, who in the organization can declare a breach and who can authorize a shutdown. If the answers differ, or if anyone leaves a line blank, the first 72 hours of your next incident will include a debate that belongs in a planning session.

DataNudge Advisory

DataNudge designs and facilitates tabletop exercises built around your own threat profile, then converts the findings into updated playbooks and decision frameworks. Start a conversation about testing your readiness.

Leave a Reply