ANU releases report on Data Trust and data privacy: a brake on the data and digital dividend

October 25, 2022

The ANU Centre for Social Research and Methods has released Data trust and data privacy: a brake on the data and digital dividend?   The timing couldn’t be more appropriate given the latest large scale data breaches.

The description of the paper provides:

Data is increasingly available at scale and many of the fastest growing companies are built on data and data analytics. Governments are also increasingly using data for service delivery and to a lesser extent policy development and evaluation. Regulating and managing the increasing availability and use of data by the public, community and private sectors requires new approaches and laws.

In April 2022 the Australian Parliament passed the Data Availability and Transparency Act 2022 which allows Australian Commonwealth bodies to share data. While the legislation and associated regulation is important, so are the levels of community data trust and attitudes to data privacy.

This paper reports data on Australian’s attitudes to data trust and data privacy and how these have changed since October 2018 using data from the ANUpoll series of surveys collected in October 2018, October 2019, May 2020, August 2021 and August 2022. This provides information on how attitudes have changed during the COVID-19 period and during a period of rapid digitisation and increasing availability and use of data. The data shows that trust in key institutions with regards to data privacy increased during the early stages of COVID-19 period, and has stayed high through to mid-2022.

Australians also for the most part think governments should be sharing data with researchers (particularly in universities) and making use of data internally. However, support for such uses of data is slipping. Part of the response to these trends is to make sure that when data is used, it is done so in a way that maximises benefits to society. Collectively, the Australian research and policy community also needs to better understand who is reluctant for their data to be used, why they are reluctant, and what the possible responses and safeguards might be to make better use of such resources whilst still maintaining a social licence.

Interesting points made in the Report Read the rest of this entry »

Federal Trade Commission takes action against Drizly and its CEO for security failures that exposed the data of 2.5 million cosumers

The Federal Trade Commission (“the FTC”) is taking action against Drizly, an online alcohol supplier, and its CEO, James Rellas, regarding a data breach that exposed personal information of 2.5 million consumers in 2020.  The data breach, it is alleged, was caused by security failures on Drizly’s part.

The core of the complaint is that Drizly:

  • failed to implement basic security measures.  They included not requiring employees to use two-factor authentication for GitHub, not limiting employee access to personal data, not having adequate written security policies, or failing to train employees on those procedure;
  • stored information on an unsecured platform. Drizly stored login credentials on GitHub contrary to the platform’s own guidance and well-publicized security incidents involving GitHub;
  • failed to monitor its network for security threats. The FTC specifically claimed that the failure included not putting a senior executive in charge of ensuring that the data was secure.  It did it monitor its network for unauthorized attempts to access or remove personal data; and
  • exposed its customers to hackers and identity thieves. After the data breach personal information that Drizly had collected about consumers was offered for sale on two different publicly accessible sites on the dark web.

The action is by way of administrative complaint, a precursor to formal litigation.  This has resulted in a consent agreement. It is a more assertive process than the Own Motion Investigation that the Australian Information Commissioner uses, on a very sparing basis, in Australia.

An interesting feature of this consent agreement is that the Chief Executive, James Rellas, is accountable for information security under the consent agreement, even if he leaves Drizly and works for another entity.  That is a procedure that the Australian Government should consider in its reforms of the Privacy Act.  Having the power to make orders against directors to ensure proper data security by way of enforceable undertakings would focus their minds.  With this approach the cost is not only to the business.  It is to its officers as well.  Having an order attached to a director wherever he or she went over a period would be something they would dread.

While the Australian enforceable undertakings are a pale version of what the FTC imposes on companies who have had a data breach or otherwise breached privacy it is worth reviewing how the FTC drafts its complaints and agreements.  They are the gold standard in terms of imposing comprehensive orders which enforce proper privacy practices over a 10 or 20 year period.  It is only a matter of time before Australia will move in this direction.

The statement provides:

