If employees use their same password at work and in their personal lives, another company's breach may weaken your security. Five steps to mitigate the risk.
Following the hack of the global intelligence firm Stratfor, hackers published the stolen password file containing the usernames and hashes for more than 860,000 accounts. An effort to use typical password breaking techniques on the file yielded quick results: About 1 in every 10 accounts had a trivial password.
While it's unknown how many account holders reused their passwords, many subscribers used e-mail addresses of their employer, suggesting the possibility that they reused their passwords as well. While real-world research is scarce, what little there is suggests that reuse is rampant. Following the breach of Sony's online sites last year, for example, an analysis connected a small subset of users to those whose passwords were leaked in another breach. Two-thirds reused their passwords.
For companies, password reuse weakens security and can cause a company to rely on the security of third-party firms whose security is questionable. While companies can attempt to cordon off their employees' work and personal lives, workers can inadvertently reconnect the two, said Sam Curry, chief technology officer for security giant RSA's identity and data protection business unit.
"The average person probably has one or two phones, and they probably have any number of consumer services they subscribe to and two or three machines they interact with," says Sam Curry, chief technology officer for RSA's identity and data protection business unit. "If the password is the same everywhere, then there are literally dozens or hundreds of places where their passwords might be cached or the hash of it might be cached."
While companies can set policy and educate their employees to use good passwords and not reuse the secret codes--especially between business and personal sites--information security specialists should seek other solutions, says Mark Joynes, director of product management for Entrust.
"Enterprises that are taking the matter of security seriously should not be relying on password mechanisms," says Joynes. "As a function of human nature, users will reuse passwords irrespective of the relative risk of the application."
It's no longer a matter of if you get hacked, but when. In this special retrospective of news coverage, Monitoring Tools And Logs Make All The Difference, Dark Reading takes a look at ways to measure your security posture and the challenges that lie ahead with the emerging threat landscape. (Free registration required.)
Published: 2014-09-15 Buffer overflow in the Vcl.Graphics.TPicture.Bitmap implementation in the Visual Component Library (VCL) in Embarcadero Delphi XE6 20.0.15596.9843 and C++ Builder XE6 20.0.15596.9843 allows remote attackers to execute arbitrary code via a crafted BMP file.
Published: 2014-09-15 Ecava IntegraXor SCADA Server Stable 4.1.4360 and earlier and Beta 4.1.4392 and earlier allows remote attackers to read or write to arbitrary files, and obtain sensitive information or cause a denial of service (disk consumption), via the CSV export feature.
Published: 2014-09-15 SQL injection vulnerability in Ecava IntegraXor SCADA Server Stable 4.1.4360 and earlier and Beta 4.1.4392 and earlier allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
Published: 2014-09-15 IBM SONAS and System Storage Storwize V7000 Unified (aka V7000U) 1.3.x and 1.4.x before 184.108.40.206 store the chkauth password in the audit log, which allows local users to obtain sensitive information by reading this log file.