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.

89% of Android Users Didn't Consent to Facebook Data Collection
Newest First  |  Oldest First  |  Threaded View
User Rank: Ninja
4/11/2018 | 12:15:19 PM
Informed consent
@Pyker42  Yes, ISVs are burdened with TOS and EULAs, as well.  Perhaps standardized agreement forms, at the  vetted distribution-store level, would help.  Part of the agreement would be that all permissions would be off by default - leaving the end user to enable each explicitly.  At the very least, the user would be made aware that all of the functionality they crave comes at a price; and that it's up to them to determine if it's worth it.  A benefit would be that while users would still have the responsibility to read the ToS/EULA/privacy notice, they'd only have to read ONE for any app they install from that store-vendor.  While that wouldn't cover the likes of Facebook, it could help the app publishers and end users.  
User Rank: Strategist
4/11/2018 | 11:17:19 AM
Re: Comment
While I agree that TOS and EULA contracts are heavily weighted to favor the companies issuing them, that doesn't negate the fact that most users never read eaither before proceeding. Android is especially easy with permissions. Every new app gives you general categories with specific permissions granted to that app. There is blame to be put on companies like Facebook, Google, Apple, Microsoft, etc. But there is equal blame to be put on the people who use those services without realizing the implications of the data rights they are granting these companies. I agree that such services are ubiquitous and hard to eschew all together. That doesn't absolve people of their personal responibility to conciously think about what they are doing, what they are using, and what information they are sharing.
User Rank: Ninja
4/10/2018 | 12:43:26 PM
Re: Comment
Important point.  In general, TOS have been very unfair to consumers.  It's not enough to include wording such as "Read the Terms of Service and Privacy Statements carefully before...".  For starters, how many consumers have the ability to evaluate what's written, as the contract law professionals who wrote it? Also, the more comprehensive the TOS agreement, the less likely consumers are inclined to read through it, or comprehend what of it pertains to them. 


Another factor is that a number of such services are, de facto, compulsory: events, webinars, conferences, etc., which are available exclusively through such services.  Does it matter what the TOS says, or if it's read, if there is no real choice but to accept? 
User Rank: Strategist
4/10/2018 | 10:56:30 AM
I think that should read 89% of Android Users didn't know they consented to Facebook data collection.

I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2022-05-26
There is a stack-overflow vulnerability in tinytoml v0.4 that can cause a crash or DoS.
PUBLISHED: 2022-05-25
In SoX 14.4.2, there is a floating-point exception in lsx_aiffstartwrite in aiff.c in libsox.a.
PUBLISHED: 2022-05-25
In SoX 14.4.2, there is an assertion failure in rate_init in rate.c in libsox.a.
PUBLISHED: 2022-05-25
sharp is an application for Node.js image processing. Prior to version 0.30.5, there is a possible vulnerability in logic that is run only at `npm install` time when installing versions of `sharp` prior to the latest v0.30.5. If an attacker has the ability to set the value of the `PKG_CONFIG_PATH` e...
PUBLISHED: 2022-05-25
An information disclosure vulnerability exists in the OAS Engine SecureTransferFiles functionality of Open Automation Software OAS Platform V16.00.0112. A specially-crafted series of network requests can lead to arbitrary file read. An attacker can send a sequence of requests to trigger this vulnera...