Australia: New mandatory data breach notification laws

Last Updated: 22 May 2017
Article by Dudley Kneller

Australia has recognised the need to manage data breach events more effectively and ensure that affected individuals are notified in relevant circumstances.


On 13 February 2017, the Australian Senate passed the Privacy Amendment (Notifiable Data Breaches) Bill 2016 (Cth) (the Bill). The Governor-General gave formal assent to the Bill on 22 February 2017, which will now see the Bill enacted into law from 22 February 2018.

It has taken some time for Australia to finally introduce a breach notification law. After a series of "false starts" in 2013 and 2014 Australia now has a notification obligation in place for notifying data breaches. Despite updating privacy laws in March 2014, Australia has been lagging behind other countries in relation to data breach notification obligations.

A number of States in the US have had data breach notification laws in place for some time. California, upon which many States have based their own laws, has had legislation in place since 2003. At the time of writing, 48 US States, the District of Columbia, Guam, Puerto Rico and the Virgin Islands have enacted legislation requiring private or governmental agencies to notify individuals of security breaches of information involving personal information.

Whilst there has now been a change in office, in January 2015, then US President Obama proposed a national data breach notification standard in the draft Personal Data Notification and Protection Act. The proposed scheme would require notification if there is any reasonable risk of harm or fraud to individuals following a data breach. It is not clear what plans the current Trump administration has for such a scheme noting it has not been high on the Trump agenda.

The European Union, as well as New Zealand, have both introduced breach notification laws. On 16 June 2015, Canada passed legislation to introduce a national mandatory data breach notification scheme.

It would therefore seem timely that Australia too has now recognised the need to manage data breach events more effectively and ensure that affected individuals are notified in relevant circumstances.

Where does the new data notification law fit in?

The law will complement Australia's existing privacy laws which are set out in the Privacy Act 1988 (Cth) (Privacy Act). The Privacy Act lists 13 Australian Privacy Principles, or APPs, which broadly apply to APP entities and which regulate how those organisations collect, store, manage and disclose personal information in Australia. There are some limited exceptions for organisations with less than $3 million in annual revenue, although the broad nature of the Privacy Act often brings smaller organisations back into play. Those organisations who deal with health related information and those working under Australian Government contracts are necessarily affected.

The details – what, who and how?


The Bill will specifically bolster the operation of APP 11 which requires entities to take such steps as are reasonable in the circumstances to protect personal information they hold from misuse, interference and loss, and from unauthorised access, modification or disclosure.

The Bill is intended to cover data breach events. The Explanatory Memorandum at 7 states that "a data breach arises where there has been unauthorised access to, or unauthorised disclosure of, personal information about one or more individuals (the affected individuals), or where such information is lost in circumstances that are likely to give rise to unauthorised access or unauthorised disclosure."


As noted above, the law will apply to entities required to comply with the Privacy Act.


An APP entity must notify the Australian Information Commissioner (the Commissioner) and affected individuals once it has reasonable grounds to believe there is an "eligible data breach." An "eligible data breach" occurs when:

  • there is unauthorised access to, or disclosure of, information, and a reasonable person would conclude that the access or disclosure would likely result in serious harm to any of the individuals to whom the information relates; or
  • information is lost in circumstances where unauthorised access to, or unauthorised disclosure of, information is likely to occur and, if it did occur, a reasonable person would conclude that the access or disclosure would be likely to result in serious harm to any of the individuals to whom the information relates.

Entities must consider whether it is likely that the data breach will result in "serious harm" to any of the affected individuals. In assessing this requirement, if a single individual is likely to suffer serious harm, then the entity will be required to notify under the Privacy Act.

There may be some exceptions which will apply, which are discussed further below. In the meantime it is important to understand some of the threshhold issues.

So what does "serious harm" mean?

The Bill's Explanatory Memorandum provides some guidance for affected entities. Serious harm can include the following:

  • serious physical, psychological, emotional, economic and financial harm, as well as serious harm to reputation and other forms of serious harm that a reasonable person in the entity's position would identify as a possible outcome of the data breach (at 9).