The Federal Trade Commission is taking action against the online alcohol marketplace Drizly and its CEO James Cory Rellas over allegations that the company’s security failures led to a data breach exposing the personal information of about 2.5 million consumers. Drizly and Rellas were alerted to security problems two years prior to the breach yet failed to take steps to protect consumers’ data from hackers. The FTC’s proposed order requires the company to destroy unnecessary data, restricts the data that the company can collect and retain, and binds Rellas to specific data security requirements for his role in presiding over unlawful business practices.

“Our proposed order against Drizly not only restricts what the company can retain and collect going forward but also ensures the CEO faces consequences for the company’s carelessness,” said Samuel Levine, Director of the FTC’s Bureau of Consumer Protection. “CEOs who take shortcuts on security should take note.”

Boston-based Drizly, a subsidiary of Uber, operates an online marketplace where consumers of legal drinking age can place orders with retailers to buy beer, wine, and alcohol for delivery. The company collects and stores on Amazon Web Services cloud computing service a wide range of personal information from consumers such as email, postal addresses, phone numbers, unique device identifiers, geolocation information and data purchased from third parties.

According to the FTC’s complaint, Drizly and Rellas were alerted to problems with the company’s data security procedures following an earlier security incident. In 2018, a Drizly employee posted company cloud computing account login information on the software development and hosting platform GitHub. As a result of this security breakdown, hackers were able to use Drizly’s servers to mine cryptocurrency until the company changed its login information for its cloud computing account. Drizly failed to take steps to adequately address its security problems while publicly claiming to have appropriate security protections in place. Two years later, a hacker breached an employee account, got access to Drizly’s corporate GitHub login information, hacked into the company’s database, and then stole customers’ information.

In its complaint, the FTC alleges that Drizly and Rellas:

    • Failed to implement basic security measures: The FTC alleged that despite statements claiming the company used appropriate security practices to protect consumer data, Drizly and Rellas failed to put in place reasonable safeguards to secure the personal information it collected and stored. It did not require employees to use two-factor authentication for GitHub, limit employee access to personal data, develop adequate written security policies, or train employees on those procedures.
    • Stored critical database information on an unsecured platform: According to the FTC’s complaint, Drizly stored login credentials on GitHub contrary to the platform’s own guidance and well-publicized security incidents involving GitHub. For example, in its 2018 complaint against Uber, the FTC specifically publicized and described poor security practices involving the use of Uber’s GitHub account that contributed to a data breach involving the ridesharing app.
    • Neglected to monitor network for security threats: The FTC alleged that Drizly did not put a senior executive in charge of ensuring that the company was keeping its data secure, nor did it monitor its network for unauthorized attempts to access or remove personal data.
    • Exposed customers to hackers and identity thieves: Following the company’s data breach, personal information that Drizly had collected about consumers was offered for sale on two different publicly accessible sites on the dark web, where criminals post and sell data stolen by hackers. Identity thieves and other malicious actors can use such data to open fraudulent lines of credit or commit other fraud. When unauthorized accounts are opened in their name, consumers can suffer financial harm by incurring debt and damaging their credit, the FTC alleged.

Enforcement Action

The proposed order against Drizly and Rellas includes several requirements aimed at ensuring they take steps to address the problems outlined in the FTC’s complaint. Under the proposed FTC order, Drizly and Rellas are required to:

    • Destroy unnecessary data: Drizly is required to destroy any personal data it collected that is not necessary for it to provide products or services to consumers. It must also document and report to the Commission what data it destroyed.
    • Limit future data collection: Going forward, Drizly must refrain from collecting or storing personal information unless it is necessary for specific purposes outlined in a retention schedule. It must also must publicly detail on its website the information it collects and why such data collection is necessary.
    • Implement an information security program: Drizly is required to implement a comprehensive information security program and establish security safeguards to protect against the security incidents outlined in the complaint. This includes measures such as providing security training for its employees; designating a high-level employee to oversee the information security program; implementing controls on who can access personal data; and requiring employees to use multi-factor authentication to access databases and other assets containing consumer data.

Notably, the order applies personally to Rellas, who presided over Drizly’s lax data security practices as CEO. In the modern economy, corporate executives frequently move from company to company, notwithstanding blemishes on their track record. Recognizing that reality, the Commission’s proposed order will follow Rellas even if he leaves Drizly. Specifically, Rellas will be required to implement an information security program at future companies if he moves to a business collecting consumer information from more than 25,000 individuals, and where he is a majority owner, CEO, or senior officer with information security responsibilities.

