Still phishing: the Notifiable Data Breaches Scheme one year on
Rebecca Lindhout and Andrew Miers were published last week in the June edition of the Communications Law Bulletin discussing the Office of the Australia Information Commissioner’s recent Notifiable Data Breaches Scheme 12-month Insights Report. We are pleased to present a modified version of the article below.
Snapshot of the statistics
|Volume of notifications||As expected, the introduction of the NDB Scheme resulted in an increase in notifications of data breaches.
Reporting was fairly consistent during the year with 242 notifications during April – June 2018, 245 notifications from July – September 2018, 262 notifications from October – December 2018 and 215 notifications from January – March 2019.
|Cause of data breaches||Of the reported data breaches:
Malicious intent was the primary motivation behind most data breaches, with:
While the report distinguishes between data breaches caused by ‘malicious or criminal attacks’ and those caused by ‘human error’, it is worth noting that human error still plays a significant role in most malicious or criminal attacks as well. For example, while phishing incidents are initiated by a malicious actor, they only succeed when an employee falls for the trick and clicks on the offending link or enters their credentials.
Our experience of handling data breaches suggests that phishing emails, often leading to business email compromises, are rife in Australia. The Australian Cyber Security Centre has described business email compromise as the ‘major current cybercrime threat to business’. Apart from the potential for unauthorised access to personal information, business email compromise also often results in other significant business risks such as the sending of fraudulent payment requests.
|Affected data||The most commonly compromised data is contact information being 86% of personal information affected by data breaches. Often this will be in combination with other forms of data and it is that combination that can lead to the potency of the potential harm.|
Reducing the risk of credential compromise
Credential compromise includes phishing attacks which accounted for 39% of cyber incidents during the first year of the NDB Scheme. Phishing is where confidential information is stolen by sending fraudulent emails to victims. This becomes ‘spear phishing’ (i.e. more targeted phishing) when individuals or companies are specifically targeted based on company information sourced from publicly available sources such as annual reports and media releases.
To reduce the risk of credential compromise, the OAIC recommends that entities:
- Educate users on how to detect phishing emails and about password re-use and security measures;
- Implement multi-factor authentication and anti-spoofing controls such as DMARC or SPF; and
- Refer to their further guidance about preventing credential compromise.
We also recommend that entities:
- Rethink how they effectively secure the types of personal information they hold, including by implementing the Australian Cyber Security Centre’s “Essential Eight” Strategies to Mitigate Cyber Security Incidents (see here and here);
- Develop a cyber security policy (and then regularly review and update it);
- Prepare a cyber incident response plan (including incorporating a data breach response plan – see here for the OAIC’s guide); and
- Consider cyber security insurance to offset the cost of responding to cyber incidents and data breaches and potential losses that may arise. An entity’s cyber insurance policy will also often provide a breach response solution to assist in responding to an incident.
Managing Data Breaches
Putting individuals first
According to the Annual Report, one of the key areas where there is room for improvement is in putting individuals first.
IDCARE (a not-for-profit charity supporting individuals in Australia and New Zealand with identity and cyber security concerns) contributed to the Annual Report and noted a disparity between:
- The time taken between a data breach and misuse of those credentials (9.55 days);
- The average time taken for a breach to be detected (90 days); and
- The time then taken for individuals to be notified (a further 28.25 days).
IDCARE also notes a customer experience score of only 4.1 out of 10 for those affected by data breaches.
In light of the IDCARE insights into how quickly credentials are misused, time is clearly of the essence in both detecting breaches and notifying individuals so they can take preventative action to protect themselves. It is also key to notify individuals in plain English to minimise confusion and enhance trust as much as possible. The OAIC has included additional guidance on how to notify individuals and what to include in notifications in its guide to managing data breaches.
In our experience in dealing with data breaches, this also needs to be balanced against the desirability of not causing undue panic, the guiding principle perhaps being described as ‘be alert but not alarmed’.
Assessing the seriousness of harm in relation to a data breach
The OAIC noted that determining whether a data breach is an ‘eligible data breach’, particularly the likelihood of serious harm, is still a challenge for entities, particularly where the nature of the harm is less immediate but may still be serious. For example:
- Breaches involving contact information may result in that information being used in a phishing attempt which seems more real and so is more successful;
- Breaches involving contact information may result in threats to an individual’s safety (such as where a person who is the subject of domestic violence has their new address mistakenly disclosed to their attacker); and
- Breaches of personal information such as health information may result in damage to reputation or relationships or in workplace or social bullying.
Accordingly, the OAIC recommends taking a longer term approach to monitoring and responding to the risk of harm to affected individuals in the case of data breaches.
In our experience, the possibility of contact information being used in phishing attempts is one of the more common forms of potential harm to arise. However, a breach of contact information is also one of the more nebulous breaches to pin down in assessing the risk of harm since the potential impact is far more indirect and requires other intervening steps first to occur before any actual harm materialises.
Managing multi-party breaches
Eleven multi-party breaches were reported to the OAIC during the 12 months. A multi-party breach occurs where one or more entities hold personal information jointly – such as where it is owned by one entity and used by others. In these circumstances, each of the affected entities has obligations under the NDB Scheme but compliance by one entity will generally be taken as compliance by each of the entities who hold the information.
The OAIC suggests that the entity with the most direct relationship with the individuals affected by the data breach should make the notification. We think this stands to reason because, regardless of which third party might be responsible for the breach occurring, ultimately it is the reputation of the entity in direct relationship with the individuals whose reputation is on the line. That entity is going to want to have some control over the messaging.
Accordingly, the OAIC recommends that:
- Entities should ensure their contracts with suppliers (and other third parties) who have access to and use of their information address arrangements in the event of a data breach. This includes responsibility for gathering the relevant information, allowing access to premises and systems, responsibility for assessing the data breach, taking steps necessary to minimise the harm and prevent it recurring, and also responsibility for making any necessary notifications; and
- Entities’ data breach response plans should be consistent with the approach they agree in their third party contracts. Data breach response plans should also consider any international notifications which may also be required (eg under the GDPR).
Taking these steps will help:
- Minimise the likelihood of multiple notifications being made to the OAIC and to affected persons, which is likely to result in unnecessary confusion; and
- Allow entities and their suppliers (or other affected entities) to work in a collaborative manner which gives comfort about transparency and is also more likely to result in harm reduction.
Harm reduction and preventative measures
The Annual Report contains practical examples of actual breaches and drawn out suggestions from those breaches around harm reduction and preventative measures which can be implemented in the case of a data breach. These include:
- Where an employee’s email account was compromised:
- engaging an external firm to notify affected individuals, including advice to delete the phishing email, change their passwords and monitor their bank accounts; and
- implementing multi-factor authentication, a secure customer relationship management system for document transfer and additional staff training around spotting spoofed emails as preventative measures; and
- Where an entity became aware that an unknown third party had gained unauthorised access to some member accounts in its online portal:
- immediately notifying the individuals and deactivating the affected accounts;
- only reinstating the affected accounts with additional security measures such as CAPTCHA (i.e. “completely automated public Turing test to tell computers and humans apart”) and identity verification checks to prevent future unauthorised access; and
- where a data breach affected a vulnerable segment of the community, the affected entity used social workers to notify and provide support to affected individuals via phone.
The OAIC concluded that ‘the first year of the NDB Scheme has resulted in welcome improvements in transparency and accountability for the protection of personal information‘. With plenty of lessons and recommendations coming out of the first year of the NDB Scheme, including those set out in this alert, entities who focus on achieving an environment where privacy and security are core focuses rather than just a ‘compliance issue’ have the opportunity to enhance trust with their consumers and end users and differentiate themselves.
If you require assistance in equipping yourself to handle privacy and cyber risk, navigating the NDB Scheme, or find yourself unsure of how best to respond to a potential notifiable data breach, contact HWL Ebsworth to speak with our Privacy, Data Protection and Cyber Security Group.
This article was written by Andrew Miers, Partner and Rebecca Lindhout, Special Counsel.
P: +61 2 9334 8855
P: +61 2 9334 8725
Important Disclaimer: The material contained in this publication is of a general nature only and is based on the law as of the date of publication. It is not, nor is intended to be legal advice. If you wish to take any action based on the content of this publication we recommend that you seek professional advice.