The Explanatory Memorandum does attempt to provide some helpful guidance for entities. It states that whilst individuals may be distressed or otherwise upset at an unauthorised access to or unauthorised disclosure or loss of their personal information, this would not itself be sufficient to require notification unless a reasonable person in the entity's position would consider that the likely consequences for those individuals would constitute a form of serious harm.

It seems therefore that some flexibility in determining when to notify is available to entities which was not otherwise a feature of earlier proposed breach legislation.

What should the notification say?

If an entity suspects that an eligible data breach has occurred, it must undertake an assessment into the relevant circumstances. In the event of an eligible data breach, an entity is required to notify the Commissioner and affected individuals as soon as practicable after the entity is aware that there are reasonable grounds to believe that there has been an eligible data breach (unless an exception applies). The notification must include:

  • the identity and contact details of the entity;
  • a description of the serious data breach;
  • the kinds of information concerned, and
  • recommendations about the steps that individuals should take in response to the serious data breach.

Whilst details relating to identity, affected information and contact details may sometimes be readily determined (although not in every case) other details may not be so easily included. When a breach event occurs the reality is far from straightforward. Often there is confusion as the organisation tries to establish the extent of the breach, and respond, minimise damage and restore affected systems. The uncomfortable reality is that breach events can evolve over time with sophisticated hackers often updating their own malware to defeat containment strategies from the affected organisation.

This can make it a challenge to comply with the notification obligations to include required information.

We need to notify, but how do we do it?

So you have determined that you need to notify an eligible breach and you are aware of what information needs to be included. But how do you go about it?

There are three options available to notify affected individuals.

An entity can choose one of the following:

  • if it is practicable to do so, take such steps as are reasonable in the circumstances to notify each of the individuals to whom the relevant information compromised in an eligible data breach relates, or
  • if it is practicable to do so, take such steps as are reasonable in the circumstances to notify those individuals who are considered to be at risk of serious harm from the eligible data breach, or
  • if it is NOT practicable to notify via either of the above methods, notify the individuals by publishing the statement on the entity's website and taking reasonable steps to publicise the statement. Examples of this option may include taking out advertisements in newspapers and online, social media platforms etc.

As you will note from the above, the common consideration is whether it is "practicable" for the entity to notify using the particular option. Consideration such as the cost involved in notifying, time and effort all need to be taken into account.

For data breaches involving a number of affected individuals spread across different states, an organisation may opt to notify via website, print and social media.

For a breach involving a smaller number of affected individuals whom the entity can readily identify as at risk of serious harm the entity is more likely to implement the second option.

In the case of an extensive breach compromising a number of databases containing user or account information it may not be immediately apparent which individuals are impacted. In this case notifying the entire group will allow potentially affected individuals to assess their own situation and take steps to update passwords, retrieve information or close accounts etc.

Every breach situation is likely to be different and it is therefore important that entities have a process in place around effective notification which takes likely breach scenarios into account.

Are there any exceptions to the notification requirements?

The Explanatory Memorandum includes some exemptions which are important to consider.

Certain government agencies including law enforcement bodies will not be required to notify affected individuals if compliance with this requirement would be likely to prejudice law enforcement activities.

If notification would be inconsistent with another Commonwealth law that regulates the use or disclosure of information, an entity will be exempt to the extent of the inconsistency. If compliance would be inconsistent with another law of that kind which is prescribed in regulations under the Privacy Act, an entity will be exempt from the notification requirement.

Finally, to avoid creating a double notification requirement, an unauthorised access, unauthorised disclosure or loss of personal information cannot give rise to an eligible data breach if that access, disclosure or loss has been, or is required to be, notified under the mandatory data breach notification requirement in s 75 of the My Health Records Act 2012 (Cth).

These are fairly limited exemptions. Are there any other exemptions which may be relevant?

Whilst the various exemptions listed above are important and will apply in those limited circumstances, the Bill does include further exemptions which will be of interest to a broader number of entities. An additional exemption applies where entities have taken remedial action following an eligible data breach or potential eligible data breach.

Specifically, this exemption applies where a reasonable person would conclude that, as a result of the remedial action, the unauthorised access or unauthorised disclosure of personal information (including an unauthorised access or unauthorised disclosure following loss of the information) is not likely to result in serious harm to the affected individuals.

An entity that promptly and effectively responds to a data breach through remedial action will not be required to comply with the notification requirements if, as a result of actions taken by the entity, the breach is not likely to, or does not, result in serious harm.