This action is part of the FTC’s aggressive efforts to ensure that companies are protecting consumers’ data and that careless CEOs learn from their data security failures. Last year, the Commission secured its first order requiring a firm to minimize data collection and has worked in subsequent orders to ensure companies only collect what they need to conduct their business. The Commission is also taking steps to bolster security market-wide, including by finalizing updates to the Safeguards Rule, issuing a policy statement on the Health Breach Notification Rule, and initiating an advance notice of proposed rulemaking on commercial surveillance and lax data security practices.

The FTC voted 4-0 to issue the proposed administrative complaint and to accept the consent agreement with Drizly and Rellas. Commissioner Christine Wilson voted yes but dissented in part as to the inclusion of Rellas as an individual defendant and issued a separate statement. Chair Lina M. Khan and Commissioner Alvaro Bedoya issued a joint concurring statement and Commissioner Rebecca Kelly Slaughter issued a separate concurring statement.

The FTC will publish a description of the consent agreement package in the Federal Register soon. The agreement will be subject to public comment for 30 days after publication in the Federal Register after which the Commission will decide whether to make the proposed consent order final. Instructions for filing comments will appear in the published notice. Once processed, comments will be posted on Regulations.gov.

NOTE: The Commission issues an administrative complaint when it has “reason to believe” that the law has been or is being violated, and it appears to the Commission that a proceeding is in the public interest. When the Commission issues a consent order on a final basis, it carries the force of law with respect to future actions. Each violation of such an order may result in a civil penalty of up to $46,517.

Read the rest of this entry »

European Data Protection Board releases guidelines on personal data breach notification under the GDPR… excellent timing given the spate of data breaches in Australia

October 24, 2022

The timing couldn’t be better.  The European Data Protection Board (“EDPB”)  released Guidelines 09/2022 on personal data breach notification under GDPR on 18 October 2022. Given the issue of notification of data breaches is a significant issue currently in Australia it is a very relevant document.  More importantly the guidelines on privacy and data breach issues are much more comprehensive in the EU and the UK.  That makes for better and more effective systems and protections, if followed.

The announcement provides:

The European Data Protection Board welcomes comments on the Guidelines 09/2022 on personal data breach notification under GDPR. The targeted update and this public consultation concern paragraph 73 of the Guidelines (marked in yellow in the document). Such comments should be sent 29th November 2022 at the latest using the provided form.

Please note that, by submitting your comments, you acknowledge that your comments might be published on the EDPB website.

The EDPB Secretariat staff screens all replies provided before publication (only for the purpose of blocking unauthorised submissions, such as spam), after which the replies are made available to the public directly on the EDPB public consultations’ page. Unauthorised submissions are immediately deleted. The attached files are not altered in any way by the EDPB.

Please, note that regardless the option chosen, your contribution may be subject to a request for access to documents under Regulation 1049/2001 on public access to European Parliament, Council and Commission documents. In this case the request will be assessed against the conditions set out in the Regulation and in accordance with applicable data protection rules.

All legal details can be found in our Specific Privacy Statement (SPS).

The guidelines are referable to obligations under the GDPR.  That said they contain best practice processes when dealing with the data breaches.  To that extent they are a very valuable resources in the Australian context in providing structure in anticipating and responding to a data breach.  Some points worth noting are:

  • the benefits of notification include the controllers obtaining advice on whether the affected individuals need to be informed. The supervisory authority may order the controller to inform those individuals about the breach.
  • communicating a breach to individuals allows the controller to provide information on the risks presented as a result of the breach and the steps those individuals can take to protect themselves from its potential consequences.
  • the focus of any breach response plan should be on protecting individuals and their personal data. Breach notification should be seen as a tool enhancing compliance in relation to the protection of personal data.
  • controllers and processors are encouraged to plan in advance and put in place processes to be able to detect and promptly contain a breach, to assess the risk to individuals, and then to determine whether it is necessary to notify the competent supervisory authority, and to communicate the breach to the individuals concerned when necessary. Notification to the supervisory authority should form a part of that incident response plan
  • GDPR requires:
    • both controllers and processors to have in place appropriate technical and organisational measures to ensure a level of security appropriate to the risk posed to the personal data being processed which should take into account:
      • the state of the art,
      • the costs of implementation
      • the nature,
      • the scope,
      • context and
      • purposes of

