Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Threat Intelligence

9/16/2019
02:00 PM
50%
50%

Court Rules In Favor of Firm 'Scraping' Public Data

US appeals court said a company can legally use publicly available LinkedIn account information.

If you make data public online, can someone be prevented from using it? HiQ Labs (a data analytics company) said "no," LinkedIn said "yes," and now a federal court has agreed with HiQ in the latest courtroom round of a case that could have significant implications for securing enterprise data.

HiQ Labs scrapes information from LinkedIn profiles that users have set to be viewable to the Internet at large. It then combines that data with public data gleaned from other websites, and sells the results to employers looking for more insight into potential employees.

LinkedIn reportedly at first appeared to have no problem with the practice, but after launching its own somewhat similar service, served HiQ with a cease-and-desist letter which the smaller company has fought.

According to a report by Vice LinkedIn claimed that access to this public data violated the Computer Fraud and Abuse Act (CFAA). The Ninth Federal Circuit Court of Appeals ruled that, because the data belongs to the individual LinkedIn user and those users obviously intended it to be widely available, HiQ is breaking no laws in finding and using the data.

At its heart, the legal issue is over the definition of "authorized use" of data — something that security professionals must consider in many cases of deciding whether legal remedies can be sought for individuals and companies accessing data that is available through a Web interface. LinkedIn is likely to appeal this verdict.

For more, read here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Cybersecurity Industry: It's Time to Stop the Victim Blame Game
Jessica Smith, Senior Vice President, The Crypsis Group,  2/25/2020
Google Adds More Security Features Via Chronicle Division
Robert Lemos, Contributing Writer,  2/25/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9431
PUBLISHED: 2020-02-27
In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the LTE RRC dissector could leak memory. This was addressed in epan/dissectors/packet-lte-rrc.c by adjusting certain append operations.
CVE-2020-9432
PUBLISHED: 2020-02-27
openssl_x509_check_host in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.
CVE-2020-9433
PUBLISHED: 2020-02-27
openssl_x509_check_email in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.
CVE-2020-9434
PUBLISHED: 2020-02-27
openssl_x509_check_ip_asc in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.
CVE-2020-6383
PUBLISHED: 2020-02-27
Type confusion in V8 in Google Chrome prior to 80.0.3987.116 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.