Clearly there is likely to be an inherent tension between entities required to notify under the Bill and the same entities taking all the steps they can to avoid notification by taking remedial action.

It is also open for an affected entity to apply to the Commissioner for an exemption to the notification obligation. Such exemptions are likely to apply in circumstances where an organisation may be assisting a law enforcement body or regulatory body such as the Australian Signals Directorate in relation to enforcement/investigation activities relating to a breach event, or where an organisation is itself working through a complex breach event and where notification may be more prejudicial to affected persons in the circumstances.

Entities may also apply to the Commissioner for an exemption from, or an extension of time to comply with, the notification requirements, and would not be required to comply until the Commissioner has decided the application.

A final exemption will be of interest to entities in a group structure or forming part of a joint venture or similar arrangement. In such circumstances, if more than one entity jointly and simultaneously holds the same particular record of personal information, an eligible data breach of one entity may also be an eligible data breach of each of the other entities. The exemption is intended to assist entities who may be involved in an outsourcing, shared service or joint venture arrangement.

Where one of these affected entities demonstrates its compliance with the assessment and notification obligations in the new Part IIIC, the remaining entities are taken to have also complied.

What are the penalties for failure to comply with the notification requirements?

Failure to comply with an obligation included in the Bill will be deemed to be an interference with the privacy of an individual for the purposes of the Privacy Act.

Such a failure to comply can result in affected individuals filing a complaint with the Commissioner, prompting an investigation of the entity. The Commissioner may also investigate without a complaint being made and may issue a determination requiring the entity to:

  • compensate such individuals for any loss or damage suffered; or
  • take actions to redress any loss or damage or steps to ensure that an entity's conduct is not repeated or continued.

If the failure to comply with notification requirements is "serious or repeated", entities may be liable for penalties of up to $1.8 million ($360,000 for individuals).

Wrap up

The advent of the Privacy Amendment (Notifiable Data Breaches) Act 2017 (Cth) and its incorporation into the Privacy Act tops off a flurry of regulator activity in the privacy space. What began life originally as a Private Member's Bill introduced by Senator Natasha Stott-Despoja in 2007 has evolved over time, been updated, lapsed and subsequently re-introduced, modified and finally passed.

It comes at a time where cyber breach events are on the rise with organisations relying more and more on technology to engage with customers, suppliers and the world at large. With this engagement comes increased responsibility and accountability to manage information securely and ensure it is protected from unauthorised use and disclosure.

The breach notification regime will be a welcome addition to the Commissioner's arsenal. The Australian Privacy and Information Commissioner, Timothy Pilgrim has been waiting patiently. His 13 February 2017 statement is clear in its intent:

The new scheme will strengthen the protections afforded to everyone's personal information, and will improve transparency in the way that the public and private sectors respond to serious data breaches.1

Whilst the Commissioner has been assisting entities to deal with breaches for some time through its "Data breach notification — a guide to handling personal information security breaches"2 and "Guide to developing a data breach response plan"3, we expect such guides to be updated with a new level of vigour. All Australian entities subject to the Privacy Act will need to respond quickly and ensure their processes and procedures adhere to the new notification laws ideally well in advance of the 22 February 2018 date of introduction.


1 Australian Privacy and Information Commissioner, Timothy Pilgrim "Mandatory data breach notification" Statement (13 February 2017), available at < HTTPS://WWW.OAIC.GOV.AU/MEDIA-AND-SPEECHES/STATEMENTS/MANDATORY-DATA-BREACH-NOTIFICATION#MANDATORY-DATA-BREACH-NOTIFICATION > (accessed 3 May 2017)

2 Office of the Australian Information Commissioner Data breach notification — a guide to handling personal information security breaches August 2014, accessed 3 May 2017,

3 Office of the Australian Information Commissioner Guide to developing a data breach response plan April 2016, accessed 3 May 2017,

Client Disclaimer

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances. Madgwicks is a member of Meritas, one of the world's largest law firm alliances.

Direct To Live SETLIVE

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Some comments from our readers…
“The articles are extremely timely and highly applicable”
“I often find critical information not available elsewhere”
“As in-house counsel, Mondaq’s service is of great value”

Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.