Read the rest of this entry »

The Commonwealth Government to increase fines for serious data breaches to either 30% of turnover or $50 million whichever is the larger

October 22, 2022

The Attorney General has announced proposed amendments to the Privacy Act to increase the potential size of penalty for a serious or repeated privacy breaches.  They will be increased to the greater of:

  • $50 million;
  • 3 times the value of the benefit obtained through the misuse of the data; or
  • 30% of the coThe jmpany’s adjusted turnover in the relevant period.

The statement provides:

Image

The reports do not say what the penalty to Government agencies will be in the event of a serious data breach.  Clearly the turnover calculation will not apply.

Currently penalties for serious and repeated interferences with privacy are found in section 13G of the Privacy Act 1988.  It provides:

An entity contravenes this subsection if:

                     (a)  the entity does an act, or engages in a practice, that is a serious interference with the privacy of an individual; or

                     (b)  the entity repeatedly does an act, or engages in a practice, that is an interference with the privacy of one or more individuals.

Civil penalty:          2,000 penalty units.

Under the Privacy Act the Commissioner must commence civil penalty proceedings in the Federal Court to seek penalties under section 13G.  The process Read the rest of this entry »

Information Commissioner starts investigation into Medibank while cyber gang escalates its demands…the data breach is taking on the appearance of a saga.

October 21, 2022

The Office of the Information Commissioner announced today that it was “making inquiries into Medibank.” The ostensible reason was to ensure that it complied with the Notifiable Data Breaches Scheme.  Given the circumstances it had ample power to do an own motion investigation in any event.  Given Medibank’s spluttering initial response to the data breach it is not surprising that this is the basis chosen.

The OIAC media release provides:

The Office of the Australian Information Commissioner (OAIC) is making preliminary inquiries with Medibank following its cyber incident, to ensure compliance with the requirements of the Notifiable Data Breaches (NDB) scheme.

As information is gathered and assessed, the number one priority is ensuring that Medibank customers have information and resources available to take steps to protect themselves from any risk arising as a result of their personal information being compromised.

“This matter is understandably of great concern, given the sensitive information that may be involved,” Australian Information Commissioner and Privacy Commissioner Angelene Falk said. Read the rest of this entry »

Medibank data breach…threats to expose personal information and demands for ransom….Why is this news? It happens on a weekly if not daily basis. That is what criminal hackers do. The key is to get companies to properly protect their data

What do criminals do?  They act for profit.  Cyber criminals are still just criminals.  They steal for monetary gain.  Ransomware and just plain demanding ransoms is part of their weaponary.  Exposing health and other personal information happens if the crooks think that will get the money they are after.

As the Guardian reports in Medibank says sample of stolen customer data includes details of medical procedures, the data stolen from Medibank includes details of medical procedures.  The Australian has an article in a similar vein with Medibank hackers stole data on medical conditions customers and treatment.  This shouldn’t be surprising.  What is less understandable is how the sensitive health data was commingled with other records?  Why was it not properly encrypted?  Why wasn’t it siloed?

I have been writing on cyber security and data breaches for so long that I find the breathless quality of Australian media reporting of the Medibank data breach curious.  It is as if this is the only and worst data breach involving health records.  It isn’t by a long chalk.  The Sydney Morning Herald writes of ‘Immense harm’: Federal police investigating threat to sell Australians’ health data.  While the Australian enters into policy speculation with Medibank hack sparks call to end companies creating data ‘honeypots’ for hackers. Where the Australian gets it wrong is that under the current Privacy Act collection of personal information should only be for a specific purpose and used for that purpose.  The legislation is deeply flawed but if properly enforced action should have been taken against companies who collect and hold onto data because it suits them.  The enforcement was weak.  It has always been weak.  Until now no Government has not much cared.

