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.

Endpoint

12/17/2010
10:35 AM
50%
50%

Password Diversity Urged In Wake Of Gawker Attack

One of biggest threats is reuse of hacked credentials on other websites

As the fallout continues from the breach at Gawker.com that compromised 1.5 million accounts, authentication experts say the incident is a good warning for Gawker users and everyone else to better manage their passwords across Internet accounts.

According to security professionals, some of the biggest risks posed by this latest breach aren't from sensitive data being gleaned from Gawker data stores, but instead from repeated attacks elsewhere using the same username and password combinations in other sensitive locations.

"As far as value to the attackers, these credentials, as well as the credentials for other systems or intelligence that could lead to a repeat intrusion are the primary target," Seth Hanford, operations team lead for IntelliShield, wrote on the Cisco Security Blog. "Not because Gawker and its related web entities are so valuable, but because human nature remains what it is, and passwords are continually reused from site to site."

The proliferation of social media and Web 2.0 sites with protected content and comment boards requiring a log-in has certainly added more strain to the typical user's memory capacity for passwords. While the first impulse might be to reuse passwords, this can only complicate matters if a single credential is uncovered by bad actors.

Most hackers know how rampant password reuse is and will frequently take lists of credentials they've gleaned from breaches, such as those at Gawker, and cross-reference them against banking and financial website log-in pages.

"People must understand that once you provide a password to any Internet site, you are no longer able to protect it," says Thom VanHorn, vice president of global marketing for AppSec. "Yes, those social networks have a responsibility to implement proper security methodologies that include vulnerability assessment and database activity monitoring, but as an individual you also have a responsibility to use common sense and create complex and secure passwords, and vary your password with each different site."

Security adherents urge Gawker users to not only change their Gawker credentials, but any other credential that shares the same username and password. Because the hackers that stole the Gawker information has published the credentials publicly, any enterprising hacker in search of an easy score can utilize that information elsewhere.

In the future, if coming up with unique passwords for every account you have seems daunting, then consider at least prioritizing when you register.

"As stupid as this suggestion sounds, I have three levels of passwords. For sites where I don't care if my credentials are compromised, I use dumb passwords. For areas of reputation, I use a real unique password, but easy to remember and shared," says Phil Lieberman, president of identity management firm Lieberman Software. "For financial systems, I use different passwords that are strong and not guessable. Consequently, a breach on a social site cannot lead to financial loss using this strategy."

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/21/2020
Cybersecurity Bounces Back, but Talent Still Absent
Simone Petrella, Chief Executive Officer, CyberVista,  9/16/2020
Meet the Computer Scientist Who Helped Push for Paper Ballots
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/16/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Latest Comment: Exactly
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-7734
PUBLISHED: 2020-09-22
All versions of package cabot are vulnerable to Cross-site Scripting (XSS) via the Endpoint column.
CVE-2020-6564
PUBLISHED: 2020-09-21
Inappropriate implementation in permissions in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to spoof the contents of a permission dialog via a crafted HTML page.
CVE-2020-6565
PUBLISHED: 2020-09-21
Inappropriate implementation in Omnibox in Google Chrome on iOS prior to 85.0.4183.83 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
CVE-2020-6566
PUBLISHED: 2020-09-21
Insufficient policy enforcement in media in Google Chrome prior to 85.0.4183.83 allowed a remote attacker to leak cross-origin data via a crafted HTML page.
CVE-2020-6567
PUBLISHED: 2020-09-21
Insufficient validation of untrusted input in command line handling in Google Chrome on Windows prior to 85.0.4183.83 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page.