Quick answer
Data breach response is the process of containing a breach, assessing what data was affected and who is at risk, meeting notification obligations and recovering. Decisions made in the first 72 hours shape the legal, financial and reputational outcome.
On this page
The First 72 Hours
- Contain: stop ongoing access without destroying evidence. Reset credentials, isolate affected systems and preserve logs.
- Assess: determine what data was accessed or taken, whose it was and how sensitive it is.
- Notify: work out which regulators, individuals, insurers and partners must be told, and by when.
- Communicate: prepare accurate, consistent messages. Early statements that later prove wrong cause lasting damage.
- Recover and learn: fix the root cause and test that it is fixed.
Why It Matters
Poorly handled breaches cost more than the breach itself: regulatory penalties, legal claims, lost customers and recovery delays. Preparation is the difference.
How to Test Your Readiness
- Run a tabletop exercise of a data breach with executives, legal and communications.
- Check logging is sufficient to tell what an attacker accessed.
- Confirm contacts for your insurer, legal advisers and incident response provider.
- Map where personal and sensitive data lives.
How to Reduce the Risk
Know where sensitive data is, minimise what you keep, encrypt it, log access to it, keep an incident response plan current and rehearse it.
Regulatory and Framework Context
In Australia, the Notifiable Data Breaches scheme under the Privacy Act requires notifying the OAIC and affected individuals of eligible breaches as soon as practicable, with an assessment completed within 30 days of suspecting one. Critical infrastructure and ransomware payment reporting obligations may also apply.
Being exploited now
Threat Radar →The latest related vulnerabilities confirmed as exploited in the wild.
- CVE-2026-59310·3 months ago·Virtualisation RansomwareBroadcom VMware vCenterBroadcom VMware vCenter Path Traversal VulnerabilityEPSS 61.7%
- CVE-2026-63077·4 months ago·Dev tools RansomwareJetBrains TeamCityJetBrains TeamCity Deserialization of Untrusted Data VulnerabilityEPSS 94.9%
- CVE-2026-20316·4 months ago·Edge devices RansomwareCisco Secure Firewall Management Center (FMC)Cisco Secure Firewall Management Center Use of Hard-coded Password VulnerabilityEPSS 35.1%
- CVE-2026-15409·4 months ago·Edge devices RansomwareSonicWall SMA1000 AppliancesSonicWall SMA1000 Appliances Server-Side Request Forgery VulnerabilityEPSS 6.8%
Latest intel on this topic
- Uber says nearly 150,000 impacted by third-party breachThe Record · 18 November 2026
- Hacked! Infoblox discloses third-party data breach, employee data compromisedCyber Daily · 17 November 2026
- Lithuanian customs agency restores services after cyberattack, possible data breachThe Record · 16 November 2026
- Toy Story: LEGO discloses BrickLink data breach as site goes offline for daysCyber Daily · 16 November 2026
- TSMC employee data breach linked to cloud providerBleepingComputer · 15 November 2026
Updated hourly from the daily briefing. More in data breaches in australia: the latest reports.
Common questions
Do we have to notify every breach?
Not every incident is notifiable; it depends on the data involved and the likely harm. Get legal advice quickly, because the clock starts when you become aware.
Should we engage an incident response firm?
For anything beyond a minor incident, yes. Engaging through legal counsel can also help protect privilege over the investigation.
Change log
- 13 November 2026First published.