The key is for companies to take their responsibilities seriously.  That means proper regulation and enforcement whereby the cost of non compliance is high.  The next issue is to make sure that when there is a data breach it is dealt with methodically and thoroughly and not turned into a cause celebre.  It helps not at all if it becomes a political battleground.  The company affected has to respond appropriately and quickly and the regulator may need to get involved.  There will always be media coverage but it shouldn’t develop a life of its own as seems to be the case with the latest spate of data breaches in Australia.  It is always worth remembering that it is a legal issue, complying with the law.

The Australian Financial Review undertakes an analysis and critique of Medibank’s responses so far with Medibank’s ransomware response is a lesson in what not to do. It is replete with talking heads  wanting to get their name out as experts prognosticating on this,  that or other things relating to the Medibank data breach.  Much of it is speculation over analysis.  That said  the Medibank response has been dreadful, as bad as Optus but in a different way.  Going through its media releases has been the privacy equivalent of a slow motion car crash involving a crash test dummy. Whatever data breach response plan it had was sub standard.  The first 24 hours should be regarded as the Golden Hours.  Getting as much information about the breach, starting on remediation and crafting a notice to the market, the clients, to government and the media is critical. Information to hand will always be incomplete but being as forthcoming

It’s latest update, Medibank cyber incident response,  provides:

As we have worked through this cyber incident, Medibank has committed to transparency about what we know, and how that could impact our customers, our people, and the broader community.

This cyber incident is now the subject of an investigation by the Australian Federal Police.

We know that our customers, people, and the community want to know what data has been stolen, and how that may affect them. Read the rest of this entry »

Cyber Security Minister O’Neil states that relentless cyber attacks are here to stay…Right but they have always been here but governments were not paying attention. The problem is now data breaches are becoming an ongoing political rather than legal issue

October 20, 2022

The sub editors are earning their keep coming up with ever more dramatic headlines for cyber attack stories.  It is as if data breaches were a new phenomenon.  They aren’t.  I have been writing about data breaches and privacy and cyber security for over a decade.  What has changed things is the Optus Data Breach that affected almost half the population in one way or another.

The Home Affairs Minister Clare O’Neil has echoed earlier statements by ministers that the Medibank cyber attack is a huge wake up call.  The problem is that this wake up call has been made by civil society groups and commentators for years.  It was ignored by both sides of politics.  This sudden interest in cyber security and privacy by a government reminds me of a conversation I had with Professor George Williams during a break at a legal conference years ago.  I was bemoaning the ineffective privacy protections in legislation and the lack of options at common law and equity.  He said that reform will come with a major privacy incident which gets the governments attention or convinces the courts of an unacceptable gap in legal protections.  How prescient were those comments.  The Optus and Medibank data breaches seems to have achieved the former.  Or at least the promise of the former.  Hopefully the courts will recognise the protections at common law and equity are wholly inadequate.

Now MInisters are inserting themselves into every significant data breach.  That has all the makings of poor policy.  It is relatively unusual for governments and their ministers to insert themselves into the middle of a cyber attack.  There have been exceptions, usually for extraordinary events, but on the whole it is a matter for the regulator, the affected organisation, the various experts brought in to fix the mess and sometimes the insurer.  Later the courts Read the rest of this entry »

Medibank Private halts trading when hackers contact to negotiate regarding possibly stolen data

October 19, 2022

Medibank Private’s woes continue as the ABC reports in Health insurer Medibank Private halts trading after receiving message from company claiming to be behind cyber attack when it was contacted by a group wanting to negotiate the return of stolen data.  Nothing has been verified, or at least publicly identified, but Medibank Private notified the ASX to put a halt to the trade in its shares. The Australian Financial Review, in Medibank ransom demand targets politicians, actors, LGBT activists,  claims that the hackers were demanding ransom to prevent the release of health and credit card information. The Sydney Morning Herald, in Medibank hackers threaten to release stolen health data in ransom demand, claims to have seen the ransom note.

