AI agents investigate every alert, add context, and prepare cases for response, on a full-stack SecOps platform that captures and correlates all your security data.
Cloud-based SIEM platform providing visibility across all your data sources
Every alert investigated, with a verdict and the evidence behind it
Manage your external footprint, publicly available data, and Dark Web leaks
Log management and threat detection across any of your log sources
Get ultimate assurance that your environment is free from threat actors
Fully featured distrubuted NDR for on-premises and public cloud environments
A SecOps platform purpose-built for industrial and OT environments
Integrated endpoint agent providing deep visibility, response and forensics
Deploy honeypots and honeytokens and stay ahead of threat actors
24x7 security operations from our Australian SOC. AI investigates every alert, and experienced analysts validate findings and contain threats around the clock.
24x7 managed detection and response across endpoint, network, cloud, identity, and log sources
AI investigations and 24x7 MDR on the Microsoft Sentinel you already own
Eyes-on-glass SOC and continuous threat hunting
Expert hunters and AI agents find attacker activity your alerts missed
Quickly recover from cyber attacks and breaches
ThreatDefence is the only SecOps as a Service company providing broad coverage across your entire technology stack with evidence-based security.
We provide security teams with full-stack SecOps infrastructure – you get deep visibility from day one, gain control over your security data, and get access to a comprehensive set of ready-to-use tools, detections, workflows, playbooks and scenarios.
24x7 SOC, Continuous Monitoring, Threat Containment and Incident Response
Visibility and actionable insights for all IT assets
Leverage our Cyber Range to train defenders based on real-world scenarios and simulations
OT and industrial cyber security services for critical infrastructure
Monitoring, evidence and a 24×7 SOC in one platform
Compliance monitoring, evidence and board reporting
Privacy Act reform impacts, obligations, and practical security considerations
Monitoring and compliance support for critical infrastructure environments
A practical guide to securing critical infrastructure with continuous monitoring
A practical buyer’s guide for schools evaluating SIEM and SOC services
A practical guide to selecting the right SIEM and SOC service for local government
Articles on security operations, AI and compliance
Events, awards and company news
Read what our customers say about us
Solution briefs and datasheets
How we keep your data secure
Technical support and knowledge base
Guides, case studies, and advisories in one place
How AI agents investigate alerts and run security operations
Free ebook: a practical guide to adopting an AI SOC platform
A practical guide to incident response and digital forensics
Where SOAR playbooks fit and where AI agents take over
Free ebook: modern security operations with Microsoft Sentinel
How the framework is structured and what changes from the Essential Eight
How an attack unfolds stage by stage and how to detect each one
November 16, 2026
November 13, 2026
November 10, 2026
We provide end-to-end SecOps solutions for Managed Security Service Providers (MSSPs), Managed Service Providers (MSPs), and Value-Added Resellers (VARs).
Find out how you can become a ThreatDefence partner.
Protect your entire technology stack and build your SecOps on your own pace
White-labeled AI SOC for every client tenant, co-managed with our SOC team
Launch your SOC business without any upfront investment
Embed security operations, threat intelligence and exposure data in your product
Sovereign SOC for Australian MSPs and MSSPs, with onshore analysts and client data
Set the rules for closing alerts automatically, with evidence checks and review
How MSPs deliver branded security monitoring with a SOC partner
ThreatDefence was an official partner of the Cyber Resilience Summit NSW, 29 October 2026 at Hilton Sydney.
Our team was back at BSides Canberra, and our cyber quiz was a hit again.
Two days in Perth with our partner Ever Nimble, on security operations and cyber resilience.
Sponsors of the AUSCERT Cyber Security Conference on the Gold Coast.
Sponsors of the Gartner Security & Risk Management Summit in March.
Sponsors of the Cyber Security for Critical Assets Summit in Perth, February 2026.
Expert conversations with speakers and attendees at CyberCon Melbourne 2025.
A data breach response plan sets out how an organization will respond when personal or sensitive information is accessed, disclosed, or lost without authorization. It covers containing the breach, assessing the harm, notifying those affected, and preventing a repeat.The hardest part of any breach is deciding whether it must be notified. This guide works through the timeline and the test, then applies them to worked examples.
A data breach occurs when information an organization holds is accessed or disclosed without authorization, or is lost in circumstances where unauthorized access or disclosure is likely. Regulators group the causes into malicious or criminal attack, human error, and system fault, and a plan needs to handle each.
Malicious or criminal attack is the largest category in the Notifiable Data Breaches reports published by the Office of the Australian Information Commissioner. It includes phishing that leads to a compromised mailbox, stolen or guessed credentials, ransomware with data theft, and intrusions through unpatched systems. It also includes theft of paperwork and devices, and deliberate action by an insider.
These breaches are the hardest to assess, because the organization usually does not know at first what the attacker reached.
Human error covers personal information sent to the wrong recipient by email, post, or message, files published or shared with the wrong settings, a reply-all that should have been blind copied, and documents left in a public place. These breaches are frequent, usually small, and often containable if caught quickly.
A system fault is a software bug or misconfiguration that exposes records to the wrong users: a portal that shows one customer another’s details, or a database reachable without a password.
A breach does not need an attacker, so the plan has to be usable by an office manager dealing with a misdirected email as well as by a security team dealing with ransomware. Many breaches also involve email in some way, either as the route in or as the place the data was sitting.
A cyber incident and a data breach are different things that often overlap. An incident response plan deals with the attacker and the systems. A data breach response plan deals with the information and the people it belongs to. The two run side by side.
Containment is the first duty and the one that most affects the outcome. Effective remedial action can change whether a breach is notifiable at all.
Recall it if the mail system allows. Contact the recipient at once, ask them to delete it unopened, and get written confirmation. Note who the recipient is and whether they can be trusted.
Remove the sharing, then check the access log to see who opened it while it was exposed.
Preserve the audit records first, then run the compromised account playbook set out in the incident response playbooks guide.
Confirm from the device management record whether it was encrypted and locked, then run the lost device playbook in the same guide.
Restrict access at once, then copy its access logs before anything else on the system is changed.
Follow the incident response plan. Containment here is a security operation.
Ask the supplier what was affected, what they have done, and for their evidence. Review what data they hold.
In every case, record what was done and when. The record of containment is part of the evidence for the assessment that follows.
Australia’s Notifiable Data Breaches scheme operates under the Privacy Act 1988 and is administered by the Office of the Australian Information Commissioner (OAIC). It sets a sequence that a plan should follow.
The 30 days is an outer limit for the assessment, not a waiting period. An organization that already has enough information to believe a breach is eligible should notify as soon as practicable.
The scheme applies to organizations and agencies covered by the Privacy Act. That generally includes businesses with annual turnover above AUD 3 million, Australian Government agencies, and some smaller businesses such as health service providers.
A data breach is eligible only when each of the following is true.
Serious harm is wider than financial loss. It includes identity theft, physical harm, psychological distress, and damage to reputation.
The assessment of likelihood weighs several factors:
Identity documents, health records, financial details, and credentials carry the greatest risk.
Information that could embarrass, endanger, or discriminate against a person.
Encryption, and whether the key was also exposed.
A criminal group, an unknown party, or a known recipient who can be trusted to delete it.
The scale raises the chance that someone is seriously harmed.
A longer window widens what could have been taken.
Fraud, impersonation, extortion, or targeting of vulnerable people.
Record how each factor was weighed.
A payroll officer emails a spreadsheet of staff salaries and bank details to an external accountant with a similar name to the intended recipient. The mistake is noticed within the hour.
The recipient is a known professional, confirms in writing that the file was deleted unopened, and has no reason to misuse it. Remedial action has probably removed the likely risk of serious harm. This would usually be assessed as not eligible. It is still a breach, and it goes in the breach register with the reasoning.
A manager’s laptop is stolen from a car. It holds customer contracts and contact details.
The laptop uses full-disk encryption, the user was signed out, and the device management system shows it has not connected since the theft. Access to the information is unlikely. With evidence of encryption recorded, this would usually be assessed as not eligible. Without encryption, the same theft would probably be notifiable. The lost device playbook in the incident response playbooks guide covers the steps that produce that evidence.
An HR coordinator’s mailbox is accessed by an attacker for nine days. Audit records show the mailbox was synchronized in full. It contains job applications with passport scans, tax file numbers, and medical certificates.
Identity documents and health information were obtained by a criminal, for hundreds of people, and nothing done afterward can retrieve them. Every element of the test is met. This is an eligible data breach. The OAIC and the affected individuals are notified as soon as practicable.
A payroll provider tells its customers that an attacker copied files from its systems. The files include the names, bank details, and tax file numbers of the organization’s staff.
Both organizations hold the information, so both have obligations under the scheme. The organization’s own assessment starts when the supplier’s notice gives it grounds to suspect, and it depends on the supplier for evidence of what was taken. Bank details and tax file numbers in criminal hands make serious harm likely, and neither party can retrieve them. This is an eligible data breach. Only one of the organizations needs to notify, and OAIC guidance suggests it be the one with the most direct relationship with the individuals. Here that is the employer.
Each case turns on evidence. Proof of deletion, proof of encryption, audit records of access, and a supplier’s account of what was copied decided the outcome. A plan that ensures such evidence exists is worth more than one that only describes the steps.
An assessment has to produce a decision that can be defended later. In practice it runs as a short investigation with a fixed set of questions.
Set down what happened, when, and how it was discovered, which systems, accounts, or documents were involved, and whether the exposure has stopped.
This is usually the slowest step. For a misdirected file it takes minutes. For a compromised mailbox holding years of correspondence, it can take weeks.
The work is to find every piece of personal information in what was exposed. For mailboxes and file shares this means searching the content for identity documents, tax and health identifiers, bank details, and dates of birth, then building a list of the people concerned. Specialist review tools exist for this, and for large volumes a forensic or legal review provider is normally engaged.
Use audit records to separate what the attacker opened from what they could merely reach. Where a mailbox was synchronized or a share copied in bulk, treat all of it as taken. Where logs are missing, say so, and assess on the basis of what was accessible. The data exfiltration investigation guide covers the evidence in detail.
Apply the factors set out earlier to each group of affected people. The answer may differ between groups. Staff whose payroll details were exposed face a different risk from customers whose names and email addresses were.
Write down the conclusion, the reasoning, the evidence relied on, and who made the decision. Do this whether the outcome is to notify or not.
The 30 days pass quickly when content review is involved. Start the identification of personal information on day one, alongside the technical investigation, and prepare notification materials before the assessment concludes.
A notification to the OAIC must include the organization’s identity and contact details, a description of the breach, the kinds of information concerned, and recommended steps for individuals. A notice to affected people should cover the same ground in plain words.
A short factual account, with dates.
The specific types, for that person where possible.
Containment, and the steps taken to reduce harm.
Practical actions, such as replacing a document, changing passwords, or watching for scams.
The phone line or mailbox set up to answer questions.
Avoid statements the evidence cannot support. A notice that has to be corrected later damages trust more than an early notice that is honest about what is still unknown.
The scheme gives a choice of route. An organization can notify every individual whose information was involved, or only those at risk of serious harm. Where neither is practicable, it publishes the statement on its website and takes reasonable steps to publicize it.
Notifying a handful of people is a letter. Notifying thousands is a project, and plans that stop at “notify affected individuals” underestimate it.
The organization needs a current address, email, or phone number for each person. Former customers and past job applicants are often the hardest to reach.
Email is fastest. Where the breach involved the email system, or where recipients may suspect a scam, post or a notice on the website may be needed as well.
A staffed phone line or mailbox, with people briefed on what they can say. Call volumes peak in the first days.
Guidance on replacing identity documents, access to identity or credit monitoring where appropriate, and referral to support services.
Criminals follow breach announcements with phishing that pretends to come from the organization. Tell people how genuine contact will look.
Employees will be asked by customers, family, and sometimes media. Give them a short, accurate script.
Legal counsel and the insurer should see the notice before it goes, and the statement to the regulator is lodged first or at the same time. Where several organizations hold the same data, agree who notifies so people are not told twice or not at all.
The work continues after the notices are sent.
The regulator may ask how the breach occurred, what was done, and what has changed. The assessment record and incident log are the basis for the answers.
Individuals may complain to the organization or the regulator, or seek compensation. Keep records of every contact.
Identify the root cause and the changes needed. For a misdirected email that might be a delay-send rule and a check on external recipients. For a mailbox takeover it is stronger authentication and less data kept in mail.
Many serious breaches involve information that no longer needed to be held. Review what is kept, where, and for how long. Old identity documents in mailboxes are a common example.
With examples, so staff recognize one and report it.
Where to report a suspected breach, and how fast it is acknowledged.
Named roles, deputies, and contact details.
The test and factors above, with a form that records the reasoning.
Which regulators and contracts apply, the timeframes, and who approves a notification.
Draft wording for individuals, regulators, customers, and staff, with gaps for the facts. Notices prepared in advance save days.
Every breach, including those assessed as not notifiable. Patterns across several entries show where to invest.
What contracts require suppliers to report, and how quickly.
The incident response plan, the communications plan, and the insurance policy, with the point at which each is invoked.
Leads the assessment and recommends the decision.
Contain the breach and establish what was accessed.
Provide the evidence of what was and was not taken.
Advises on obligations, privilege, and contact with regulators.
Approves notifications and public statements.
Prepare notices and answer affected people.
In a small organization one person may hold several roles. The plan should still name who makes the notification decision, and who decides if that person is unavailable.
A single breach can trigger several duties at once, on top of the Notifiable Data Breaches scheme. Map them before an incident.
ThreatDefence provides the evidence a breach assessment depends on. Our responders establish which records were accessed or taken and over what period, and document the findings so they can support a notification decision.
We work alongside legal counsel and the insurer, help prepare the facts for a statement to the regulator, and keep the environment under 24x7 SOC monitoring during and after the response.
Experiencing a breach?
Our incident response team answers 24x7, with or without a retainer.
Explore Incident Response and DFIR
Discuss data breach readiness, forensic investigation, and 24x7 monitoring for your organization.
CountryAustraliaUnited StatesNew ZealandUnited KingdomCanadaSingaporeOtherI'm an MSP, MSSP, or reseller
Δ
A notification to the OAIC does not report the crime. Where a breach results from an attack, theft, or fraud, report it to police, and report the cyber incident to the Australian Signals Directorate through its ReportCyber service. Both reports are voluntary for most organizations and separate from the privacy notification. Critical infrastructure entities, and organizations that make a ransomware payment, have mandatory reports with their own timeframes.
The steps are to contain the breach, assess the information involved and the risk of harm, notify those who need to know, and review the cause. Containment and assessment usually run together, and notification can begin before the assessment is finished.
A breach is eligible when personal information has been accessed or disclosed without authorization, or lost where that is likely, when serious harm to at least one person is likely, and when remedial action has not removed that risk. A payroll file deleted unopened by a trusted recipient usually fails the test. A mailbox of passport scans synchronized by an attacker meets it.
The notification itself has no fixed number of days. Once there are reasonable grounds to believe an eligible data breach has occurred, the statement goes to the OAIC and individuals are told as soon as practicable. The 30 days applies earlier, to assessing a suspected breach, and is not permission to delay. An organization that already knows the breach is eligible notifies without waiting for day 30.
No. In Australia only eligible data breaches are notified to the OAIC and to individuals. A breach contained before serious harm became likely, such as an encrypted laptop that never reconnected, is recorded with the reasoning and goes no further. Contracts, APRA, and overseas privacy laws apply their own tests, so a breach that is not eligible under the Privacy Act can still need reporting elsewhere.
The organization that holds the information is responsible. Where a supplier holds data on the organization’s behalf, both may have obligations, and the contract should say who notifies. The decision to notify normally sits with the privacy lead and an executive, on legal advice.
A cyber incident is an event that compromises systems or security. A data breach involves information being accessed, disclosed, or lost without authorization, whether through a cyber incident or another cause. Many cyber incidents involve no data breach, and some breaches involve no attack.
Yes, where there are already reasonable grounds to believe the breach is eligible, or where people need to act quickly to protect themselves, for example by replacing an identity document or changing a password. Send what is established, say plainly what is still being investigated, and commit to an update. Legal counsel should review the wording before it goes.
Data Exfiltration Investigation
Incident Response Plan
Incident Response and DFIR Services