theDocumentId => 741670 In Facebook Debacle, More Than Zuckerberg to Blame

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.

Operational Security //

Big Data

3/23/2018
09:35 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

In Facebook Debacle, More Than Zuckerberg to Blame

Facebook and CEO Mark Zuckerberg are rightly taking a lot of heat from the fallout over Cambridge Analytica and the firm's use of social media data. However, other businesses, as well as users, need to take some responsibility as well.

Facebook and its privacy practices has been at the top of this week's news cycles as the realization of what went on, starting in 2014 and continuing through the 2016 presidential election, has finally dawned on the general public.

The social media giant, along with CEO Mark Zuckerberg, has been accused of all sorts of malfeasance by the denizens of the Internet, the press and even the US government.

There's a real underlying problem here, though. It's the Facebook users themselves that let all of this happen.

It's not new news that Facebook data has been mined for political purposes before this. The Obama campaign did so quite effectively in 2012.

(Source: Wikimedia)
(Source: Wikimedia)

What sets this apart is that a third-party app was able to figure out the private data of the friends of whoever was using that app. This is something that Facebook claimed in 2011, as part of a consent order with the US Federal Trade Commission that it would not allow for commercial use.

There seems to have been an exception for academic use, which was exploited by a Russian-connected academic turned around and who sold that data to a third party -- the shell company Cambridge Analytica -- in violation of Facebook policies. (See How to Access the Voter Information Dirt Cambridge Analytica Has on You.)

Facebook has a primary business model of providing data on its users to commercial interests, who then buy advertising that is targeted to these users based on this data. It's how Facebook lives. In return, it allows users to have certain abilities on its system -- such as posting and sharing things -- but then watches what they actually do and then tells advertisers about it.

Users who are not aware that this happens have their heads buried in the sand in denial. Information of any sort they give to Facebook -- directly or indirectly -- can be exploited by Facebook for their benefit in some manner.

And it's not only Facebook that has this as a business model. Your Internet service provider (ISP) can do the same thing -- selling a list of which sites you connect to interested advertisers.

Any broadband connection you use can detail information to others about what you are doing on the Internet. Yes, I'm looking at you, cable TV.


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth annual Big Communications Event. There's still time to register and communications service providers get in free!

And let's not forget about Google, which has been snickering in the background while Facebook has been getting all the heat. The "Don't Be Evil" firm sort of invented the game here.

So, what can be done in a practical manner to stop Facebook from somehow spewing out things you don't want out?

Have you ever checked Facebook privacy settings? It's a menu choice under the triangle icon you use to log out.

One section is called Apps. There are choices there that allow deletion of apps that can use your information -- or the information of your friends -- for their own purposes. One might delete them all if one wanted to. This privacy granularity wasn't available in quite the same way to users in 2014, but it is now.

Attention to these settings could have stopped the Russian-linked academic in 2014. Changing them now might stop someone else who doesn't care about what Facebook policies are, but just wants the data.

In the end, you are always responsible for your own data. Don't blame Facebook for not being your data nanny. Take back control of your own digital life.

Related posts:

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
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
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
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
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-18428
PUBLISHED: 2021-07-26
tinyexr commit 0.9.5 was discovered to contain an array index error in the tinyexr::SaveEXR component, which can lead to a denial of service (DOS).
CVE-2020-18430
PUBLISHED: 2021-07-26
tinyexr 0.9.5 was discovered to contain an array index error in the tinyexr::DecodeEXRImage component, which can lead to a denial of service (DOS).
CVE-2021-37576
PUBLISHED: 2021-07-26
arch/powerpc/kvm/book3s_rtas.c in the Linux kernel through 5.13.5 on the powerpc platform allows KVM guest OS users to cause host OS memory corruption via rtas_args.nargs, aka CID-f62f3c20647e.
CVE-2021-37555
PUBLISHED: 2021-07-26
TX9 Automatic Food Dispenser v3.2.57 devices allow access to a shell as root/superuser, a related issue to CVE-2019-16734. To connect, the telnet service is used on port 23 with the default password of 059AnkJ for the root account. The user can then download the filesystem through preinstalled BusyB...
CVE-2020-23240
PUBLISHED: 2021-07-26
Cross Site Scripting (XSS) vulnerablity in CMS Made Simple 2.2.14 via the Logic field in the Content Manager feature.