Dealing with hackers who plant ransomware or those who simply exfiltrate data and then ransom in back to the organisation who is usually very keen to avoid more humiliation and cost has become a niche industry.  Just as hackers have developed sophisticated processes for payment and negotiation there are people who have an expertise in negotiating with those hackers and sometimes outwitting them. There is an excellent article in the 31 May 2021 of the New Yorker titled How to Negotiate with Ransomware Hackers which gives a little bit of an insight into this murky world. The Australian also ran a similar, but lesser, story ‘They demanded $1m in 72 hours’: your money or your data.   The official government advice is not to pay ransoms.  The reality is much more nuanced.  Payments are made.  And hackers often to abide by their side of an agreement.  But not always.  And then there are the middling results where the hackers provide ransom keys but upon unlocking the ransomed data some or much of the data is corrupted.  Sometimes the hackers only return some of the data, sometimes intentionally and sometimes by accident.  Being a crook does not mean they are good administrators. 

The answer is always to maintain proper cyber security.  That doesn’t just mean having up to date programs.  It means making sure the human element is covered.  Staff need to be trained and there needs to be systems to avoid lax security occurring.

The ABC article provides:

Health insurer Medibank Private has confirmed they have received messages from a group wishing to negotiate with the company regarding their alleged removal of customer data.

The update comes less than a week after the company was hit by a cyber attack

Medibank says they are working urgently to establish if the claim is true, but are treating the matter seriously.

As a result of this, the health insurer has halted trading on the share market until further notice.

Medibank CEO David Koczkar has apologised to customers and said he understood the latest update was distressing. 

“We have always said that we will prioritise responding to this matter as transparently as possible,” Mr Koczkar said.  Read the rest of this entry »

National Institute of Standards and Technology releases report: Profile of the IoT Core Baseline for Consumer IoT Products

The Internet of Things is a key part of any cyber security and privacy.   The National Institute of Standards and Technology (“NIST”) has released a very important report on IoT baselines, titled Profile of the IoT Core Baseline for Consumer IoT Products.

The Abstract provides:

This publication documents the consumer profile of NIST’s IoT core baseline and identifies cybersecurity capabilities commonly needed for the consumer IoT sector (i.e., IoT products for home or personal use). It can also be a starting point for small businesses to consider in the purchase of IoT products. The consumer profile was developed as part of NIST’s response to Executive Order 14028 and was initially published in Recommended Criteria for Cybersecurity Labeling for Consumer Internet of Things (IoT) Products. The consumer profile capabilities are phrased as cybersecurity outcomes that are intended to apply to the entire IoT product. This document also discusses the foundations to developing the recommended consumer profile and related considerations. NIST reviewed a landscape of relevant source documents to inform the consumer profile and engaged with stakeholders across a year-long effort to develop the recommendations.

At 30 pages it is a relatively brief NIST publication.  That does not mean it is not technical and dense.

Some interesting points Read the rest of this entry »

An article that universities are at particular risk of a cyber attack….that was news 10 years ago. But it is worth saying it again now governments in Australia are sort of taking privacy seriously

Sometimes it feels like the the last decade of writing and reporting on privacy never existed.  Articles are being written and statements made portentously with a breathless quality about a cyber threat here or a privacy harm there as if it was never said before.  The Australian’s Universities are at particular risk of cyber attack is a classic example of this reheating of well known facts and previous commentary of a phenomana that has been well known and understood for many years but written as if it is some sort of revelation. 

Universities are and have always been a focus for espionage and theft of information, sometimes by state actors and sometimes by criminals who can see a financial pay day in stealing commercial information.  During the Cold War, the analog era, universities were engaged to do sensitive defence related research.  There was a constant competition between those screening staff and protecting information and those intent on  trying to corrupt or turn staff and otherwise purloin information.  In the digital era this issue has taken on new dimensions with much more information, including personal information on a massive scale, and many more ways of accessing it.  Universities are notorious for having inadequate cyber protection often because of multiple systems being cobbled together after mergers or rationalisations.  The authorisation policies are lax and the training is poor.

I have posted on data breaches at the University of Western Australia, Deakin University, University of Tasmania, Australian Catholic University, Australian National University and  the University of Greenwich.

The article says Read the rest of this entry »